Hello Christopher, Thanks for the bug report.
* Christopher Hulbert wrote on Wed, Jun 14, 2006 at 03:49:06PM CEST: > I don't think this is a libtool bug, but I thought I would not this. We have planned to use response files on w32 at one point, FWIW. > I was compiling a library with 1635 object files into a static > archive. The cygwin command shell fails with: What's the command? `ar cru ...'? How long exactly is the command line, and why did the command line length limit max_cmd_len=8192 setting not trigger a multiple archiver invocation? All these questions may be answered by the output of ./libtool --debug [rest of command line] >log 2>&1 and sending the log file (please bzip2 or gzip). Erm, please also tell us the size of your environment (`env | wc'); I don't remember off-hand whether that was part of the limit on Cygwin. > 5 [main] sh 3668 C:\cygwin\bin\sh.exe: *** fatal error - fork: > can't reserve memory for stack 0x23E660 - 0x240000, Win32 error 487 > 6 [main] sh 2896 child_copy: stack write copy failed, > 0x23E660..0x240000, done 0, windows pid 2352532, Win32 error 5 > ../libtool: fork: No error > make: *** [libvsip.la] Error 129 Hmm. Is that a typical command line limitation error even? Maybe your system just ran out of virtual memory? (I don't know Cygwin that well off-hand.) > This seems to be correlated with so many object files. I remember > seeing libtool at one point somewhere else trying to do partial > linking. Would there be a way to do something similar when there are > so many object files? Yes, and all that machinery should be in place. > Currently After it fails I just manually go > into the directory and run ar cru .libs/libvsip.a *.o and it seems to > work fine. This is really weird. Is this a recent Cygwin? Which w32 system on? Cheers, Ralf _______________________________________________ Bug-libtool mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-libtool
