Message-ID:	<20010131093808.527.qmail@lauras.lt>
From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Wed, 31 Jan 2001 11:38:08 +0200
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Path defaults in GCC
Mail-Followup-To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	djgpp-workers AT delorie DOT com
References:	<20010130201315 DOT 511 DOT qmail AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010131100500 DOT 29266H-100000 AT is>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.12i
In-Reply-To:	<Pine.SUN.3.91.1010131100500.29266H-100000@is>; from eliz@is.elta.co.il on Wed, Jan 31, 2001 at 10:06:49AM +0200
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

> 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. The problem is
that compiler driver does not see standard paths, if called with a different
name. The path expansion code simply does not get any path to play with.

> As for the changes, please make sure they don't break the cross-build 
> environment, both when building GCC as a native or cross-compiler, and 
> when using it later on a Unix box.

Thanks for pointing this out - indeed some minor tweaking will be required
for not losing /usr/local/lib/gcc-lib/ path for a DJGPP-target compiler.
DJGPP hosted compiler should be OK, because all those paths are defined
as target macros only.

Laurynas

- Raw text -