Date: Thu, 2 Jul 1998 16:52:26 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bill Currie <bill AT taniwha DOT tssc DOT co DOT nz>
cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>,
        Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>,
        Andris Pavenis <pavenis AT lanet DOT lv>,
        djgpp workers list <djgpp-workers AT delorie DOT com>
Subject: Re: Some notes about DJDEV202.ZIP
In-Reply-To: <359B7286.9BFF0483@taniwha.tssc.co.nz>
Message-ID: <Pine.SUN.3.91.980702164558.17900D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 2 Jul 1998, Bill Currie wrote:

> Umm, then just what is the problem? if 2.8 looks in the right places
> (with $DJDIR/* coming after the version dependent dirs, and 2.7x only
> looks in $DJDIR/*, then I can't see any room for incompatabilities.

The problem is that gcc before 2.8 did NOT look in any directory relative 
to $DJDIR.  It was *forced* to look inside $DJDIR/* by setting 
environment variables in DJGPP.ENV.

This makes problems with 2.8.x, since directories set by the environment 
variables are searched *before* the built-in ones.  So, if DJGPP.ENV is 
left as it is in v2.01, gcc 2.8.x will look in $DJDIR/* first, and find 
there wrong files.

> Ach, the only solutions I can see (probably unacceptable)
> are either for 2.8x to ignore LIBRARY_PATH and C_INCLUDE_PATH

This is IMHO unacceptable.  The *_PATH variables are meant to allow users 
to augment the search tree with directories specific to the local setup.  
We cannot deprive them of this freedom.

It just so happens that gcc before 2.8 was set up by using those 
directories, because we couldn't trust the compiled-in defaults.