Hi Ralf, > Sure. I've pushed the combined patch as > <http://git.savannah.gnu.org/gitweb/?p=libtool.git;a=commit;h=101ad44541c6d303cf465937a212042885f4338e>.
Thanks for adding this. > > 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' Find attached the resulting logs (stdout+stderr, and tests/testsuite.dir/36/testsuite.log). The test passes. But it also passes when I comment out the line newargv = prepare_spawn (newargv); in ltmain.sh and do a "make clean; make": The output of make check-local TESTSUITEFLAGS='-v -d -x -k execute' is then exactly the same. This indicates that the test is not actually checking against the bug whose fix is prepare_spawn. Bruno
libtool-log1.gz
Description: GNU Zip compressed data
libtool-testsuite.log.gz
Description: GNU Zip compressed data
