On Thursday, February 28, 2013 7:06:18 PM UTC+1, leif wrote: > > Jean-Pierre Flori wrote: > > For info, I'm trying to build Sage on a Debian sparc64, and it failed > > because by default gcc produces 32 bits objects but then MPIR (and MPFR > > and MPC) decided to be smart enough to build as 64 bits, and then when > > Sage tried to build its own GCC, which is 32 bits, it failed... > > > > Exporting ABI=32 seems to calmn down MPIR, but I guess it should be like > > that by default. > > That's not very surprising, as AFAIK neither Linux SPARC nor Linux > SPARC64 is among the platforms anyone has ever tried (or intended) to > port Sage to. > > So despite we tried to remove the partially present OS/platform > dependency of SAGE64 a while ago (i.e., not really caring about it on > anything but SunOS and Darwin), there might still be implicit > assumptions (especially in spkg-install scripts) such that SAGE64 > effectively gets ignored on Linux. > > For MPIR on Linux, we currently only support setting ABI (and > C[XX]FLAG64). More precisely, unless ABI is already set, our > spkg-install script explicitly sets ABI to 64 if the compiler is able to > produce 64-bit executables *and* we're able to run these, otherwise to > 32, with a few exceptions (Itanium, POWER/PPC). > > So setting ABI=32 (at least for MPIR) on Linux SPARC64 is currently the > [correct] way to go. > > Deciding to default to 32-bit builds on Debian SPARC64 is IMHO pretty > arbitrary. (FWIW, anybody could decide to configure his/her GCC to > build 32-bit binaries on 64-bit OSs [with 32-bit runtime support] by > default.) > > > -leif > > > > If I by any chance get a working 32 bit install, I'll try to give a 64 > > bits install a shot, and this should be triggered using SAGE64 :) > > > > I'll also give a shot on Solaris 10 / sparc64, but the gcc I have there > > is old and MPIR complains... > > -- > () The ASCII Ribbon Campaign > /\ Help Cure HTML E-Mail > > GCC is quite funny, without help it will refuse to try to build itself as a 64 bit app (and by default MPIR is 64 bits so it fails). But then setting ABI=32, you get a 32 bits MPIR, a 32 bits stage 1 gcc, which tries to build a 64 bits stage 2 gcc, what fails because MPIR is now 32 bits :)
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
