These are all caused by the same issue. Yasm is producing 64 bit
binaries and MPIR is trying to build a 32 bit binary, or vice versa.
How precisely is MPIR being built on these machines. Specifically,
what is the exact configure command issued? I suspect someone is
trying to override the compiler
* This is what mpir's config is:
CC Version
gcc -v
Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
On 2010-Jan-15 12:21:09 -0800, Robert Miller r...@rlmiller.org wrote:
* This is what mpir's config is:
CC Version
gcc -v
Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
...
I'm not sure whether you are trying to build a 32-bit or 64-bit
sage (there's nothing in prereq which clearly states one way or
the other) but it looks like mpir is building all the assembler
code in 64-bit mode and all the C code in 32-bit mode. That
definitely isn't going to work.
This is
Robert Miller wrote:
I'm not sure whether you are trying to build a 32-bit or 64-bit
sage (there's nothing in prereq which clearly states one way or
the other) but it looks like mpir is building all the assembler
code in 64-bit mode and all the C code in 32-bit mode. That
definitely isn't going
These failures still appear when building mpir-1.2.2 instead of
mpir-1.2.2.p0
--
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
Dr. David Kirkby wrote:
Robert Miller wrote:
These seem related to #7910... Any thoughts?
When you say they seem to be related to #7910, what makes you think that?
I realise there is a mix of 32 and 64-bit objects in those list of error
messages, but I think the reasons for #7910 are pretty
