This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Problems when env-size gets too large


Hi there!

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
	Alex Puchmayr


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]