It looks to me like you have something hanging around in your
environment you shouldn't have. Specifically you have:
CFLAGS=-O0 -g
So it never runs the tests to see which ABI is appropriate. It is
trying to build with ABI=64, which means it is taking the 64 bit
assembly code, but the compiler is
Thanks for your answer. Please find attached
spkg/build/gmp-mpir-1.1.2/src/config.log.
Bill Hart writes:
> Can you post the contents of MPIR's config log in
> spkg/build/mpir.../src/src thanks.
>
> Bill.
>
> 2009/6/3 Jhair :
>>
>> Hello,
>>
>> I'm trying to compile the sage library which AFAIK u
Can you post the contents of MPIR's config log in
spkg/build/mpir.../src/src thanks.
Bill.
2009/6/3 Jhair :
>
> Hello,
>
> I'm trying to compile the sage library which AFAIK uses mpir:
> http://www.sagemath.org/.
>
> I'm getting build errors like:
>
> /usr/bin/ld: i386:x86-64 architecture of inp
Hello,
I'm trying to compile the sage library which AFAIK uses mpir:
http://www.sagemath.org/.
I'm getting build errors like:
/usr/bin/ld: i386:x86-64 architecture of input file `mpn/.libs/
add_n.o' is incompatible with i386 output
If I check the generated file, it says:
$ file ./spkg/build/g
Hi Peter,
Can you begin following the instructions for MSVC Express in the
readme file in the build.vc9 directory. Let us know how far you get.
I did this myself the other day and it worked fine, so with a bit of
work you should be able to do this too.
Bill.
2009/6/3 Peter_APIIT :
>
>
>
> On 3
On 30 May, 18:38, Bill Hart wrote:
> Ah, this issue is discussed for GMP here:
>
> http://gmplib.org/list-archives/gmp-bugs/2008-July/001047.html
>
> Exactly the same thing is happening in MPIR because originally MPIR
> started from the GMP codebase and no changes we have made since have
> rect
