2009/12/23 Nareto <renn...@gmail.com>:
> Hello Bill, thanks for replying. My system is:
> $ uname -a
> Linux tosharch 2.6.31-ARCH #1 SMP PREEMPT Tue Nov 10 19:48:17 CET 2009
> i686 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel GNU/Linux
>
> so it's a 32bit. Old? It's no older than 3 years, which (sigh) I guess
> is old in computer terms.

I think you have 64-bit *hardware* but you are running a 32-bit OS on
it.  This is probably confusing the Sage build system somehow.

> I did find out something. I downloaded as you suggested mpir 1.3.0-rc3
> and it compiled without errors. 'make check' also didn't give errors
> and reported "All 3 tests passed". I was looking at the ./configure
> output and comparing it to the one from the sage compilation and I
> spotted this difference:
>
> mpir 1.2.p9 (from sage's sources):
> using ABI="64"

That's the problem.  Try setting

  export ABI=32

before building Sage.

We don't set ABI in the spkg-install for mpir, so I have no idea how
it's getting set to 64 instead of 32.

William

>      CC="gcc -std=gnu99"
>      CFLAGS="-march=i686 -mtune=core2 -O2 -pipe"
>      CPPFLAGS=""
>      CXX="g++"
>      CXXFLAGS="-march=i686 -mtune=core2 -O2 -pipe"
>      MPN_PATH=" x86_64/core2 x86_64 generic"
>
> mpir 1.3.0-rc3:
> using ABI="32"
>      CC="gcc -std=gnu99"
>      CFLAGS="-m32 -O2 -fomit-frame-pointer -mtune=core2 -march=core2"
>      CPPFLAGS=""
>      MPN_PATH=" x86/core2 x86 generic"
>
> is this relevant? I'll ask sage people how to get it to use ABI=32 and
> see if it works
>
> regards,
> Renato
>
> --
>
> You received this message because you are subscribed to the Google Groups 
> "mpir-devel" group.
> To post to this group, send email to mpir-de...@googlegroups.com.
> To unsubscribe from this group, send email to 
> mpir-devel+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/mpir-devel?hl=en.
>
>
>



-- 
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

--

You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.com.
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.


Reply via email to