Jaap Spies wrote:
> William Stein wrote:
>> On Thu, Sep 10, 2009 at 12:08 PM, Jaap Spies <j.sp...@hccnet.nl> wrote:
>>> Minh Nguyen wrote:
>>>> Hi folks,
>>>>
>>>> This release has the following updated packages:
>>>>
>>>> * matplotlib-0.99.0.spkg
>>>> * networkx-0.99.p1-fake_really-0.36.p1.spkg
>>>>
>>>> The source tarball and sage.math binary are available at
>>>>
>>>> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha1.tar
>>>> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha1-sage.math.washington.edu-x86_64-Linux.tar.gz
>>>>
>>>> and the upgrade path is
>>>>
>>>> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha1/
>>>>
>>>> Please test and report all problems.
>>>>
>>> Build fails on Fedora 11, 32 bit:
>>>
>>> gcc  -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer    -I. 
>>> -I../src/headers  -o base3.o ../src/basemath/base3.c
>>> gcc: Internal error: Killed (program cc1)
>> This is a bug in GCC.  It's been reported to the GCC developers by the
>> PARI developers and they recently fixed it, but haven't released the
>> fix.  You'll have to either build PARI without optimizations or use an
>> older compiler.
>>
>> Or maybe we should find a workaround, e.g., not build that one file
>> with optimizations?  I'm definitely +1 to somebody making a hackish
>> workaround since those broken GCC's are going to be widely deployed
>> for years.
>>
>> Thoughts?
>>
> 
> Changing O3 to O1 in src/config/get_cc did the job.
> After a 'touch spkg/installed/pari-2.3.3.p1' the buid goes on.
> 

OK, it builds well, and:
----------------------------------------------------------------------
All tests passed!


Jaap


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an 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