Let me add a few clarifications to this email: On 2012-04-15 21:36, Georg S. Weber wrote: > "he who codes, rules" as the saying goes. I was wrong (and I'm glad > about it!). Just some comments w.r.t. the reasoning in that old message > of mine. Firstly, if I'm not mistaken, OS X is the only system where > Sage now builds its own (GCC both C and Fortran) compiler, not anywhere > else, especially not on Linux. That's actually not true. Currently, GCC is built on all systems where the system compiler is not GCC or is GCC version < 4.4.0. The environment variable SAGE_INSTALL_GCC can be used to override this.
> Secondly, there was nevertheless still quite some work to do, with more > than one (tickets and) participants, to switch on OS X from "Apple" GCC > (v4.0.1 resp. v4.2.1) to "FSF" GCC (v4.6.2) to build Sage. We ship GCC-4.6.3 (there were some earlier GCC-4.6.2 spkgs). > Thirdly, Jeroen's new spkg uses some clever tricks for bootstrapping GCC > --- on the one hand, that spkg relies on the MPFR and MPIR (as a > replacement for GMP) libraries to having been built first by the host > compiler, but on the other hand, it includes itself the sources of the > (to be built and needed) MPC library. This is not true. MPC now is a standard spkg just like MPIR and MPFR. Some earlier versions of my GCC spkg did include MPC. > After GCC is built, both the MPFR > and MPIR libraries are rebuilt, now with the newly built and functional > GCC MPC is also rebuilt. > --- which in turn is *not* built a second time after that --- which > a purist might want to do, due to the altered way MPFR and MPIR are now > built, but in practice, it does not seem to really matter. Indeed. It doesn't matter because GCC dynamically links against MPIR/MPFR/MPC. After rebuilding those libraries, gcc will use those new libraries. > Behind the scenes, OS X / > XCode seems to provide pretty stable (or at least up-to-the-task) > versions of all the other required requisites for bootstrapping GCC > (binutils, libtool, a linker/loader, ..., make, bison, flex, ...) bison and flex are NOT required to build GCC (or any other part of Sage). -- 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
