mpir on 32-bit

45 views
Skip to first unread message

kcrisman

unread,
Feb 11, 2013, 10:28:37 AM2/11/13
to sage-...@googlegroups.com
See http://ask.sagemath.org/question/1713/error-installing-package-mpir-240p6

Will this probably need an spkg upgrade to fix?  It's nice that people are finding the answer on ask.sagemath, but...

Jean-Pierre Flori

unread,
Feb 11, 2013, 10:43:45 AM2/11/13
to sage-...@googlegroups.com
We are now at MPIR 2.6.0, so it would be nice to know if this upgrade alone fixes the problem.

Thierry

unread,
Feb 23, 2013, 4:20:03 PM2/23/13
to sage-...@googlegroups.com
I have problems in compiling sage 5.7. The build stops during the build
of the mpir-2.6.0.p0 package.

spkg/logs/mpir-2.6.0.p0.log is pasted at http://paste.debian.net/237529/

The problem seems related to some 32bit architecture (hence i send my
message on this thread) :

Building a 32-bit version of MPIR.
Building MPIR with the C++ interface and (also) static libraries.
** Building with "fat binary" support for 32-bit CPUs **
[...]
configure: error: ABI=32 is not among the following valid choices: standard
Error configuring MPIR (with CFLAGS unset).

The machine is running Debian wheezy,
Linux 3.2.0-4-686-pae #1 SMP Debian 3.2.35-2 i686 GNU/Linux

I used the following sage variables :
- SAGE_FAT_BINARY='yes'
- SAGE_BINARY_BUILD='yes'
- SAGE_CHECK="yes"
- MAKE="make -j2"

I had no problem building 5.6 on the same machine with the same
configuration. I will try to 'export ABI=standard' as suggested in
ask.sagemath.

Ciao,
Thierry

Thierry

unread,
Feb 24, 2013, 7:11:11 AM2/24/13
to sage-...@googlegroups.com
On Sat, Feb 23, 2013 at 10:20:03PM +0100, Thierry wrote:
[...]
> I had no problem building 5.6 on the same machine with the same
> configuration. I will try to 'export ABI=standard' as suggested in
> ask.sagemath.

Exporting ABI='standard' globally allows the mpir spkg to be built but
then gap-4.5.7.p3 cannot be built since it also uses the ABI variable
for which the value 'standard' does not make sense (it only accepts
ABI=32 or ABI=64).

I created a ticket at http://trac.sagemath.org/sage_trac/ticket/14172

Ciao,
Thierry

Jean-Pierre Flori

unread,
Feb 24, 2013, 9:01:20 AM2/24/13
to sage-...@googlegroups.com
Ill report this on mpir group.

leif

unread,
Feb 24, 2013, 12:56:58 PM2/24/13
to sage-...@googlegroups.com
Thierry wrote:
> On Sat, Feb 23, 2013 at 10:20:03PM +0100, Thierry wrote:
> [...]
>> I had no problem building 5.6 on the same machine with the same
>> configuration. I will try to 'export ABI=standard' as suggested in
>> ask.sagemath.

That included MPIR 2.4.0.


> Exporting ABI='standard' globally allows the mpir spkg to be built but
> then gap-4.5.7.p3 cannot be built since it also uses the ABI variable
> for which the value 'standard' does not make sense (it only accepts
> ABI=32 or ABI=64).


This seems to be an upstream bug (actually, a regression) in MPIR 2.6.0,
which apparently doesn't allow ABI=32 specifically on
core[-pc-linux-gnu] (i.e., on old Intel Core CPUs, predecessors of the
Core2 processors).

(Setting ABI=standard [only] when installing the MPIR spkg is just a
work-around.)


-leif

>
> I created a ticket at http://trac.sagemath.org/sage_trac/ticket/14172
>
> Ciao,
> Thierry
>


--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail

Reply all
Reply to author
Forward
0 new messages