Message-ID:	<20010131114652.357.qmail@lauras.lt>
From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Wed, 31 Jan 2001 13:46:52 +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:	<20010131093808 DOT 527 DOT qmail AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010131130833 DOT 1051C-100000 AT is>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.12i
In-Reply-To:	<Pine.SUN.3.91.1010131130833.1051C-100000@is>; from eliz@is.elta.co.il on Wed, Jan 31, 2001 at 01:12:54PM +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

> 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.

OK then, sorry for not being clear.

Laurynas

- Raw text -