[ Cc:ing the list ] * Bruno Haible wrote on Tue, Nov 11, 2008 at 12:21:10AM CET: > > > If you prefer a tarball for testing, then I can also just push the > > combined patch and you can use the nightly build from the Libtool > > web page. > > Yes please. It's safer and less troublesome if I can use a complete > tarball.
Sure. I've pushed the combined patch as <http://git.savannah.gnu.org/gitweb/?p=libtool.git;a=commit;h=101ad44541c6d303cf465937a212042885f4338e>. > What should I check, other than "./configure; make; make check"? Wait until the nightly snapshot on <http://pogma.com/libtool/> is new enough to contain this change, unpack it, ./configure make make check-local TESTSUITEFLAGS='-v -d -x -k execute' If you have an old libtool script lying around from before the patch, you can verify that the test suite exposes the failure, with: make check-local \ TESTSUITEFLAGS='-v -d -x -k execute LIBTOOL=path/to/old/libtool' Of course, if you have the energy to do a full 'make -k check' on this system, that's great, too. But it will take long, and in case you're running Vista, it will be interactive, too. :-/ Thanks, Ralf
