From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Tue, 16 May 2000 09:24:59 -0400
MIME-Version:	1.0
Subject:	Re: Fw: DJGPP config changes part 2 of 2
Message-ID:	<392113EB.12560.1376E8@localhost>
References:	<39204A70 DOT 12816 DOT 84C5F5 AT localhost>
In-reply-to:	<Pine.SUN.3.91.1000516145137.24814V-100000@is>
X-mailer:	Pegasus Mail for Win32 (v3.12c)
Reply-To:	djgpp-workers AT delorie DOT com

> Could you please explain why does GCC need to know about the /dev/env
> magic?  After all, the library will do that for it when /dev/env is
> used in a file name, no?
> 

GCC sets the various paths it needs based on the prefix you use when 
configure. But configuring with $DJDIR requires modifying the configure 
script as Andris has already noted. This patch makes it possible to use 
'/dev/env/DJDIR/' as the prefix which requires no modifications. The patch 
translates '/dev/env/DJDIR/' to canonical form because there is a routine in 
gcc that compares paths and generates a relative path. Comparing a path like 
'c:/foo/bar' to '/dev/env/DJDIR' is obviously not a good idea. Then the other 
paths generated because of the comparison (that are seen with 'gcc -print-
search-dirs') will be out of whack. That same kind of translation is already 
done in gcc 2.95.2 and earlier with '$DJDIR', so it's really just replacing 
one kind of translation with another kind.

- Raw text -