We have actually hit this problem ourselves and are quite frankly mystified as to where it is picking up a broken MPIR or GMP from...
Anyway, I propose the following solution. If we change the numbers in Makefile.am to 22 : 6 : 1 we should get a library version number 16.6.1 which should exceed all previous library numbers. I have checked that this works. The only question is, do you want me to release MPIR-2.7.2 for this or reissue MPIR-2.7.1? I prefer to do the latter, since it is quite broken for everyone. (On the other hand, if I make it 2.7.2 should I then use 22 : 6 : 2?) Bill. On 19 November 2015 at 18:37, Bill Hart <goodwillh...@googlemail.com> wrote: > You can understand my confusion then, as in MPIR 2.7.0 we had: > > LIBGMP_LT_CURRENT = 16 > LIBGMP_LT_REVISION = 0 > LIBGMP_LT_AGE = 6 > > and in MPIR-2.7.1 we have: > > LIBGMP_LT_CURRENT = 16 > LIBGMP_LT_REVISION = 1 > LIBGMP_LT_AGE = 6 > > leading to .so version numbers 16.0.0 and 10.6.1. > > So just to get this straight, because I think this is absolutely > hilarious: the previous version numbers were totally screwed up because of > whitespace. I am just now recovering from the effects of the side-splitting > laughter that ensued. Given how idiotic the vim editor is, I cannot be the > only person who has hit this bug. > > Thanks to Leif for tracking this down. I don't think there is any way I > could have even guessed that this would be the problem. > > I've just now committed a patch to remove the remaining whitespace in > Makefile.am. > > Bill. > > On 19 November 2015 at 15:45, leif <not.rea...@online.de> wrote: > >> 'Bill Hart' via mpir-devel wrote: >> > Hmm, actually, I have >> > >> > LIBGMP_LT_CURRENT = 16 >> > LIBGMP_LT_REVISION = 1 >> > LIBGMP_LT_AGE = 6 >> > >> > I don't see where the 10 is coming from. >> >> Libtool madness. >> >> But the flaw w.r.t. the strange change is actually in the previous >> version of MPIR; the variable definitions in Makefile.am must not >> contain trailing whitespace (which is still the case for >> LIBGMPXX_LT_REVISION, and has been the case for LIBGMP_LT_REVISION in >> 2.7.0). >> >> >> -leif >> >> > On 19 November 2015 at 15:03, Bill Hart <goodwillh...@googlemail.com >> > <mailto:goodwillh...@googlemail.com>> wrote: >> > >> > That looks like a stupid bug on our part. >> > >> > I think the best way to fix this is to correct the .so version >> > number in our repo since the current numbering is useless. >> > >> > Bill. >> > >> > On 19 November 2015 at 14:28, Jeroen Demeyer < >> jdeme...@cage.ugent.be >> > <mailto:jdeme...@cage.ugent.be>> wrote: >> > >> > The .so version number changed from >> > >> > libmpir.so.16.0.0 (MPIR 2.7.0) >> > >> > to >> > >> > libmpir.so.10.6.1 (MPIR 2.7.1) >> > >> > which is strange in several ways (it's a downgrade; did the >> > version need to change at all for a bug-fix release?). It's >> > probably at the basis of the problems in Sage. >> > >> > >> > Jeroen. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "mpir-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to mpir-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to mpir-de...@googlegroups.com. >> Visit this group at http://groups.google.com/group/mpir-devel. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
