On Wed, Oct 14, 2009 at 3:29 AM, Martin Albrecht <m...@informatik.uni-bremen.de> wrote: > > Hi there, > > I had trouble building the current rc2. > > make[6]: Leaving directory > `/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/src/library/base' > /usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/bin/exec/R: > /usr/local/sage-4.1.2.rc2/local/lib/gcc-lib/x86_64-unknown-linux- > gnu/4.0.3/libgcc_s.so.1: version `GCC_4.2.0' not found (required by > /usr/lib/libstdc++.so.6) > make[5]: *** [all] Error 1 > make[5]: Leaving directory > `/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/src/library/base' > make[4]: *** [R] Error 1 > make[4]: Leaving directory > `/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/src/library' > make[3]: *** [R] Error 1 > make[3]: Leaving directory > `/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/src' > make[2]: *** [R] Error 1 > make[2]: Leaving directory `/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src' > > > It is quite understandable that GCC_4.2.0 isn't found in that library because > it is 4.0.3 the trouble is: I don't have 4.0.3 installed anyway. The library > was put there by the fortran SPKG. If I remove it, then r's build will fail > because it cannot execute fortran. > > I managed to make it compile by changing CFLAGS in spkg-install, but surely > this is not the way to go. Bottomline seems to be: the fortran installed by > Sage conflicts with the GCC installed on the system?
Use the SAGE_FORTRAN and SAGE_FORTAN_LIB environment variables to use gfortran. See the README.txt. Soon we'll deprecate including our own fortran on all Linuxes. William --~--~---------~--~----~------------~-------~--~----~ 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 URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
