From:	pavenis AT lanet DOT lv
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Wed, 31 Jan 2001 14:29:02 +0200
MIME-Version:	1.0
Subject:	Re: Path defaults in GCC
Message-ID:	<3A78212E.26594.6CD80A@localhost>
References:	<20010131093808 DOT 527 DOT qmail AT lauras DOT lt>
In-reply-to:	<Pine.SUN.3.91.1010131130833.1051C-100000@is>
X-mailer:	Pegasus Mail for Win32 (v3.12c)
Reply-To:	djgpp-workers AT delorie DOT com

On 31 Jan 2001, at 13:12, Eli Zaretskii wrote:

> 
> On Wed, 31 Jan 2001, Laurynas Biveinis wrote:
> 
> > > Didn't GCC have some special code to expand $DJDIR at runtime, written
> > > by Robert Hoehne when /dev/env didn't exist yet?
> > 
> > I don't understand why DJDIR expansion is relevant here.
> 
> I thought you were asking how did GCC find its auxiliary files and 
> libraries without the /dev/env paths present in the sources.  I tried to 
> explain this by special code added by Robert to construct those paths
> from what getenv("DJDIR") returned.  IIRC, that is the reason why GCC
> refuses to run if DJGPP or DJDIR are not defined in the environment.
> 

Development version of gcc-2.97 tries to find real prefix from location
of gcc binary so I think it's no more problem. However it may be usefull
to leave these checks in to force poeple to fix broken installations

About the test for DJGPP and DJDIR environment variables. 
At time of gcc-2.8.1 gcc went into infinite loop while trying to
expand when DJDIR was not defined. Therefore I added check
for environment variables to refuse to work if these variables are not 
defined. 

Now we have also another example: MINGW port of gcc-2.95.2 uses 
	relative prefix like gcc-2.97


Andris

- Raw text -