This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: 1.3.4: error in inheriting new PATH environment form WIN32 executable to cygwin executable
- To: cygwin at cygwin dot com
- Subject: Re: 1.3.4: error in inheriting new PATH environment form WIN32 executable to cygwin executable
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Wed, 7 Nov 2001 14:09:33 -0500
- References: <OF4C6A95E3.F945D816-ONC1256AFD.0048D132@lossburg.arburg.com>
- Reply-To: cygwin at cygwin dot com
On Wed, Nov 07, 2001 at 02:33:08PM +0100, Heiko_Elger@arburg.com wrote:
>Hello,
>
>I have the following problem:
>
>If a MS WIN 32 program changes his environment PATH variable to a very long
>value (over 270 characters) and than calling a CYGWIN program per system() call
>the path inside the CYGWIN program is reset to NULL! If it calls a MS WIN 32
>program all works fine.
>
>We have this problem with clearmake in exporting a very long path and the shell
>is the CYGWIN sh.exe.
>
>I tried to reproduce it within a very small test.
>I wrote two small programs (belwo you wil find the sourcecode):
> changeenv.c --> MS WIN 32 program which change his PATH environment and calls
>per system() the program "printpath"
> printpath.c --> prints the PATH environment to stdout
Cygwin expects path spec components will be no more than MAX_PATH in length.
MAX_PATH == 260. This is a Microsoft constant.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/