[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PATH vs. Path ([Fwd: Returned mail: see transcript for details]

From: Earnie Boyd
Subject: Re: PATH vs. Path ([Fwd: Returned mail: see transcript for details]
Date: Wed, 2 Mar 2005 20:54:38 -0500 (EST)
User-agent: SquirrelMail/1.4.3a

<quote who="Eli Zaretskii">
> Bash uses PATH, of course.  But it strikes me as a grave bug of the
> MinGW port of Bash that it doesn't convert Path to PATH, because Unix
> shell scripts use PATH, and will choke if it's not found.  Too bad we
> need to cope with such a port.

For correction and clarification both Cygwin and MSYS (MinGW's bash) do
convert Path to PATH else nothing would work correctly without the
headaches of dealing with Path vs PATH in every ported tool.

This thread however, should only discuss make without the use of our UNIX
emulation friends.  Therefore, for that senario, we must convert Path to
PATH in make.  Hmm...  Looking at the result of envoking cmd.exe from MSYS
and executing ``set'' I see that all environment variable names have been
uppercased and remain that way in the spawned child.

So, based on my discovery with MSYS and therefore Cygwin, I'm in favor of
John Calcote's patch to uppercase all environment variable names for the
Windows build.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]