Re: How to avoid Max Command line size on Windows

[David Lamy-Charrier <david dot lamy at gmail dot com>]

All,

Thanks a lot for your help and your fast replies.
It's really pleasant to work with such a responsive community.

I think the best way for me would be to try the re-integrate the
changes done in the mainline to support @file into my GCC sources
(3.4.0).

For information, I am using MinGW on Windows XP Pro and the 8192 Bytes
limitation comes from there (if my understanding is correct):
http://support.microsoft.com/default.aspx?scid=kb;en-us;830473

Regards,
David



On 11/18/05, Brian Dessent <brian@dessent.net> wrote:
> Sisyphus wrote:
>
> > I thought different. To me a "command line" is something that's entered at a
> > prompt, and whilst makefiles contain commands, I've never thought of them as
> > containing "command lines". But thinking about the numbers involved (ie
> > 8192), I'm starting to think that your interpretation might be more to the
> > point than mine :-)
>
> The CreateProcess() limitation is actually 32k characters, so I'm not
> sure exactly where this 8192 limit is coming from.  I have read in the
> past where linking particularly large libraries (like libgcj) runs into
> this 32k limit, and the workaround is cygexec (or
> --enable-libgcj-multifile).  It seems like something else is imposing
> this 8k limit - and since the poster did not mention the details of his
> environment (cygwin, MSYS/mingw, etc) we probably won't know for sure.
> It might be that some autoconf test somewhere just uses 8k if it detects
> it's running under mingw, or something.
>
> Brian
>