On Wednesday, 14 March 2012 09:07:17 UTC+8, John H Palmieri wrote: > > > > On Tuesday, March 13, 2012 5:11:00 PM UTC-7, Dima Pasechnik wrote: >> >> >> >> On Monday, 12 March 2012 06:15:35 UTC+8, Jeroen Demeyer wrote: >>> >>> 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). >>> >> $ gcc -v >> Using built-in specs. >> Target: i686-apple-darwin10 >> [...] >> gcc version 4.2.1 (Apple Inc. build 5666) (dot 3) >> >> You seem to indicate this will not be used to build Sage any more. >> Right? >> (even though this is a working setup, as far as Sage 5.0.beta* are >> concerned... >> > > In my experience, it's not a working setup on OS X Lion: pari fails > self-tests (and this also leads to failures in Sage doctests), gsl fails > self-tests, and symmetrica also causes failures in Sage doctests. See also > #12459. (See #11881 for the meta ticket for building on Lion.) > > I guess the answer to your question is yes, though: even with OS X 10.6 or > earlier, the proposal is to build gcc. >
how much binary incompatibility is it going to introduce? I imagine it's easy to reach the point when system libraries won't work any more together with binaries produced by such a compiler... Dima > > -- > John > > -- 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
