Date:	Thu, 4 May 2000 18:26:35 +0200 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp-workers AT delorie DOT com, "Mark E." <snowball3 AT bigfoot DOT com>
Subject:	Re: minor DJGPP config change
In-Reply-To:	<Pine.SUN.3.91.1000504180442.19648B@is>
Message-ID:	<Pine.A41.4.05.10005041814380.48816-100000@ieva05.lanet.lv>
MIME-Version:	1.0
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

On Thu, 4 May 2000, Eli Zaretskii wrote:

> 
> On Thu, 4 May 2000, Andris Pavenis wrote:
> 
> > Really it was so: gcc-2.96 didn't found $DJDIR/lib as gcc tried to use relative
> > prefix.
> 
> Could you please explain this a bit more in detail?  I'm not sure I 
> understand: are you telling that there was a bug in GCC 2.96 which caused 
> it to think $DJDIR/lib was a relative path name?  If so, is that 
> corrected in current development sources?
> 

There are some hacks in gcc.c from gcc-2.96 snapshots to get gcc binaries
which can be installed anywhere (prefix is determined at runtime from actual 
location of gcc executable). This relative prefix overrides the default
one which is $DJDIR (of course)

For the other side gcc/prefix.c substitutes environment variable at start
of some file location only if it begins with prefix (which now is
determined at runtime and of course doesn't more begin with $DJDIR)

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)

Andris 

PS. There is no similar problems with gcc-2.95.2. And also the problem
    with LD_LIBRARY_PATH can remain unnoticed unless one removed
    definition of this enviroment variable from DJGPP.ENV

- Raw text -