Date: Wed, 31 Jan 2001 13:12:54 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Path defaults in GCC
In-Reply-To: <20010131093808.527.qmail@lauras.lt>
Message-ID: <Pine.SUN.3.91.1010131130833.1051C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Wed, 31 Jan 2001, Laurynas Biveinis wrote:

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

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.

> The problem is that compiler driver does not see standard paths, if 
> called with a different name.

I didn't understand you were talking about xgcc.  I don't think your 
message indicated that the problem was limited to building GCC.  I 
thought the question was about running GCC after it is already built.