Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 25 Mar 2004 21:53:08 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Problems when env-size gets too large Message-ID: <20040326025308.GA17415@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <2489378D03C2CB45A7CEB4F53F40F93F05367371 AT lnzvt-mxs0001 DOT vaig DOT vads DOT cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Thu, Mar 25, 2004 at 09:45:43PM -0500, Mike Sieweke wrote: >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 functions. Actually, you may be able to work around the problem by mounting the directory containing the executable (or even the executable itself) with the -X option: mount -X c:\somewhere\bin /somewhere/bin This will cause cygwin to use only its own conventions for passing arguments and environment variables, bypassing any Windows limits. cgf -- 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/