Date:	Wed, 31 Jan 2001 15:16:54 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	pavenis AT lanet DOT lv
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Path defaults in GCC
In-Reply-To:	<3A78212E.26594.6CD80A@localhost>
Message-ID:	<Pine.SUN.3.91.1010131151109.2010A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 31 Jan 2001 pavenis AT lanet DOT lv wrote:

> Development version of gcc-2.97 tries to find real prefix from location
> of gcc binary so I think it's no more problem.

I'm confused: what is the role of the code that Laurynas just posted, 
which uses /dev/env/DJDIR?  Is it used before or after looking in 
directories relative to gcc.exe's location?

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

Relative prefix is okay, but it doesn't solve all problems.  For example, 
it gets in your way if you want to have several versions of gcc, like 
gcc-2.7.2.exe, gcc-2.8.1.exe, gcc-2.95.exe, etc. in the same directory.

In other words, relative prefix forces you to segregate different 
versions into separate directories.  This is annoying, since it bloats 
PATH and requires several copies of include directories and libraries.

So I think it is still useful to have the /dev/env-relative prefix.

- Raw text -