Date: Tue, 16 May 2000 10:14:09 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Fw: DJGPP config changes part 2 of 2
In-Reply-To: <39204A70.12816.84C5F5@localhost>
Message-ID: <Pine.A41.4.05.10005161008020.26162-100000@ieva06.lanet.lv>
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 Mon, 15 May 2000, Mark E. wrote:

> This is part 2 of what I'm planning to send to the gcc maintains. Let me know 
> of any problems you find.
> 
> --------------------------------------------
> 
> This is the one with the more ambitious set of changes. The biggest change is 
> that it allows hosts to provide their own canonicalization routine to 
> update_path in prefix.c. DJGPP then uses this to canonicalize 
> '/dev/env/DJDIR/foo/bar/' to 'c:/djgpp/foo/bar/' (assuming DJDIR is set to 
> c:/djgpp). Previously, one would use something like 'sh ./configure --
> prefix=\$\{DJDIR}', but it's almost impossible for ${DJDIR} to survive 
> without being evaluated.
> 

There was one hack how to push ${DJDIR} through recursive makefiles I took
from sources of GNU Pascal and used in port of gcc-2.95.2 to DJGPP.

Anyway runtime conversion of /dev/env/DJDIR to $DJDIR (so gcc and other
programms sees value of $DJDIR instead) is of course better than trying
to force ${DJDIR} not to be evaluated. 

Andris