3 failed tests?
Hello, I ended up getting 3 failed tests, all being the same test, depdemo-inst.test. Im running off of Mac OS X 10.4.7, using the bash shell. Also it gave me this right under your email. make[2]: *** [check-TESTS] Error 1 make[1]: *** [check-am] Error 2 make: *** [check-recursive] Error 1 I hope this helps. -- -Jonathan Handler ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: 3 failed tests?
On Jul 28, 2006, at 12:49 AM, Jon Handler wrote: Hello, I ended up getting 3 failed tests, all being the same test, depdemo-inst.test. Im running off of Mac OS X 10.4.7, using the bash shell. Also it gave me this right under your email. make[2]: *** [check-TESTS] Error 1 make[1]: *** [check-am] Error 2 make: *** [check-recursive] Error 1 I hope this helps. Hi Jon, Actually, it would be much more interesting to see which tests failed and why. Could you run make check again with VERBOSE=1 e.g. env VERBOSE=1 make check TESTS=depdemo-conf depdemo-make depdemo-inst And post the results here (compressed if large). Also please include the libtool version and xcode version. Thanks, Peter ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
Hi Stephen, * Stephen More wrote on Tue, May 24, 2005 at 11:30:28PM CEST: On 5/24/05, Ralf Wildenhues [EMAIL PROTECTED] wrote: * Stephen More wrote on Tue, May 24, 2005 at 08:44:27PM CEST: I built libtool-1.5.6 on a RHEL4 ( Red Hat Enterprise Linux Box ) $ ./config.guess i686-pc-linux-gnu *snip* I then built libtool-1.5.18 on the same box and got: 25 of 101 tests failed Is there anything else you would like me to report ? Please rerun the test suite with VERBOSE=X and send the output, preferably packed (bzip2, gzip). Here is the output. Thanks a bunch! This looks like a reincarnation of a bug with ash I reported (and believed fixed) quite some time ago: | === Running demo-make.test | Making in ../demo *snip* | /bin/sh ./libtool --tag=CC --mode=link gcc -g -O2 -o helldl -export-dynamic -dlpreopen libhello.la dlmain.o | rm -f .libs/helldl.nm .libs/helldl.nmS .libs/helldl.nmT | creating .libs/helldlS.c | extracting global C symbols from `./.libs/libhello.a' | (cd .libs gcc -c -fno-builtin helldlS.c) | helldlS.c:12: error: stray '\1' in program | helldlS.c:12: warning: useless keyword or type name in empty declaration | helldlS.c:12: warning: empty declaration | make[3]: *** [helldl] Error 1 Let me guess: Your /bin/sh is ash, and somehow libtool fails to find the proper $echo (which should be != echo). Could you please post the exact configure line you issued plus output, and config.log? Thanks, Ralf ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
On 5/25/05, Ralf Wildenhues [EMAIL PROTECTED] wrote: Let me guess: Your /bin/sh is ash, and somehow libtool fails to find the proper $echo (which should be != echo). $ ls -l /bin/sh lrwxrwxrwx 1 root root 4 Apr 6 14:24 /bin/sh - bash [EMAIL PROTECTED] libtool-1.5.18]$ rpm -q -a | grep -i bash bash-3.0-19.2 Could you please post the exact configure line you issued plus output, and config.log? Sure attached find the output and config.log. Let me know what else you may need. -Steve More config.log.bz2 Description: BZip2 compressed data typescript.bz2 Description: BZip2 compressed data ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
Oh, no. * Ralf Wildenhues wrote on Wed, May 25, 2005 at 09:19:27AM CEST: Thanks a bunch! I'm sorry. I just recently learned that this phrase does _not_ mean Thanks a lot, but rather has a negative connotation. I'm not a native speaker, and also I tend to forget such things. Sorry for any resulting misunderstandings. (I'll think I need to go and hide a while now..) Regards, Ralf ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
* Stephen More wrote on Wed, May 25, 2005 at 02:42:55PM CEST: On 5/25/05, Ralf Wildenhues [EMAIL PROTECTED] wrote: Let me guess: Your /bin/sh is ash, and somehow libtool fails to find the proper $echo (which should be != echo). $ ls -l /bin/sh lrwxrwxrwx 1 root root 4 Apr 6 14:24 /bin/sh - bash [EMAIL PROTECTED] libtool-1.5.18]$ rpm -q -a | grep -i bash bash-3.0-19.2 Could you please post the exact configure line you issued plus output, and config.log? Sure attached find the output and config.log. Let me know what else you may need. I'm stunned. How did that happen (from config.log): | ECHO='echo -e' Libtool configuration sure does not contain any code which sets this. Do you have anything like this in your environment? What says env | grep ECHO If so, could you please unset ECHO and try configuring again to make sure all failure are gone now? Thanks, Ralf ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
Great !! Yes, ECHO='echo -e' was set. I unset ECHO and now I pass All 112 tests. After some trouble shooting, I have found out that this environment variable was set because of an installed rpm: Computer Associates International BrightStor ARCserve Backup. ( This just reinforces my opion of CA Software. ) Thank you again for all your help. -Steve More On 5/25/05, Ralf Wildenhues [EMAIL PROTECTED] wrote: I'm stunned. How did that happen (from config.log): | ECHO='echo -e' Libtool configuration sure does not contain any code which sets this. Do you have anything like this in your environment? What says env | grep ECHO If so, could you please unset ECHO and try configuring again to make sure all failure are gone now? ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
Hi Stephen, * Stephen More wrote on Wed, May 25, 2005 at 03:47:57PM CEST: Great !! Yes, ECHO='echo -e' was set. I unset ECHO and now I pass All 112 tests. Good to know. After some trouble shooting, I have found out that this environment variable was set because of an installed rpm: Computer Associates International BrightStor ARCserve Backup. ( This just reinforces my opion of CA Software. ) Well, environment variables like `ECHO' are not really standardized in any way. One could argue that it is as much a bug in Libtool to honor it as it is in whatever other software packages you use. FYI, within branch-2-0 and HEAD Libtool versions we moved to using lt_ECHO instead of ECHO, which should have a much smaller chance of collision with other software. Regards, Ralf ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Failed Tests
I built libtool-1.5.6 on a RHEL4 ( Red Hat Enterprise Linux Box ) $ ./config.guess i686-pc-linux-gnu 25 of 99 tests failed (11 tests were not run) Please report to bug-libtool@gnu.org I then built libtool-1.5.18 on the same box and got: 25 of 101 tests failed (11 tests were not run) Please report to bug-libtool@gnu.org Here are the items that failed: FAIL: demo-make.test FAIL: demo-exec.test FAIL: demo-inst.test FAIL: mdemo-make.test FAIL: demo-make.test FAIL: demo-exec.test FAIL: demo-inst.test FAIL: mdemo-make.test FAIL: dryrun.test FAIL: demo-make.test FAIL: demo-exec.test FAIL: demo-inst.test FAIL: demo-make.test FAIL: demo-exec.test FAIL: demo-make.test FAIL: demo-exec.test FAIL: demo-make.test FAIL: demo-exec.test FAIL: demo-inst.test FAIL: mdemo-make.test FAIL: quote.test FAIL: pdemo-make.test FAIL: pdemo-exec.test FAIL: pdemo-inst.test FAIL: mdemo-make.test Is there anything else you would like me to report ? Steve More ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
Hi Stephen, * Stephen More wrote on Tue, May 24, 2005 at 08:44:27PM CEST: I built libtool-1.5.6 on a RHEL4 ( Red Hat Enterprise Linux Box ) $ ./config.guess i686-pc-linux-gnu *snip* I then built libtool-1.5.18 on the same box and got: 25 of 101 tests failed Is there anything else you would like me to report ? Please rerun the test suite with VERBOSE=X and send the output, preferably packed (bzip2, gzip). Regards, Ralf ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
Here is the output. -Steve More On 5/24/05, Ralf Wildenhues [EMAIL PROTECTED] wrote: Hi Stephen, * Stephen More wrote on Tue, May 24, 2005 at 08:44:27PM CEST: I built libtool-1.5.6 on a RHEL4 ( Red Hat Enterprise Linux Box ) $ ./config.guess i686-pc-linux-gnu *snip* I then built libtool-1.5.18 on the same box and got: 25 of 101 tests failed Is there anything else you would like me to report ? Please rerun the test suite with VERBOSE=X and send the output, preferably packed (bzip2, gzip). Regards, Ralf typescript.bz2 Description: BZip2 compressed data ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: Failed Tests
Hi Timothy, * Timothy Moran wrote on Sat, Apr 30, 2005 at 05:33:11PM CEST: Just leaving a message about certain bugs that your program had responded to. Thanks. Attached file is a trap log from Linux/Linspire. Tim M. Igland:/Added Programs/libtool-1.5.16# ./configure Not a good idea. Libtool and, FWIW, many other packages that use Autoconf will not like to run in directories with a path with spaces in the name. We know this is technically suboptimal, but the fact that many shell scripts are involved together with the fact that white space is the common shell word delimiter makes this near impossible to fix. It's much less work if you rename your directory differently -- you may add a symlink to keep the original path working for other software, e.g.: mv 'Added Programs' Added_Programs ln -s Added_Programs 'Added Programs' checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes /Added: /Added: No such file or directory All your subsequent failures should be caused by this. Regards, Ralf ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
