Date: Fri, 5 May 2000 14:21:07 -0400 (EDT)
Message-Id: <200005051821.OAA05725@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: pavenis AT lanet DOT lv
CC: djgpp-workers AT delorie DOT com, snowball3 AT bigfoot DOT com
In-reply-to: <Pine.A41.4.05.10005041814380.48816-100000@ieva05.lanet.lv>
	(message from Andris Pavenis on Thu, 4 May 2000 18:26:35 +0200 (WET))
Subject: Re: minor DJGPP config change
References:  <Pine DOT A41 DOT 4 DOT 05 DOT 10005041814380 DOT 48816-100000 AT ieva05 DOT lanet DOT lv>
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

> Date: Thu, 4 May 2000 18:26:35 +0200 (WET)
> From: Andris Pavenis <pavenis AT lanet DOT lv>
>
> I see 2 possible solutions:
> 
> 	- forcing always substitute environment variable $DJDIR
>           (of course for DJGPP only: #ifdef __DJGPP__)
> 
> 	- disabling looking for relative prefix for DJGPP 
> 	  (also ifdef-ing corresponding code out in gcc.c out for DJGPP)

Is it possible to try $DJDIR, and if it fails, fall back to the other
method (which I understand uses the directory where gcc binary lives
to compute the prefix)?