On Wednesday 05 September 2007 11:21, mabshoff wrote:
> On Sep 5, 5:08 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > 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.
>
> <SNIP>
>
> William's suggestions are workaround, but I don't believe they fix the
> real issue (if they work). interrupt.c is unchanged between 2.8.2 and
> 2.8.3[.3], but:
>
> [EMAIL PROTECTED] Work2]$ diff -urN sage-2.8.2/devel/c_lib/src/stdsage.h
> sage-2.8.3.4/devel/sage-main/c_lib/stdsage.h
> --- sage-2.8.2/devel/c_lib/src/stdsage.h 2007-08-24
> 16:27:03.000000000 +0200
> +++ sage-2.8.3.4/devel/sage-main/c_lib/stdsage.h 2007-08-31
> 18:41:00.000000000 +0200
> @@ -33,6 +33,7 @@
> #define STDSAGE_H
>
> #include "Python.h"
> +#include "ccobject.h"
>
> #ifdef __cplusplus
> extern "C" {
>
> And:
>
> /**
> * @file ccobject.h
> *
> * @author Joel B. Mohler <[EMAIL PROTECTED]>
> *
> * @brief These functions provide assistance for constructing and
> destructing
> * C++ objects from pyrex.
> *
> */
>
> So maybe Joel can jump in on this. This might be a compiler issue,
> even though I do not see the problem on a Centos 5 box at all, I just
> build 2.8.3.3 and then upgrade to 2.8.3.4.
As of 2.8.3.4, I think you could comment out ccobject.h and still have a
compiling sage. I don't think anyone has submitted patches relying on it --
I plan to submit such patches this week yet.
This certainly isn't a fix, but it could provide some clues about what is
broken.
--
Joel
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
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/
-~----------~----~----~----~------~----~------~--~---
