Date: Sat, 07 Jul 2001 17:12:16 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
Message-Id: <1438-Sat07Jul2001171216+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <CAEGKOHJKAAFPKOCLHDIIEDFCFAA.tim.van.holder@pandora.be>
Subject: Re: Upload of gcc-3.0 archives
References:  <CAEGKOHJKAAFPKOCLHDIIEDFCFAA DOT tim DOT van DOT holder AT pandora DOT be>
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

> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> Date: Sat, 7 Jul 2001 13:48:10 +0200
> 
> I'd like one more feature: gcc3 is currently configured with /dev/env/DJDIR
> as prefix (as it should be), but it tends to display the expanded path.
> I'd like to see this changed so it uses /dev/env/DJDIR in output as well,
> especially in -print-prog-name (as that is used by libtool to determine the
> ld used by gcc, resulting in a non-portable cache value).

I don't think changing that is a good idea.  /dev/env/DJDIR is
something you know in advance, so you can simply force libtool to use
it (e.g., by setting the value of the cache variable).

The reason I think printing /dev/env/DJDIR might be bad is that the
output could be used for comparing file names, or seeing if some
directory is a child of the DJGPP installation.  It also doesn't tell
what's the value of DJDIR on the target machine, which might hurt
debugging user problems.

So I think the fact that it prints the expanded directory is a
valuable feature, not a bug.

> BTW, the last build (in alphas/) prints 'ld' instead of
> $DJDIR/ld.exe when asked for the location of ld, which I think is a
> bug.

Yes, I see that, too...  It seems like it only recognizes programs
that are in lib/gcc-lib/djgpp/3.0/, but does not look along the PATH,
because the moment you copy ld.exe to that directory, it is
recognized.