Re: libtool-2.4.2.418 released [alpha]
Hi Gary and Tim, On Wed, 6 Nov 2013, Gary V. Vaughan wrote: | Hi Tim, | | > On 6 Nov 2013, at 11:20, Tim Mooney wrote: | >> The Libtool Team is pleased to announce the release of libtool 2.4.2.418. | > | >> This is a preliminary alpha release to begin platform testing in | >> preparation for the next stable release. | > | > I built 2.4.2.418 on x86_64-pc-solaris2.11 (OpenIndiana 151a8) with | > the Oracle Studio 12.3 toolchain. There was one unexpected failure | > in the new test suite: | > | > 21: quote shell meta-characters in filenamesFAILED (libtool.at:120) | | Yes, I'm seeing this failure on quite a few of my test architectures too, but | haven't been able to get to the bottom of it. If you have any insight, I'd be | very happy to hear about it. Gary, in bug#15734 you sugested it was a problem with grep. On my UnixWare box, I tested with a GNU grep first in the path and #21 did not fail. Now, which part is tripping up the system grep and what to do about it, I do not know. ;-) -- Tim RiceMultitalents(707) 456-1146 t...@multitalents.net ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: libtool-2.4.2.418 released [alpha]
Hi Tim, > On 6 Nov 2013, at 11:20, Tim Mooney wrote: >> The Libtool Team is pleased to announce the release of libtool 2.4.2.418. > >> This is a preliminary alpha release to begin platform testing in >> preparation for the next stable release. > > I built 2.4.2.418 on x86_64-pc-solaris2.11 (OpenIndiana 151a8) with > the Oracle Studio 12.3 toolchain. There was one unexpected failure > in the new test suite: > > 21: quote shell meta-characters in filenamesFAILED (libtool.at:120) Yes, I'm seeing this failure on quite a few of my test architectures too, but haven't been able to get to the bottom of it. If you have any insight, I'd be very happy to hear about it. > If I re-run the test-suite with --verbose, test #21 shows: > > 21. libtool.at:60: testing quote shell meta-characters in filenames ... > ./libtool.at:102: $LIBTOOL -n --mode=$mode $preargs $preflag"$flag:test" > $postargs > stdout: > libtool: compile: cc -c -DVAR=:test foo.c -KPIC -DPIC -o .libs/foo.o > libtool: compile: cc -c -DVAR=:test foo.c -o foo.o >/dev/null 2>&1 > ./libtool.at:106: grep "$mode:.*$match_preflag$flag:test " stdout > stdout: > libtool: compile: cc -c -DVAR=:test foo.c -KPIC -DPIC -o .libs/foo.o > libtool: compile: cc -c -DVAR=:test foo.c -o foo.o >/dev/null 2>&1 > ./libtool.at:116: $LIBTOOL -n --mode=$mode $preargs $preflag"$flag\\:test\\" > $postargs > stdout: > libtool: compile: cc -c "-DVAR=\\:test\\" foo.c -KPIC -DPIC -o .libs/foo.o > libtool: compile: cc -c "-DVAR=\\:test\\" foo.c -o foo.o >/dev/null 2>&1 > ./libtool.at:120: grep > "$mode:.*$match_preflag"'"\?'"$flag:test"'"\? ' stdout > stdout: > ./libtool.at:120: exit code was 1, expected 0 > 21. libtool.at:60: FAILED (libtool.at:120) > > > Let me know what other useful information I can provide. A fix? ;-) > There's a patch after my signature that alters the README to provide > the actual name of the log file from the test suite. Thanks, I'll apply and push that presently. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: libtool-2.4.2.418 released [alpha]
Libtoolers! The Libtool Team is pleased to announce the release of libtool 2.4.2.418. This is a preliminary alpha release to begin platform testing in preparation for the next stable release. I built 2.4.2.418 on x86_64-pc-solaris2.11 (OpenIndiana 151a8) with the Oracle Studio 12.3 toolchain. There was one unexpected failure in the new test suite: 21: quote shell meta-characters in filenamesFAILED (libtool.at:120) If I re-run the test-suite with --verbose, test #21 shows: 21. libtool.at:60: testing quote shell meta-characters in filenames ... ./libtool.at:102: $LIBTOOL -n --mode=$mode $preargs $preflag"$flag:test" $postargs stdout: libtool: compile: cc -c -DVAR=:test foo.c -KPIC -DPIC -o .libs/foo.o libtool: compile: cc -c -DVAR=:test foo.c -o foo.o >/dev/null 2>&1 ./libtool.at:106: grep "$mode:.*$match_preflag$flag:test " stdout stdout: libtool: compile: cc -c -DVAR=:test foo.c -KPIC -DPIC -o .libs/foo.o libtool: compile: cc -c -DVAR=:test foo.c -o foo.o >/dev/null 2>&1 ./libtool.at:116: $LIBTOOL -n --mode=$mode $preargs $preflag"$flag\\:test\\" $postargs stdout: libtool: compile: cc -c "-DVAR=\\:test\\" foo.c -KPIC -DPIC -o .libs/foo.o libtool: compile: cc -c "-DVAR=\\:test\\" foo.c -o foo.o >/dev/null 2>&1 ./libtool.at:120: grep "$mode:.*$match_preflag"'"\?'"$flag:test"'"\? ' stdout stdout: ./libtool.at:120: exit code was 1, expected 0 21. libtool.at:60: FAILED (libtool.at:120) Let me know what other useful information I can provide. There's a patch after my signature that alters the README to provide the actual name of the log file from the test suite. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 --- libtool-2.4.2.418.orig/README 2013-10-26 19:02:00.0 -0500 +++ libtool-2.4.2.418/README2013-11-05 16:16:33.243527395 -0600 @@ -113,7 +113,7 @@ to send the verbose output of the FAILing group, along with the information from the end of '$(top_builddir)/libtool --help' to the bug report mailing list, with a subject line that -includes the string '[TEST FAILURE]'. The file test-suite.log contains +includes the string '[TEST FAILURE]'. The file testsuite.log contains the verbose output from all failed tests. In order to enable debug shell tracing, you can set VERBOSE=debug when ___ https://lists.gnu.org/mailman/listinfo/libtool
