On 9/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> When building any of the 2.8.3.x releases on my 64-bit Opteron 246
> running RHEL5, I encounter the following error during the compile of
> the
> sage-2.8.3.x module.
...
> In file included from
> /scratch/sage-2.8.3/local/include/python2.5/Python.h:57,
> from stdsage.h:35,
> from interrupt.c:12:
> /scratch/sage-2.8.3/local/include/python2.5/pyport.h:734:2: error:
> #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc
> config?)."
> scons: *** [interrupt.os] Error 1
> ------
> The thing is, I'm pretty sure my glibc is current. gcc -v returns:
> -----
> Alos, SAGE 2.8.2 compiles fine. And 2.8.3 runs fine from the Debian
> binary.
>
> Is this a misconfiguration on this machine, or something more serious?
I don't know, but I'm going to take it very seriously.
First, does the file stdint.h exist on your machine? If so
does the following program compile and run or not, and
if so, what does it output:
#include <stdio.h>
#include <stdint.h>
main() {
printf("%d",LONG_BIT);
}
Second, could you try commenting the error out of
local/include/python2.5/pyport.h
then trying to finish the SAGE build and see what happens?
Just comment out line 737 (or thereabouts) that looks like this:
#error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
then do "sage -br" (or make) to get going again.
William
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
