Oh yes of course, you have to touch configure.in. I'll add that to my instructions.
Bill. 2009/7/28 Jason Moxham <[email protected]>: > > configure depends on configure.in and gmp-h.in at least , but as far as > autotools knows it only depends on configure.in , so it wont regenerate if > you only change the version number in gmp-h.in . I'll put a ticket for this. > > I've svn everything now , we are ready to release , I've left the make > install-gmpcompat option in docs and Makefile , we dont need it , but it > doesn't do any harm. I've removed it in trunk. > > > On Tuesday 28 July 2009 22:02:05 Jason Moxham wrote: >> Found the problem , I deleted configure , ran autoreconf , and the new >> configure had the latest 1.2.2 , never had a problem with configure not >> updating before . Just tried it again , and it happens all the time. >> Does your autotools update the version number on configure for the current >> SVN rev 2206 >> >> On Tuesday 28 July 2009 21:52:44 Jason Moxham wrote: >> > I tried that , but no joy , I tend to use >> > >> > Usage: /usr/bin/autoreconf [OPTION] ... [DIRECTORY] ... >> > >> > Run `autoconf' (and `autoheader', `aclocal', `automake', `autopoint' >> > (formerly `gettextize'), and `libtoolize' where appropriate) >> > repeatedly to remake the GNU Build System files in specified >> > DIRECTORIES and their subdirectories (defaulting to `.'). >> > >> > I couldn't find any 1.2.1 that needed changing , perhaps its in a split >> > format ie a 1 , a 2 , a 1 , that will be difficult to find >> > >> > On Tuesday 28 July 2009 21:37:29 Bill Hart wrote: >> > > This sequence before make dist is critical. >> > > >> > > aclocal >> > > autoheader >> > > autoconf >> > > automake >> > > ./configure >> > > >> > > Dunno if it is the right order though, so I run everything more than >> > > once to make sure. >> > > >> > > I suppose if that doesn't work you can grep for 1.2.1 and see what >> > > hasn't changed. The main place to change it is at the bottom of >> > > gmp-h.in. Then one or more of the above in the right order are suppose >> > > to update it in all the right places. >> > > >> > > Bill. >> > > >> > > 2009/7/28 Jason Moxham <[email protected]>: >> > > > On Tuesday 28 July 2009 15:10:30 Bill Hart wrote: >> > > >> Check out trunk into an appropriately named directory on sage.math >> > > >> Edit NEWS with all new features and improvements >> > > >> Edit ChangeLog with new release date >> > > >> Edit AUTHORS file with their new contributions >> > > >> Edit version number in gmp-h.in >> > > >> Update soname stuff in Makefile.am (1.2.3->1.2.4 need to take rev >> > > >> number from 1.2.3 not from trunk) >> > > >> Update doc/version.texi with version and dates >> > > >> makeinfo version.texi >> > > >> makeinfo mpir.texi >> > > >> update build.vc9/config.* with version number in each file >> > > >> aclocal >> > > >> autoheader >> > > >> autoconf >> > > >> automake >> > > >> ./configure >> > > >> check lots of makefiles, configure and config.h have been altered >> > > >> check everything in to svn >> > > >> make dist >> > > > >> > > > Done all that , but I still get mpir-1.2.1.tar.gz , there is still a >> > > > missing one or something >> > > > >> > > > By the way I notice we dont put bug fixes in NEW/Changelog , so I >> > > > havent bothered either >> > > > >> > > >> 2009/7/28 Jason Moxham <[email protected]>: >> > > >> > configure has version string still at 1.2.1 , but I cant see where >> > > >> > it comes from. >> > > >> > >> > > >> > On Tuesday 28 July 2009 01:44:38 Jason Moxham wrote: >> > > >> >> On Tuesday 28 July 2009 01:15:33 Jason Moxham wrote: >> > > >> >> > On Tuesday 28 July 2009 01:02:09 Bill Hart wrote: >> > > >> >> > > Yes, we can issue 1.2.2, but not from trunk. There's too much >> > > >> >> > > broken stuff in there at present. If you apply the patches to >> > > >> >> > > the 1.2.x branch. Do you want to do the honours. >> > > >> >> > >> > > >> >> > Ok , I just want to test it on a sun box , and a couple of >> > > >> >> > other systems, it was a trivial fix , so it shouldn't of broke >> > > >> >> > anything else (thats the kiss of doom , putting it in writing) >> > > >> >> > . No other fixes worth putting in? >> > > >> >> > Not sure I can fix the docs , my latex is broken , or was. >> > > >> >> >> > > >> >> I can't find all the references to mpir version numbers? >> > > >> >> scooby-doo where are you? , havent done the tests yet , have to >> > > >> >> sleep now , will finish tomorrow >> > > >> >> >> > > >> >> > > Once there's a tarball, I can upload it. Actually you should >> > > >> >> > > have access, but I don't think you do. >> > > >> >> > > >> > > >> >> > > Bill. >> > > >> >> > > >> > > >> >> > > 2009/7/28 Jason Moxham <[email protected]>: >> > > >> >> > > > I've Fixed this in trunk SVN , and this also fixes the >> > > >> >> > > > extra requirement of make install-gmpcompat , we dont >> > > >> >> > > > require it anymore. We can issue a mpir-1.2.2 ? >> > > >> >> > > > >> > > >> >> > > > On Monday 27 July 2009 23:07:27 Jason Moxham wrote: >> > > >> >> > > >> The problem is this , when we install libgmpxx we have to >> > > >> >> > > >> relink it against libgmp and libgmp is not installed yet . >> > > >> >> > > >> For libmpir this is not a problem as libtool knows this is >> > > >> >> > > >> the library we are installing and so looks elsewhere for >> > > >> >> > > >> the library. For libgmp , libtool doesn't know this ( and >> > > >> >> > > >> we couldn't figure out how to tell it) , so the install >> > > >> >> > > >> fails with libgmpxx , but on other unices it does get as >> > > >> >> > > >> far as installing libgmp , so a second attempt at >> > > >> >> > > >> installation is successful(and this is what we do at the >> > > >> >> > > >> mo) . For some reason bsd does the libgmp and libgmpxx as >> > > >> >> > > >> a pair and if libgmpxx fails then libgmp is not installed >> > > >> >> > > >> either. If I install libgmp manualy , then we can install >> > > >> >> > > >> libgmpxx as normal. >> > > >> >> > > >> >> > > >> >> > > >> On Monday 27 July 2009 15:40:12 Jason Moxham wrote: >> > > >> >> > > >> > Hi , I'll give it go >> > > >> >> > > >> > >> > > >> >> > > >> > My guess is that this is what is wrong >> > > >> >> > > >> > >> > > >> >> > > >> > ./configure blah --enable-gmpcompat >> > > >> >> > > >> > test ret code >> > > >> >> > > >> > make >> > > >> >> > > >> > test ret code >> > > >> >> > > >> > make install >> > > >> >> > > >> > test ret code >> > > >> >> > > >> > # this can return a fail , but for gmp-compat we have to >> > > >> >> > > >> > ignore it make install-gmpcompat >> > > >> >> > > >> > test ret code >> > > >> >> > > >> > >> > > >> >> > > >> > Jason >> > > >> >> > > >> > >> > > >> >> > > >> > On Monday 27 July 2009 14:24:41 William Stein wrote: >> > > >> >> > > >> > > Hi, >> > > >> >> > > >> > > >> > > >> >> > > >> > > Do of you mpir devs want to try to debug that Sage >> > > >> >> > > >> > > fails to build on FreeBSD because of MPIR? I can give >> > > >> >> > > >> > > you an account on the relevant freebsd box. >> > > >> >> > > >> > > >> > > >> >> > > >> > > William >> > > >> >> > > >> > > >> > > >> >> > > >> > > >> > > >> >> > > >> > > ---------- Forwarded message ---------- >> > > >> >> > > >> > > From: Minh Nguyen <[email protected]> >> > > >> >> > > >> > > Date: Mon, Jul 27, 2009 at 3:41 AM >> > > >> >> > > >> > > Subject: [sage-devel] status of FreeBSD 64-bit support >> > > >> >> > > >> > > To: [email protected] >> > > >> >> > > >> > > >> > > >> >> > > >> > > >> > > >> >> > > >> > > >> > > >> >> > > >> > > Hi folks, >> > > >> >> > > >> > > >> > > >> >> > > >> > > As of Sage 4.1.1.alpha1, the compilation of Sage now >> > > >> >> > > >> > > dies when it comes to compiling MPIR. The full log is >> > > >> >> > > >> > > up at >> > > >> >> > > >> > > >> > > >> >> > > >> > > http://sage.math.washington.edu/home/mvngu/patch/insta >> > > >> >> > > >> > >ll -f ree bsd 64 .l og >> > > >> >> > > >> > > >> > > >> >> > > >> > > Here's a relevant snippet from my attempt: >> > > >> >> > > >> > > >> > > >> >> > > >> > > /usr/local/bin/bash ./libtool --mode=install >> > > >> >> > > >> > > /usr/bin/install -c 'libgmpxx.la\ ' >> > > >> >> > > >> > > '/usr/scratch/mvngu/sage-4.1.1.alpha1/local/lib/libgmp >> > > >> >> > > >> > >xx .l a' libtool: install: warning: relinking >> > > >> >> > > >> > > `libgmpxx.la' (cd >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg/build/mpir-1 >> > > >> >> > > >> > >.2 .p 4/s rc; /usr/local\ /bin/bash ./libtool >> > > >> >> > > >> > > --tag=CXX --mode=relink g++ -O2 -m64 -march=k8 >> > > >> >> > > >> > > -mtune=k8 -\ o libgmpxx.la -rpath >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/local/lib >> > > >> >> > > >> > > -version-in\ fo 4:4:1 dummy.lo cxx/isfuns.lo >> > > >> >> > > >> > > cxx/ismpf.lo cxx/ismpq.lo cxx/ismpz.lo cxx/ismp\ >> > > >> >> > > >> > > znw.lo cxx/osdoprnti.lo cxx/osfuns.lo cxx/osmpf.lo >> > > >> >> > > >> > > cxx/osmpq.lo cxx/osmpz.lo li\ bgmp.la ) g++ -shared >> > > >> >> > > >> > > -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o >> > > >> >> > > >> > > .libs/dummy.o cxx/.\ libs/isfuns.o cxx/.libs/ismpf.o >> > > >> >> > > >> > > cxx/.libs/ismpq.o cxx/.libs/ismpz.o cxx/.libs/i\ >> > > >> >> > > >> > > smpznw.o >> > > >> >> > > >> > > cxx/.libs/osdoprnti.o cxx/.libs/osfuns.o >> > > >> >> > > >> > > cxx/.libs/osmpf.o cxx/.libs/o\ smpq.o >> > > >> >> > > >> > > cxx/.libs/osmpz.o -Wl,--rpath >> > > >> >> > > >> > > -Wl,/usr/scratch/mvngu/sage-4.1.1.alpha1/\ local/lib >> > > >> >> > > >> > > -L/usr/scratch/mvngu/sage-4.1.1.alpha1/local/lib -lgmp >> > > >> >> > > >> > > -L/usr/lib -ls\ tdc++ -lm -lc -lgcc_s >> > > >> >> > > >> > > /usr/lib/crtendS.o /usr/lib/crtn.o -m64 -march=k8 >> > > >> >> > > >> > > -mtune\ =k8 -Wl,-soname -Wl,libgmpxx.so.4 -o >> > > >> >> > > >> > > .libs/libgmpxx.so.4 /usr/bin/ld: cannot find -lgmp >> > > >> >> > > >> > > libtool: install: error: relink `libgmpxx.la' with the >> > > >> >> > > >> > > above command before ins\ talling it >> > > >> >> > > >> > > *** Error code 1 >> > > >> >> > > >> > > >> > > >> >> > > >> > > Stop in >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg/build/mpir-1 >> > > >> >> > > >> > >.2 .p 4/s rc. *** Error code 1 >> > > >> >> > > >> > > >> > > >> >> > > >> > > Stop in >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg/build/mpir-1 >> > > >> >> > > >> > >.2 .p 4/s rc. *** Error code 1 >> > > >> >> > > >> > > >> > > >> >> > > >> > > Stop in >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg/build/mpir-1 >> > > >> >> > > >> > >.2 .p 4/s rc. *** Error code 1 >> > > >> >> > > >> > > >> > > >> >> > > >> > > Stop in >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg/build/mpir-1 >> > > >> >> > > >> > >.2 .p 4/s rc. Error installing MPIR. >> > > >> >> > > >> > > >> > > >> >> > > >> > > real 5m58.954s >> > > >> >> > > >> > > user 1m55.129s >> > > >> >> > > >> > > sys 5m52.480s >> > > >> >> > > >> > > sage: An error occurred while installing mpir-1.2.p4 >> > > >> >> > > >> > > Please email sage-devel >> > > >> >> > > >> > > http://groups.google.com/group/sage-devel explaining >> > > >> >> > > >> > > the problem and send the relevant part of >> > > >> >> > > >> > > of /usr/scratch/mvngu/sage-4.1.1.alpha1/install.log. >> > > >> >> > > >> > > Describe your computer, o\ perating system, etc. >> > > >> >> > > >> > > If you want to try to fix the problem, yourself >> > > >> >> > > >> > > *don't* just cd to >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg/build/mpir-1 >> > > >> >> > > >> > >.2 .p 4 and type 'make'. Instead type >> > > >> >> > > >> > > "/usr/scratch/mvngu/sage-4.1.1.alpha1/sage -sh" in >> > > >> >> > > >> > > order to set all environment variables correctly, then >> > > >> >> > > >> > > cd to >> > > >> >> > > >> > > /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg/build/mpir-1 >> > > >> >> > > >> > >.2 .p 4 (When you are done debugging, you can type >> > > >> >> > > >> > > "exit" to leave the subshell.) >> > > >> >> > > >> > > *** Error code 1 >> > > >> >> > > >> > > >> > > >> >> > > >> > > Stop in /usr/scratch/mvngu/sage-4.1.1.alpha1/spkg. >> > > >> >> > > >> > > >> > > >> >> > > >> > > real 6m10.853s >> > > >> >> > > >> > > user 1m59.821s >> > > >> >> > > >> > > sys 6m0.205s >> > > >> >> > > >> > > Error building Sage. >> > > >> >> > > >> > > >> > > >> >> > > >> > > -- >> > > >> >> > > >> > > Regards >> > > >> >> > > >> > > Minh Van Nguyen >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. 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 -~----------~----~----~----~------~----~------~--~---
