rry
-Original Message-
From: Jörg Schaible [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 2:53 AM
To: [EMAIL PROTECTED]
Subject: RE: Limit to length of command line arguments? (was Cygwin/bash:
need environment variables >32K)
Hi Barry,
Buchbinder, Barry (NIH/NIAID) wrote
On Thu, 23 Oct 2003, Nicolas BUONOMO wrote:
> Corinna Vinschen a ecrit :
>
> > On Thu, Oct 23, 2003 at 11:39:39AM +0200, david.liberce wrote:
> >
> >>I reproduce this behaviour.
> >>
> >>Looks like the PATH environment variable is not valid anymore after $VAR
> >>has been asigned?
> >
> >
> > Nop
Corinna Vinschen a écrit :
On Thu, Oct 23, 2003 at 11:39:39AM +0200, david.liberce wrote:
I reproduce this behaviour.
Looks like the PATH environment variable is not valid anymore after $VAR
has been asigned?
Nope. I debugged this situation. It looks like a Windows restriction.
When trying
Corinna Vinschen a écrit :
On Thu, Oct 23, 2003 at 11:39:39AM +0200, david.liberce wrote:
I reproduce this behaviour.
Looks like the PATH environment variable is not valid anymore after $VAR
has been asigned?
Nope. I debugged this situation. It looks like a Windows restriction.
When trying
On Thu, Oct 23, 2003 at 11:39:39AM +0200, david.liberce wrote:
>
> I reproduce this behaviour.
>
> Looks like the PATH environment variable is not valid anymore after $VAR
> has been asigned?
Nope. I debugged this situation. It looks like a Windows restriction.
When trying to call CreateProce
Davied wrote:
>I reproduce this behaviour.
>
>Looks like the PATH environment variable is not valid anymore after $VAR
>has been asigned?
>
>David
No, it cannot start external programs. The error message is
bash: /usr/bin/ls.exe: Invalid argument
All internal commands I have tested work.
echo
x27;
Objet : RE: Cygwin/bash: need environment variables >32K
I have no long command line!
In my environment most Cygwin executables do not work,
if long environment variables are set (resp. exported).
Please have a look at my very short example below.
First I create an environment variable V
king fine!
Can anyone reproduce this behaviour?
It is really critical for the use of Cygwin in out project ;-)
Thanks
Andre
-Original Message-
From: Buchbinder, Barry (NIH/NIAID) [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 22. Oktober 2003 15:53
To: 'Klein Andre ICM N AS PD B 3'
Hi Barry,
Buchbinder, Barry (NIH/NIAID) wrote on Thursday, October 23, 2003 12:43 AM:
> While doing some other work, I've come to the impression that
> this is not a fileutils problem. In a directory with ~1700
> htm files whose names take 37k,
> $ ls *
> bash: /bin/ls.exe: Invalid argument
>
consideration.
- Barry Buchbinder
-Original Message-
From: Buchbinder, Barry (NIH/NIAID)
Sent: Wednesday, October 22, 2003 9:53 AM
To: 'Klein Andre ICM N AS PD B 3'; '[EMAIL PROTECTED]'
Subject: RE: Cygwin/bash: need environment variables >32K
It may be a comman
Original Message-
From: Klein Andre ICM N AS PD B 3 [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2003 7:16 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Cygwin/bash: need environment variables >32K
Thanks for your answer!
I've tried to make the example more simple (s. at
Sent: Mittwoch, 22. Oktober 2003 12:01
To: '[EMAIL PROTECTED]'
Subject: Re: Cygwin/bash: need environment variables >32K
On Wed, Oct 22, 2003 at 11:30:54AM +0200, Klein Andre ICM N AS PD B 3 wrote:
> I need to set a very long environment variable CLASSPATH within Cygwin
bash.
>
On Wed, Oct 22, 2003 at 11:30:54AM +0200, Klein Andre ICM N AS PD B 3 wrote:
> I need to set a very long environment variable CLASSPATH within Cygwin bash.
> But there seems to be an upper limit of 32K for environment variables!?!?
>
> Is there any way to increase this upper limit?
>
> I have att
I need to set a very long environment variable CLASSPATH within Cygwin bash.
But there seems to be an upper limit of 32K for environment variables!?!?
Is there any way to increase this upper limit?
I have attached 2 small files for demonstrating the problem.
Start run.sh and the invocation of the
14 matches
Mail list logo
