Date: Tue, 20 Apr 1999 10:41:44 -0400
Message-Id: <199904201441.KAA10263@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il
CC: pavenis AT lanet DOT lv, djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.990420115928.841F-100000@is> (message from Eli
	Zaretskii on Tue, 20 Apr 1999 11:59:48 +0300 (IDT))
Subject: Re: [binkley AT sst DOT ncsl DOT nist DOT gov: djgpp and ld]
References:  <Pine DOT SUN DOT 3 DOT 91 DOT 990420115928 DOT 841F-100000 AT is>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Because ${DJDIR} works even for those who do NOT install it in /djgpp
> (like myself ;-).

For packages that can dymanically find where djgpp is installed,
great.  We're all set.  For the rest, which hard-code a static path, I
suggest we hard-code /djgpp instead of /usr/local or whatnot.
Sometimes it may help, but at least it won't conflict with other gcc
ports.  In any case, we can't rely on it actually pointing to where
djgpp really is installed - we must rely on environment variables,
argv[0], or something else dynamic.

My only purpose in this suggestion is to ensure that the hardcoded
paths fail to accidentally pick up some non-djgpp package.