On Fri, Jan 09, 2009 at 06:39:27PM +0000, Luke Kenneth Casson Leighton wrote: > http://bugs.winehq.org/show_bug.cgi?id=13606 > > folks, hi, > > am running a configure script under wine, and it's _literally_ one to > two seconds per sh.exe instance. i started running ./configure over > two hours ago and there are about 100 lines of output so far, with a > further 200 to go i am better off leaving this running overnight. as > this is development work i am doing, not "building something that's > already known to work" i have to call a halt to the development, > because it is crazy to expect to have to wait four to six hours if i > make a single change to configure.in or Makefile.pre.in - god help me > if i have to run autoconf (fortunately i can do that from linux). > > ... so i did some investigation: > > strace -o log.txt -ff wine cmd > > followed by running c:\msys\msys.bat > > ignoring the fact that sh.exe crashed on me (which it doesn't do when > you don't use strace) i was able to obtain some system call usage when > firing up sh.exe, and it's _horrendous_. > > X11 keyboard files, X11 locale files, iconv, windows fonts, unix fonts > - all to fire up c:/msys/bin/sh.exe ? > > further up the strace files, i'm looking at the biggest offender and > it looks like it's reading files one byte at a time. reconstructing > some of the sentences i can make out "remember that we get here even > under command.com\r\n". ohhh i remember where i've seen that - that's > in msys.bat. .... why is it being read one byte at a time?? there are > _thousands_ of lines like this:
If it starts up the wine environment every time this might take some time. Try to keep a "notepad" open in the background so the wine environment stays running. Ciao, Marcus
