On 10/16/07, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Oct 16, 6:09 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > On 10/16/07, mabshoff <[EMAIL PROTECTED]> wrote:
> >
>
> Hi David,
>
> <SNIP>
>
> > > gcc blows up, there is little we can do about that. Please check if
> > > there are updates compilers available for SuSE 10.2. If not you can
> > > either install your own gcc from sources or install the optional
> > > gcc.spkg. In that case you need to modify  $LD_LIBRARY_PATH to also
> > > include $SAGE_LOCAL/lib64 before $SAGE_LOCAL/lib on an AMD 64 box.
> >
> > > I will have a look at sage/libs/pari/gen.c:19784 and see if there is
> > > anything suspicious in that area. Could you please open a ticket along
> > > the lines of "paru/gen.c causes internal compiler error on OpenSuSE
> > > 10.2" and give us "uname -a" and "gcc -v".
> >
> > Done.http://sagetrac.org/sage_trac/ticket/908
> >
>
> Some poking around reveals that this is a known regression with pari
> and gcc 4.1.0. See:
>
> http://gcc.gnu.org/ml/gcc-bugs/2006-04/msg00700.html
> http://lists.debian.org/debian-gcc/2006/05/msg00139.html
>
> > This is on a work machine, so is not that easy to access,
> > but I'll try to do some more testing.
> >
>
> Well, could you just for fun rebuild pari? I think the compiler should
> blow up in that case, too,  and I am curious why pari's build system
> doesn't catch it.

The command
sage -f pari-2.3.2.p3
worked fine on the suse machine.


>
> Regarding a solution: I have discussed this with William before but I
> plan to offer a complete optional tool chain for compiling Sage that
> is integrated into the make system just for cases like this where the
> system's compiler screws us. The optional gcc spkg should work for you
> for now provided you fix $LD_LIBRARY_PATH in the way I mentioned
> earlier. If you do so first install the gcc spkg and then force a
> rebuild of pretty much every spkg with the exception of prereq I
> believe. The gcc compilers ends up in $SAGE_LOCAL, so there is no
> chance it could screw up your system or have side effects on other
> components.
>
> Cheers,
>
> Michael
>
> <SNIP>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@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-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to