* Robert Ögren wrote on Fri, Apr 15, 2005 at 01:01:39AM CEST:
I know that slow doesn't really mean anything, so here are some numbers:
Running the configure script for glib-2.6.3 (from ftp.gtk.org) takes
around 170 seconds on Cygwin on my machine, with antivirus software
disabled.
Just throwing out (or throwing up ;-) some ideas...:
Has anybody investigated using busybox on Cygwin? Or something
similar? I.e. binding the code for the most common GNU utitilies (sed,
m4, gawk, expr, cp, cat, ls, rm, ln, echo) more tightly to the shell,
perhaps building them as DLLs, and
Tor Lillqvist wrote:
Hmm, but I guess the fork/exec separation makes this harder, Cygwin
can't know when it is emulating fork() whether the child process will
immediately exec() one of the above. Or does the Cygwin shell(s)
already have some special code instead of plain fork()/exec()?
I
Brian Dessent wrote:
It seems clear that Cygwin would benefit from some kind of special
casing in the shell because of the fork penalty, but apparently
no one has the time or is capable of providing this, if it's even feasible.
Uhh, nevermind. Upon checking it seems that all the old vfork
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.
