Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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 <cgf-no-personal-reply-please AT cygwin DOT com>
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> <ACE0291F-7ECF-11D8-A56E-003065C7FEA0 AT ix DOT netcom DOT com>
Mime-Version:	1.0
In-Reply-To:	<ACE0291F-7ECF-11D8-A56E-003065C7FEA0@ix.netcom.com>
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/

- Raw text -