This is the mail archive of the
mailing list for the Cygwin project.
Re: Problems when env-size gets too large
This isn't a Cygwin limitation. It's a Windows limit of 32k
environment size. There's no way around it except to limit
the number of variables you export. I've run into the same
problem, but with large Bash functions (which are included
in the environment). My solution was to not export any
On Mar 24, 2004, at 3:48 AM, Puchmayr Alexander AIS-A.Services wrote:
The project I'm currently working on defines a really large number of
environment variables, and I think this is the reason why I always get
the error "Resource temporarily unavailable" when I try to start *any*
command. When I do not start that large script, cygwin works fine,
except that my project specific build-scripts, which need these
environment variables, do not work.
So, is there any possibility to increase the environment size or any
other workaround that makes cygwin usable in my environment?
Thanks in advance
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html