From:	fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson)
Subject:	Re: env command does not work correctly.
4 Apr 1997 06:39:18 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199704040414.OAA28834.cygnus.gnu-win32@mundook.cs.mu.OZ.AU>
Original-To:	john AT rrci DOT com (John D. Robertson)
Original-Cc:	gnu-win32 AT cygnus DOT com (gnu-win32)
In-Reply-To:	<Pine.LNX.3.91.970403090237.294B-100000@localhost> from "John D. Robertson" at Apr 3, 97 09:08:37 am
X-Mailer:	ELM [version 2.4 PL24]
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

John D. Robertson, you wrote:
> 
> I downloaded the cygnus SDK yesterday, and I am very pleased that these 
> tools have been ported to Win32.  I soon attempted to port my tools that 
> run under Linux and Irix to gnu-win32, and I ran into a problem.
> 
> The "env" command does not set environmental variables as it is supposed 
> to.  For example:
> 
>    env ONE=one TWO=two echo_1_2
> 
> where echo_1_2 is a sh script:
> 
>    #!/bin/sh
>    echo $ONE $TWO
> 
> 
> will print nothing.

I don't know why env doesn't work, but exporting variables from bash
does seem to work, so as a workaround I would try something like this:

	#!/bin/sh
	# shell script replacement for gnu-win32 broken `env' command
	eval "$@"

Well, that probably stuffs up quoting, but you get the idea...

> I have also noticed that it is not possible to 
> export lower case environmental variable at all.  I have seen this 
> elsewhere in the list.

That one, and a few others, are listed on
<http://www.cs.mu.oz.au/~fjh/gnu-win32/bugs-list.html>.

-- 
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3         |     -- the last words of T. S. Garp.
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -