Slow response, but here it is. I'm working on the school computing cluster. It runs Rocks 5.1 (V.I), which I believe is a RedHat derivative (/bin/rpm exists, for one...). Here is the GCC version.
$ gcc -v Using built-in specs. Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man -- infodir=/usr/share/info --enable-shared --enable-threads=posix -- enable-checking=release --with-system-zlib --enable-__cxa_atexit -- disable-libunwind-exceptions --enable-libgcj-multifile --enable- languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk -- disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.4.2- gcj-1.4.2.0/jre --with-cpu=generic --host=x86_64-redhat-linux Thread model: posix gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) I downloaded mpir-1.3.1 outside of sage and started the compile. Yasm seems to have built just fine. But it failed in a different place. When creating libmpir.so, GCC returns the error, mpn/.libs/add_n.o: file not recognized: File format not recognized The more-or-less full log is at <http://www.hintonclan.org/iobass/mpir- script.txt>. Further help is much appreciated! - Ryan On Feb 22, 3:44 pm, Bill Hart <[email protected]> wrote: > This is a yasm issue (yasm is a prereq for MPIR and is included in the > tarball). > > I haven't ever seen yasm not build on an Opteron before. > > Can you download MPIR 1.3.1 fromhttp://www.mpir.org/and verify it > builds on your machine outside of the Sage context. > > Is there anything else potentially unusual about this machine? > > Bill. > > On 22 Feb, 16:33, RyanHinton<[email protected]> wrote: > > > snip -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
