Date:	Sun, 18 Apr 1999 13:50:35 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Andris Pavenis <pavenis AT lanet DOT lv>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: [binkley AT sst DOT ncsl DOT nist DOT gov: djgpp and ld]
In-Reply-To:	<B0000083641@stargate.astr.lu.lv>
Message-ID:	<Pine.SUN.3.91.990418135016.22615L-100000@is>
MIME-Version:	1.0
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

On Fri, 16 Apr 1999, Andris Pavenis wrote:

> My thoughts were directed to get some workaround for need to specify
> $DJDIR in prefix as it is not so easy to push '$' through configure files

Not easy, but nevertheless possible ;-).  IMHO, any DJGPP source
distribution should try very hard to do this, so that people who only
need to recompile without changing too much could avoid the complex
and non-trivial configure step.

Your suggestion to use an invalid name has one very large
disadvantage: it doesn't permit to produce a package that has sensible
defaults built into it.  Using "c:/djgpp" at least allows users to use
C:\DJGPP as the place where programs should work without any
environment variables.  ${DJDIR} is better, but as you know, most GNU
packages don't expand default paths at run time (although some ports,
like ID-utils and Make, were specifically changed to do just that).

- Raw text -