Date:	Mon, 14 Jun 1999 10:19:35 +0300 (WET)
From:	Andris Pavenis <pavenis AT ieva01 DOT lanet DOT lv>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Small changes to DJGPP.ENV
In-Reply-To:	<Pine.SUN.3.91.990613113000.17906S-100000@is>
Message-ID:	<Pine.A41.4.05.9906141005390.24354-100000@ieva01.lanet.lv>
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 Sun, 13 Jun 1999, Eli Zaretskii wrote:

> 
> On Fri, 11 Jun 1999 pavenis AT lanet DOT lv wrote:
> 
> > 	- there is no need for definition of COMPILER_PATH for gcc as
> > 	  at least with egcs-1.1.2 and also upcoming gcc-2.95 gcc
> > 	  already knows to search binaries in $DJDIR/bin before looking
> > 	  in DOS path. Also gcc-2.95 install cpp.exe in ${prefix}/bin
> > 	  which can be used to preprocess sources. Presence of both
> > 	  $DJDIR/bin/cpp.exe and $DJDIR/bin in COMPILER_PATH
> > 	  breaks gcc.
> 
> I think we should leave things as they are until we switch to EGCS as
> the official compiler.  Meanwhile, people who install EGCS should be
> told in the README to remove or rename the [gcc] section from DJGPP.ENV.
> 

Adding bin/cpp.exe to gccXXXb.zip will break gcc unless we'll remove
COMPILER_PATH there. I put 

#define MD_EXEC_PREFIX "$DJDIR/bin" 

in gcc-2.8.1 configuration (perhaps at last update in October 22th if I
remeber correctly. I tested it's there). So I think defining COMPILER_PATH
is not needed even for gcc-2.8.1 and of course also for egcs-1.1.2 and
it will be for gcc-2.95. 

Even if MD_EXEC_PATH is not defined only drawback is that gcc will not
search for executables in $DJDIR/bin before looking in DOS path. 

So if we leave things as they are it will be more hard to add bin/cpp.exe
if we'll need it for RSXNTDJ or something like in future. Things that can
break something should be fixed if possible. 

Andris

- Raw text -