Hi Ralf,
> Ralf Wildenhues wrote: ...
Yes. We recently identified that an audit of libtool.m4 for wrong use of $ECHO is necessary.
Oops, I glanced over the thread index for the patches list but missed that conversation.
If you have time to produce a patch to this extent for the system(s) you can test, that would be great! If not -- could I ask the favor to test a patch on your systems? I will try to produce one by next week unless anyone beats me to it.
I can provide a patch for the specific cases that gave me trouble if that's good enough. And I can test a patch that you create. But first I want to get the benchmark thingie finished. Hopefully later today if nothing unexpected happens.
Another question: How did you find those bugs? I.e., were they exposed by the Libtool testsuite? If not, how can we trigger them?
I just configured and built glib-2.6.3 (from ftp://ftp.gtk.org/pub/gtk/v2.6/) on Cygwin with
export SHELL=/bin/sh
export CONFIG_SHELL=/bin/sh
export lt_ECHO='printf %s\n'
I don't know if it happens with the testsuite. I did start it after building Libtool but must admit I got impatient and didn't let it finish. I didn't run it with sh (ash) either. But I will try to do that soon.
Anyway, the problems I experienced are in Win32-specific code paths, so you need to run under Cygwin or similar to reproduce them.
Robert
_______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
