Re: Libtool head test status
Hallo Ralf, On 8 Mar 2008, at 06:49, Ralf Wildenhues wrote: FWIW, here's the patch again but without mangling. OK? Yep, looks good to me. Please apply. 2008-03-07 Ralf Wildenhues [EMAIL PROTECTED] * tests/nonrecursive.at: Use -no-undefined for foo.la. * tests/recursive.at: Likewise. * tests/subproject.at: Likewise. * tests/lt_dladvise.at: For systems where undefined symbols are not allowed, to not try to load the module libdepend. [ mingw ]: Add to list of such systems. * tests/testsuite.at (_LT_AT_TRANSLATE_TEXT_OUTPUT): New macro, to translate line ending of expout and experr files suitable for host executables. (LT_AT_CHECK, LT_AT_NOINST_EXEC_CHECK): Use it. Report by Bob Friesenhahn. Cheers, Gary -- ())_. Email me: [EMAIL PROTECTED] ( '/ Read my blog: http://blog.azazil.net / )= ...and my book: http://sources.redhat.com/autobook `(_~)_ PGP.sig Description: This is a digitally signed message part
Re: Libtool head test status
On Sat, 8 Mar 2008, Ralf Wildenhues wrote: Now, in that test, the toplevel configure script chooses $top_srcdir/INSTALL (yes, the text file) as install script. I suspect this is because you have /uhome/src/gnu/libtool-head in the $PATH, the beginning of testsuite.log reveals that. Why is that, did you add that manually? Something in 'make check' must be putting it there since it is certainly not anything I did. Perhaps automake does this in order to find its scripts? It would be much safer to invoke any subordinate scripts using full paths. Unfortunately, Windows does not observe case. As evaluated by 'ls -l' in msys, the INSTALL file has permissions -rw-r--r-- so it should not be accidentally executed. However, if I pass /uhome/src/gnu/libtool-head/INSTALL to msys on the command line, it is indeed executed. The same happens with Cygwin. Perhaps since the execute bits are quite unreliable under Windows, any file is deemed executable. This is the path setting in the shell that invoked the tests: Bob [EMAIL PROTECTED] ~/mingw/libtool-head $ echo $PATH .:/usr/local/bin:/activestate/bin:/mingw/bin:/bin:/c/program files/graphicsmagick-1.1.11-q16:/c/Program Files/Microsoft DirectX SDK (June 2007)/Utilities/Bin/x86:/c/Perl/bin/:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/Program Files/Microsoft SQL Server/80/Tools/Binn/:/c/Program Files/Rational/common:/c/Program Files/QuickTime/QTSystem/:/c/Qt/4.1.4/bin:/c/bin:/c/Adabas/bin:/c/Adabas/pgm:/c/Program Files/OpenVPN/bin Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Re: Libtool head test status
On Sat, 8 Mar 2008, Ralf Wildenhues wrote: Now, in that test, the toplevel configure script chooses $top_srcdir/INSTALL (yes, the text file) as install script. I suspect this is because you have /uhome/src/gnu/libtool-head in the $PATH, the beginning of testsuite.log reveals that. Why is that, did you add that manually? It seems that our build environment is extending the path. Both msys and cygwin are happy to execute INSTALL as a shell script if passed to it like a command. Something is clearly doing a case-insensitive search of the PATH to find 'install' and is then using what it found. This is interesting: MINGW = Bob [EMAIL PROTECTED] ~ $ export PATH=/uhome/src/gnu/libtool-head:$PATH Bob [EMAIL PROTECTED] ~ $ which install install is /bin/install Bob [EMAIL PROTECTED] ~ $ which INSTALL INSTALL is /bin/INSTALL Bob [EMAIL PROTECTED] ~ $ INSTALL INSTALL: too few arguments Try `INSTALL --help' for more information. Bob [EMAIL PROTECTED] ~ $ echo $SHELL /bin/sh Cygwin == velma:~% which install /usr/bin/install velma:~% export PATH=/uhome/src/gnu/libtool-head:$PATH velma:~% which install /usr/bin/install velma:~% rehash velma:~% which install /usr/bin/install velma:~% install install: missing file operand Try `install --help' for more information. velma:~% INSTALL /uhome/src/gnu/libtool-head/INSTALL: line 1: Installation: command not found ./#.emacs#: line 2: syntax error near unexpected token `;;' ./#.emacs#: line 2: ` ;; custom-set-variables was added by Custom -- don't edit or cut/paste it!' /uhome/src/gnu/libtool-head/INSTALL: line 4: syntax error near unexpected token `C' /uhome/src/gnu/libtool-head/INSTALL: line 4: `Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,' velma:~% echo $SHELL /bin/zsh velma:~% bash bash-3.2$ which install install is /usr/bin/install bash-3.2$ echo $PATH /uhome/src/gnu/libtool-head:/activestate/bin:/usr/local/bin:/usr/X11R6/bin:/usr/bin:/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:. bash-3.2$ export SHELL=/bin/bash bash-3.2$ which install install is /usr/bin/install bash-3.2$ which INSTALL INSTALL is /usr/bin/INSTALL bash-3.2$ INSTALL INSTALL: missing file operand Try `INSTALL --help' for more information. == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Re: Libtool head test status
Ralf Wildenhues wrote: Now, in that test, the toplevel configure script chooses $top_srcdir/INSTALL (yes, the text file) as install script. I suspect this is because you have /uhome/src/gnu/libtool-head in the $PATH, the beginning of testsuite.log reveals that. Why is that, did you add that manually? On MinGW (under MSYS, where '.' is in the default PATH) I've always found it necessary to explicitly specify INSTALL=/bin/install when configuring/making packages -- not just libtool, but almost any autotooled package. Part of this is the '.'-in-path thing, coupled with the case-insensitive nature of the filesystem, plus the look for either foo OR foo.exe in each DIR of $PATH, before going to next DIR behavior. The nuances are slightly different on cygwin and msys. I've never had this happen on cygwin, though. -- Chuck
Re: Libtool head test status
Hi Bob, * Bob Friesenhahn wrote on Sat, Mar 01, 2008 at 08:07:01AM CET: These are results of tests I ran this evening. These are all builds from outside the source tree, including MinGW and Cygwin, which used a SMB mount to a Unix filesystem. Thanks for your testing efforts. Can you send the testsuite.log files for these two setups? Thanks. FWIW, I did testing on MinGW, and experienced failures of 21 38 39 61 62 63 64, of which 39 61 62 are testsuite issues (\r) and 64 is a followup failure. Cheers, Ralf Cygwin (old) on Windows XP == ERROR: 60 tests were run, 6 failed (3 expected failures). 4 tests were skipped. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: [EMAIL PROTECTED] Subject: [libtool 2.1c] testsuite: 21 38 64 failed MinGW (old) on Windows XP = ERROR: 62 tests were run, 14 failed (3 expected failures). 2 tests were skipped. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: [EMAIL PROTECTED] Subject: [libtool 2.1c] testsuite: 21 38 39 46 50 53 60 61 62 63 64 failed
Re: Libtool head test status
On Sun, 2 Mar 2008, Bob Friesenhahn wrote: Both are attached in lzma compressed format. I find it odd that the log file is much larger for MinGW/MSYS than for Cygwin. It seems that part of the reason for the bloat is that Makefiles don't make good shell scripts. :-) I see that in some cases the Makefile is being executed by the shell implying that a MAKE command expansion/substitution is not working. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Libtool head test status
These are results of tests I ran this evening. These are all builds from outside the source tree, including MinGW and Cygwin, which used a SMB mount to a Unix filesystem. Solaris 9 SPARC/GCC === 61 tests behaved as expected. 3 tests were skipped. Solaris 10 SPARC/GCC 61 tests behaved as expected. 3 tests were skipped. Solaris 10 x86/GCC == 61 tests behaved as expected. 3 tests were skipped. FreeBSD 5.4 === 62 tests behaved as expected. 2 tests were skipped. Apple OS-X Leopard PPC == 58 tests behaved as expected. 6 tests were skipped. Cygwin (old) on Windows XP == ERROR: 60 tests were run, 6 failed (3 expected failures). 4 tests were skipped. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: [EMAIL PROTECTED] Subject: [libtool 2.1c] testsuite: 21 38 64 failed MinGW (old) on Windows XP = ERROR: 62 tests were run, 14 failed (3 expected failures). 2 tests were skipped. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: [EMAIL PROTECTED] Subject: [libtool 2.1c] testsuite: 21 38 39 46 50 53 60 61 62 63 64 failed == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
