[sage-devel] Re: Failure building MPIR on sage 4.3.2

MPIR 1.4 is probably not far out. I'm hopeful Sage will include that. The MPIR Team On 5 Mar, 14:32, Bill Hart wrote: > I doubt Sage will includempir1.3.1. Numerous versions of sage have > past without including this, so presumably there is some reason for > that. > > But I'm sure sage will even

[sage-devel] Re: Failure building MPIR on sage 4.3.2

I doubt Sage will include mpir 1.3.1. Numerous versions of sage have past without including this, so presumably there is some reason for that. But I'm sure sage will eventually update to *some* more recent version of MPIR, which will certainly fix the yasm issues, and perhaps many others. Bill.

[sage-devel] Re: Failure building MPIR on sage 4.3.2

And trying again to build Sage 4.3.3, MPIR seems to build fine. Sorry or the false alarm. Thank you very much for your help! - Ryan -- 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 F

[sage-devel] Re: Failure building MPIR on sage 4.3.2

I just tried building MPIR 1.3.1 on /tmp -- a local file system -- instead of the network file system I was using before. Suddenly, it works! I assume the next Sage release will include this MPIR revision. Sage 4.3.3 (MPIR 1.2.2) fails to build yasm as before. Thanks! - Ryan -- To post to th

[sage-devel] Re: Failure building MPIR on sage 4.3.2

I tried the same exercise on a related Xeon cluster -- with the same failure on mpn/.libs/add_n.o. I will be on #sage-devel (IRC) off and on if anyone wants to work on this real-time. The (new) config.log is at . The behavior in both cases appears t

Re: [sage-devel] Re: Failure building MPIR on sage 4.3.2

> 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

[sage-devel] Re: Failure building MPIR on sage 4.3.2

This is a 64 bit machine, but MPIR is unable to build in 64 bit mode for some strange reason. At least the yasm problem is fixed with the new yasm in MPIR 1.3.1. Can you send us the file config.log. Also, what happens if you do: cat /proc/cpuinfo Can you confirm that the C compiler actually wor

[sage-devel] Re: Failure building MPIR on sage 4.3.2

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=/u

Re: [sage-devel] Re: Failure building MPIR on sage 4.3.2

On Tue, 23 Feb 2010 09:44:34 Bill Hart 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 from http://www.mpir.org/ and verify it > builds on your machine outside

[sage-devel] Re: Failure building MPIR on sage 4.3.2

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 from http://www.mpir.org/ and verify it builds on your machine outside of the Sage context. Is there anything else potentially unu