Vijay Sampath wrote:
I just tried out a line with 2 characters and it works fine on bash
as an input to GCC.
I think that direct Cygwin-to-Cygwin invocation has a higher limit. If
you're calling a Cygwin program from a non-Cygwin program (e.g.
CMD.EXE), you're still stuck with Windows limi
Vijay,
I guess I was misled by this:
/usr/include/limits.h:#define _POSIX_ARG_MAX 4096
/usr/include/sys/syslimits.h:#define ARG_MAX 65536 /* max bytes for an exec
function */
Furthermore, "/usr/include/limits.h" bears a Red Hat copyright and is
specifically marked as a "part of Cygwin," while
> Sent: Thursday, December 12, 2002 10:43 AM
> To: [EMAIL PROTECTED]
> Subject: RE: GCC Include Paths
>
>
> Vijay, Allan,
>
> Cygwin is similarly limited. All Unix / POSIX systems have
> such a limit,
> but Cygwin's limit is much smaller than the typical limit
Vijay, Allan,
Cygwin is similarly limited. All Unix / POSIX systems have such a limit,
but Cygwin's limit is much smaller than the typical limit on a Unix (-like)
system. I don't know it for a fact, but I'm pretty sure this limit is not
imposed by Cygwin itself (why would it?) but is a Windows
Yes, we have faced a similar problem. The problem is with the windows
command shell which limits a line to 2048 characters. I don't know how
to make that problem go away. But you shouldn't get the same problem
from a cygwin shell.
Thanks,
Vijay
> -Original Message-
> From: Allan Crook [m
5 matches
Mail list logo
