Hi,

2009/5/30 mabshoff <mabsh...@googlemail.com>:
>
>
>
> On May 30, 10:20 am, William Stein <wst...@gmail.com> wrote:
>> 2009/5/30 Andrzej Giniewicz <ggi...@gmail.com>:
>>
>>
>>
>> > Hi,
>>
>> > tried to do some test, but I have similar issue as Vlad reported on
>> > sage-support for 4.0rc0 in topic "building sage 4.0.rc0 with gcc 4.4.0
>> > and glibc 2.10.1 fails (on arch linux)", (btw, I also have Arch with
>> > gcc 4.4 and glibc 2.10), the error for me it:
>>
>> Just for the record, every major new GCC release requires changes to
>> Sage, and I'm pretty certain we haven't fixed everything for GCC 4.4.0
>> yet.
>
> No, gcc 4.4.0 works on multiple platforms. The issue the Arch people
> are seeing happens to cause problem on at least gcc 4.2.x - see
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28671#c8 - and the correct
> thing to do is to not compile gcc with arch or march settings. I have
> fixed 95% of #2999-3001 in all spkgs which would all to inject flags
> like march into each spkg.

I don't like building GCC without march eighter, anyway the error
seems to dissapear with snapshot 4.4-20090526 from gcc.gnu.org but
then it strikes ICE somewhat later, trying to isolate it for report to
gcc mailing list, anyway will have to wait some time to use sage, but
on other side the old debug fun is on again, I was always liked
tracking sneaky ICEs :)

cheers,
Andrzej.

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to