#11216 closed task (fixed)
Metaticket - make Sage work with gcc 4.6.0
Reported by: | drkirkby | Owned by: | GeorgSWeber |
---|---|---|---|
Priority: | blocker | Milestone: | sage-4.7.1 |
Component: | build | Keywords: | gcc |
Cc: | gostrc, leif | Merged in: | sage-4.7.1.alpha4 |
Authors: | Mariah Lenox | Reviewers: | Jeroen Demeyer |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
Sage will not build with gcc 4.6.0 due to a number of issues. These need to be resolved asap, as Fedora 15 will ship with gcc 4.6.0.
At least some of the problems that prevent Sage building with gcc 4.6.0 are:
- #10892 (lcalc)
- #11083 (PolyBoRi)
- #11084 (Singular)
- #11168 and #11437 (Rubiks)
- #11226 (sympow)
- #11227 (Cliquer)
There may be others on specific platforms.
When all these issues are resolved, the "Install from Source Code" section of the Sage Installation Guide needs to be updated to remove the notes about Sage not building with gcc 4.6.0. Also the Wiki at http://wiki.sagemath.org/SupportedPlatforms needs to be updated, as that now mentions that Sage will not build with gcc 4.6.0.
The lcalc, Singular and PolyBoRi issues have all been reported upstream.
Attachments (1)
Change History (15)
comment:1 Changed 11 years ago by
- Description modified (diff)
comment:2 Changed 11 years ago by
- Description modified (diff)
- Summary changed from Metaticket - List of bugs needed to be resolved for Sage to build with gcc 4.6.0 to Metaticket - make Sage work with gcc 4.6.0
- Type changed from enhancement to task
comment:3 Changed 11 years ago by
- Description modified (diff)
- Keywords gcc added
- Priority changed from critical to blocker
- Report Upstream changed from None of the above - read trac for reasoning. to N/A
comment:4 follow-up: ↓ 6 Changed 11 years ago by
- Status changed from new to needs_review
comment:5 Changed 11 years ago by
- Description modified (diff)
comment:6 in reply to: ↑ 4 Changed 11 years ago by
- Status changed from needs_review to needs_work
Changed 11 years ago by
comment:7 Changed 11 years ago by
- Description modified (diff)
- Status changed from needs_work to needs_review
I have updated the Wiki at http://wiki.sagemath.org/SupportedPlatforms. I believe the patch reverts the changes of #11159 that mention gcc-4.6.0.
comment:8 Changed 11 years ago by
- Merged in set to sage-4.7.1.alpha4
- Resolution set to fixed
- Reviewers set to Jeroen Demeyer
- Status changed from needs_review to closed
Looks good!
comment:9 Changed 11 years ago by
sage-4.7.1-alpha4 still fails to build on archlinux with gcc-4.6.0
running build_ext building 'Crypto.PublicKey._fastmath' extension creating build/temp.linux-i686-2.6 creating build/temp.linux-i686-2.6/src gcc -Wall -Wstrict-prototypes -I/opt/sage-build/sage-4.7.1.alpha4/local/include -L/opt/sage-build/sage-4.7.1.alpha4/local/lib -march=native -mtune=native -pipe -fomit-frame-pointer -fPIC -O3 -fomit-frame-pointer -Isrc/ -I/opt/sage-build/sage-4.7.1.alpha4/local/include/python2.6 -c src/_fastmath.c -o build/temp.linux-i686-2.6/src/_fastmath.o /usr/lib/gcc/i686-pc-linux-gnu/4.6.0/cc1: symbol lookup error: /usr/lib/libppl_c.so.4: undefined symbol: _ZN23Parma_Polyhedra_Library13have_sse_unitE error: command 'gcc' failed with exit status 1 Error installing PyCrypto... exiting real 0m0.198s user 0m0.117s sys 0m0.060s sage: An error occurred while installing pycrypto-2.1.0 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /opt/sage-build/sage-4.7.1.alpha4/install.log. Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /opt/sage-build/sage-4.7.1.alpha4/spkg/build/pycrypto-2.1.0 and type 'make check' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/opt/sage-build/sage-4.7.1.alpha4/spkg/build/pycrypto-2.1.0' && '/opt/sage-build/sage-4.7.1.alpha4/sage' -sh) When you are done debugging, you can type "exit" to leave the subshell. make[1]: *** [installed/pycrypto-2.1.0] Error 1 make[1]: Leaving directory `/opt/sage-build/sage-4.7.1.alpha4/spkg' real 119m10.612s user 101m4.015s sys 8m34.880s Error building Sage.
I had the same issue when building sage-4.7.0 with gcc-4.6.0. http://groups.google.com/group/sage-devel/browse_thread/thread/1fbbc05ae9837c96/80cd305a6e908bf9?lnk=raot&pli=1 https://groups.google.com/forum/#!topic/sage-devel/hLL02U1Q5zU
comment:10 Changed 11 years ago by
The workaround that I used for sage-4.7.0 was to replace $SAGE_ROOT/local/lib/libppl.so.9.0.0
with /usr/lib/libppl.so.9.0.0
comment:11 Changed 11 years ago by
comment:12 Changed 11 years ago by
Apparently it is only the 32-bit version of sage that fails to build with gcc-4.6 as noted in the ticket referenced above (#11391).
comment:13 Changed 11 years ago by
- Cc gostrc added
comment:14 Changed 11 years ago by
- Cc leif added
sage-4.7 was successfully built with gcc-4.6.0 on all the Linux machines on skynet. I believe this ticket should be closed.