Date:	Wed, 1 Jul 1998 12:20:51 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	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:	<Pine.SUN.3.91.980701110656.12487D-100000@is>
Message-ID:	<Pine.LNX.3.93.980701121045.12497A-100000@acp3bf>
MIME-Version:	1.0

On Wed, 1 Jul 1998, Eli Zaretskii wrote:

> On Tue, 30 Jun 1998, Hans-Bernhard Broeker wrote:
> 
> > Maybe a little change to the gcc
> > sources, switching the order of searching, so that $LIBRARY_PATH
> > and $C_INCLUDE_PATH are searched after the version-specific 
> > directories.
> 
> IMHO, making the DJGPP port behave differently from the Unix version
> is a bad idea.  It invalidates the description in the docs of the
> search process and the experience of those who use gcc on several
> platforms.

But the current way is also not Unix-like, and not what you would
expect by reading the gcc docs. Let me summarize the two situations, 
where the letters in front of the directory names mean the class of
directory:

1) Unix search order in the default gcc installation (/include and /lib
subdirs in each of these will be searched), rough outline: 

a) $(C_INCLUDE_PATH) or $(LIBRARY_PATH)    -- (if set)
b) /usr/local/lib/gcc-lib/i586-linux/2.7.2
c) /usr/local  -- maybe
c) /usr

2) DJGPP, current setup, with gcc-2.81:
a) $(DJDIR), via setting of $(C_INCLUDE_PATH) and $(LIBRARY_PATH)
b) $(DJDIR)/gnu/gcc-2.81 
c) /usr -- usually inexistant!

So my question is this: why not change the default DJGPP.ENV and
make DJGPP versions of gcc automagically use $(DJDIR) whenever
they would normally use /usr, i.e. use the DJGPP directory
in class 'c)', not 'a)'?

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -