2009/12/23 Nareto <renn...@gmail.com>: > I asked this problem on the mpir-devel list - at this link > http://groups.google.com/group/mpir-devel/browse_thread/thread/9644685107e7d203 > > As suggested I tried compiling latest version of mpir (1.3.0-rc3) > standalone and it compiled without errors. Comparing the output of ./ > configure from the sage compilation and the mpir standalone > compilation, i saw this difference: > > mpir 1.2.p9 (from sage's sources): > using ABI="64" > 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" > > my machine (as can be seen from 'uname -a' in first post) is 32 bit, > so could the error be caused by sage using ABI=64? How do I get it to > run ./configure for mpir using ABI=32 ?
His machine is 64-bit hardware (a core 2 duo) running a 32-bit OS. I suggested on the MPIR list that he do export ABI=32 then build Sage. William -- 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 http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
