Date: Sat, 14 Dec 2002 11:20:36 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: acottrel AT ihug DOT com DOT au
Message-Id: <7443-Sat14Dec2002112036+0200-eliz@is.elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <002a01c2a305$37d5aef0$0100a8c0@p4> (acottrel@ihug.com.au)
Subject: Re: DJGPP BUG 320
References:  <002a01c2a305$37d5aef0$0100a8c0 AT p4>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
> Date: Sat, 14 Dec 2002 11:09:16 +1100
> 
>  One obvious work-around (or even a solution?) would be not to use /dev/env
>  in environment variables.  There should be no need for this: you could
>  simply
>  say %FOO% instead of /dev/env/FOO.
> 
>  /dev/env exists to pacify programs that hard-code file names into the
>  binaries
>  when they are built; using /dev/env/FOO defers the environment variable
>  expansion till run time, instead of having the file names from the build
>  machine, which might not work on other machines.

I think this can be closed, allright.  I wonder why I didn't close it
myself after adding this note...