Bill Hart wrote:
Is it really trying to build a fat binary? I doubt that will work very
many places. The fat binary support is there for binary builders to
build binaries for multiple users, not for users to build
binaries themselves.
I doubt the fat binary option is compatible with many of the other
options either.
Well, this seems to be again someone running a 32-bit OS on a 64-bit CPU
(core-pc-linux-gnu according to the configure output).
I recall we explicitly had to set ABI=32 (hence added it to Sage's
spkg-install script) on such systems a while ago... (i.e., for MPIR 2.4.0)
Not sure why ABI="standard" (meaning what on x86/x86_64?) is required
here. (The C compiler, some GCC 4.7.2, is configured to build 32-bit
binaries by default, but also with --enable-targets=all.)
(I don't think --enable-fat is causing the problem.)
-leif
On Sunday, 24 February 2013, Jean-Pierre Flori wrote:
This was reported here:
https://groups.google.com/d/topic/sage-devel/9hpOtZYu8kI/discussion
Also see #14172
Apparently MPIR does not like the ABI=32 var (???) but prefers
ABI=standard.
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mpir-devel+unsubscr...@googlegroups.com.
To post to this group, send email to mpir-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/mpir-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
