On Monday, December 3, 2012 5:48:40 PM UTC+1, Bill Hart wrote: > > Ah, well that almost certainly has something to do with it. > > Could we try adding that option in the relevant part of configure.in, > run autoreconf -i on eno and see if that does the trick on his system. > > I don't have access to eno (or skynet in general), so I can't. I've given instruction on sage-devel to update configure.in and recraft a new spkg. If not I'll do that myself on some other computer hoping it works and send an spkg with an updated MPIR.
> Unfortunately I cannot issue a new version of MPIR for this. We are > stuck at 2.6.0 until we add a certain function required by another > library (they already added the test for library version in > anticipation). > > That's not a real problem, I think that the problem went unnoticed for some years. It's just when I explicitly asked someone to test this setup on sage-devel that the issue came back. > At some point I could add a diff patch to the website which can be > applied to fix this issue. And of course it will get merged into the > next release. > > Bill. > > On 3 December 2012 16:40, Jean-Pierre Flori <[email protected]<javascript:>> > wrote: > > Further info: > > - the result of ./config.guess is nehalem-apple-darwin9.8.0, which is > not > > one dealt with in MPIR configure.in for the "32 bit apple darwin > doesn't > > like our PIC format asm code". > > - and so we get MPN_PATH=" x86/nehalem x86 generic" > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To view this discussion on the web visit https://groups.google.com/d/msg/mpir-devel/-/D9L8Du-o9S8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
