Use -no-undefined in install tests.

2008-11-11 Thread Ralf Wildenhues
Another trivial testsuite failure with w32 (cross compiled; the failure is exposed with the pending *EXEC_CHECK patch applied). Pushed. Cheers, Ralf Use -no-undefined in install tests. * tests/install.at (Install tests): Use `-no-undefined'. diff --git a/tests/install.at b/tests

Re: testsuite.at for version 2.x Was: ... mingw-cross, check-local fail for DESTDIR tests

2008-11-11 Thread Ralf Wildenhues
Hello Roumen, all, apologies for the huge delay. * Roumen Petrov wrote on Sat, May 10, 2008 at 12:25:48PM CEST: > The libtool version before 2.x (as example 1.5x) in mingw-cross > compilation environment create executables as follow: > - foo : wrapper shell script > - foo.exe : libtool wrapper

Do not use `test ... -a ...'.

2008-11-11 Thread Ralf Wildenhues
Spotted, and pushed this trivial patch. (Yes, on HP-UX all shells know this, but being consistent is easy here.) Cheers, Ralf Do not use `test ... -a ...'. * libltdl/m4/libtool.m4 (_LT_LINKER_SHLIBS) [hpux10, hpux11]: Replace test -a with test && test. diff --git a/liblt

Re: libtool(20080421), mingw-cross, check-local fail for DESTDIR tests

2008-11-11 Thread Ralf Wildenhues
Hello Charles, Roumen, * Charles Wilson wrote on Sat, Nov 08, 2008 at 05:12:18PM CET: > Roumen Petrov wrote: > > With attached patch now I get for libtool 2.2.4: > > DESTDIR tests > > 38: Simple DESTDIR install ok > > 39: DESTDIR with in-package deplibs o

Re: Simplify cwrapper handling a bit

2008-11-11 Thread Ralf Wildenhues
Hi Charles, * Charles Wilson wrote on Tue, Nov 11, 2008 at 07:14:54AM CET: > Ralf Wildenhues wrote: > > OK to apply? > > Not this bit: Thanks for the reminder, and the speedy review. I left out that hunk, fixed a couple more coding style issues, and committed this. Cheers, Ralf Simplify c

Re: [PATCH 6/6] use print or printf or cat as $ECHO (really)

2008-11-11 Thread Ralf Wildenhues
Hi Paolo, * Paolo Bonzini wrote on Mon, Nov 10, 2008 at 09:58:32PM CET: > > > > Regarding the 6/6 patch, you have posted several variants, also there > > are pending issues. For me it'd be easiest to review the final one > > when things have been hashed out; I think I've voiced all concerns tha