On Thursday, 10 May 2012 07:42:44 UTC, P Purkayastha wrote: > > On 05/10/2012 03:37 PM, Jeroen Demeyer wrote: > > I see the problem. Originally, Sage (or you) decided to install the GCC > > package within Sage. As a consequence, MPIR was built without the C++ > > interface. From the MPIR log: > >> Building a reduced version of MPIR to bootstrap GCC. > >> MPIR will later get rebuilt (with the C++ interface and static > libraries > >> enabled) using the new compiler. > > Then MPFR failed, causing the build to abort. Then you messed with > > CFLAGS (and maybe compiler versions?) and rebuilt Sage but this time > > *without* installing GCC. This left the "partial" MPIR build in place. > > > > Rebuilding MPIR should fix your problem. > > > > Oh. That's nice. > > Indeed, the build had failed once with it trying to install gcc. While > compiling or installing gcc it complained that some headers were missing. > > It turned out that the reason why it was trying to install gcc was > because I didn't have gfortran in my system. So, I installed gfortran > and restarted the build of Sage.
it seems to me that missing gfortran alone should not trigger a build of the gcc spkg. It might cause similar problems on systems which have good enough gcc to build Sage, but which are not tested in such a scenario. > > I already started another build of Sage to check if it works this time > round. Hopefully it should turn out fine this time. > -- 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
