Speeding up libtool

2005-03-14 Thread Robert Ögren
Hi everybody, I looked through the TODO thread from 2004-11 and saw some talk about speeding up libtool. I'm particularly interested in improved compilation speed on Cygwin (Windows). Is there any progress on this? A while ago I created a temporary solution for myself which caches the commands

Re: Speeding up libtool

2005-03-15 Thread Robert Ögren
Ralf Wildenhues wrote: Hi Robert, Hi Ralf, For the HEAD branch of Libtool, I have made some changes that cause it to fork less often. For the particular bad case I was looking at (linking against ~500 objects), I got it from about 11 sec to about 5 sec, both of which include 2.5 sec of time spent

Re: Speeding up libtool

2005-03-24 Thread Robert Ögren
Ralf Wildenhues wrote: Oh dear. This should be CONFIG_SHELL=/bin/ash lt_ECHO='printf %s\n' /bin/ash configure [...] instead. This seems to mess up the result of func_win32_libid with recent libtool from CVS (1.1888 2005/03/18 15:57:13). Instead of returning (echoing) x86 archive import it ec

Re: Speeding up libtool

2005-03-25 Thread Robert Ögren
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

Re: Speeding up libtool

2005-03-25 Thread Robert Ögren
I wrote: > 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'm sorry for replying to myself, but there are some compatibility issues with glib and Libtool HEAD that I

Re: Speeding up libtool

2005-03-25 Thread Robert Ögren
Hi again Ralf, I finally have some numbers for you. The script I used is available at http://libtool-cache.sourceforge.net/libtool-cache-bench.sh What it basically does is to build GLib 2.6.3 using different versions of libtool and with and without caching. As I said before, I'm usually using Cygwi

Testsuite failures on Cygwin with ECHO=printf (was: Re: Speeding up libtool)

2005-03-26 Thread Robert Ögren
Ralf Wildenhues wrote: [...] Yes. We recently identified that an audit of libtool.m4 for wrong use of $ECHO is necessary. [details left out] Another question: How did you find those bugs? I.e., were they exposed by the Libtool testsuite? If not, how can we trigger them? The testsuite triggers th

Re: Speeding up libtool

2005-03-29 Thread Robert Ögren
Ralf Wildenhues wrote: > libtool HEAD should tell you upon invocation of `autoconf -Wall' to > remove AC_LIBTOOL_WIN32_DLL in favor of adding the win32-dll option to > LT_INIT. After doing that, things should work. (But leaving things > like they are should also work.) Unfortunately AC_LIBTOOL_W

Re: Speeding up libtool

2005-04-04 Thread Robert Ögren
Hi Ralf, Ralf Wildenhues wrote: Hi Robert, First I'd like to say many thanks for all your testing and valuable feedback. Thank you for the responses. Will take a little while to work through all of it. Hehe, sorry, I had too much time on my hands last weekend and largely spent it on fiddling with

Slow shell script execution on Cygwin

2005-04-14 Thread Robert Ögren
Hi everybody, [cc:ing libtool as I started a thread about Libtool execution speed there] One thing that has annoyed me for a while is that large/complex shell scripts with a lot of forking, like configure scripts or Libtool, run quite slowly on Cygwin. I know that you have to do a lot of trickery

Re: Slow shell script execution on Cygwin

2005-04-15 Thread Robert Ögren
Hi Ralf, Ralf Wildenhues skrev: It might be of value to retry your tests with Libtool HEAD without the lt_ECHO='printf %s\n' setting. I had only later found out that cygwin's ash has a builtin echo which does not interpret backslashes. I could not find the time to test the speedup myself yet. Tha

Re: libtool stdout output format

2005-09-06 Thread Robert Ögren
Hi Ralf and others, Ralf Wildenhues wrote: As of now, the output format -- "whatever libtool prints on stdout" -- is different between the 1.5 releases and CVS HEAD. The latter prepends a string like libtool: $mode: where mode is either `compile', `link', or similar. This output has never