Message-ID:	<002a01c2a305$37d5aef0$0100a8c0@p4>
From:	"Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To:	<djgpp-workers AT delorie DOT com>
Cc:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Subject:	DJGPP BUG 320
Date:	Sat, 14 Dec 2002 11:09:16 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2800.1123
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1123
Reply-To:	djgpp-workers AT delorie DOT com

In going over the outstanding DJGPP bugs still open in the BUG trackling
 system bug 320 looks like it could be closed. What is the concensus here?

 The URL is
 http://www.delorie.com/djgpp/bugs/show.cgi?000320


 The bug info is:-
 Bug 000320
 When Created: 06/06/2000 10:49:09
 Against DJGPP version: 2.03
 By whom: hko AT errel DOT com
 Abstract: problem with /dev/env/.. paths used in env variables processed by
 djgpp.env

 When setting an environment variable like C_INCLUDE_PATH to something like
 "/dev/env/XXX/include" the current version of djgpp.env will convert it to
 lower case and subsequently the variable 'xxx' (now lower case) will not be
 found.


 Workaround added: 06/06/2000 10:52:00
 By whom: hko AT errel DOT com

 Obvious workaround is to remove the lower case conversion operator ('>') in
 djgpp.env, but I'd prefer djgpp to accept lower case env variable names.


 Note added: 06/09/2000 10:32:40
 By whom: eliz AT is DOT elta DOT co DOT il

 Case-sensitive environment variables are a feature of DOS.  I don't think
we
 should break that feature (by converting all variables to a single case)
 just
 because of this marginal situation.  Such a change will certainly break
some
 code out there.

 So I don't think that making enviroenment variables case-insensitive is a
 good idea.


 Workaround added: 06/09/2000 10:38:19
 By whom: eliz AT is DOT elta DOT co DOT il

 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.



 Add a note
 Add a workaround
 Add a solution
 Close without fixing (i.e. will never be fixed)

- Raw text -