I have made a spkg for GCC (GNU compiler collection) version 4.6.3 with compilers for C, C++ and Fortran, see Trac #12369.
The GCC spkg depends on an MPC (multi-precision complex numbers) spkg. There has been an optional MPC package and a Sage interface for it. GCC would use the upgraded MPC package from #12515. According to (unwritten?) rules, one cannot add a spkg as standard package if it hasn't been an optional spkg first. I would like to ask for an exception for GCC and add it immediately as standard package in sage-5.0. Also MPC would need to become a standard package, but this already has been an optional package and so is less controversial. Let me clarify that GCC would not always be built: if the system already contains sufficiently recent versions of gcc, g++ and gfortran (or g95 or g77), then GCC would not be built. Currently, "sufficiently recent version of gcc" is defined as: at least 4.4.0 but not 4.6.0 nor 4.6.1 (there are known bugs in cliquer and rubiks with these gcc versions). An environment variable SAGE_INSTALL_GCC can be used to override this default choice (set to "yes" to force installation of GCC or to "no" to prevent it). The Fortran package (which contained gfortran binaries for OS X) would be removed, therefore about 4MB would be added to the source tarball size (Fortran was 33MB, GCC+MPC is 37MB). I think there is not much point in making GCC optional, since it's only used at build-time. Once Sage has been built, you don't need it anymore. What are your +1/-1 to making GCC and MPC standard packages? Jeroen. -- 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
