From: Andris Pavenis <pavenis AT latnet DOT lv>
To: "Mark E." <snowball3 AT bigfoot DOT com>, gcc-patches AT gcc DOT gnu DOT org
Subject: Re: minor DJGPP config change
Date: Thu, 4 May 2000 15:09:34 +0200
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <39107C3D DOT 15159 DOT 146256 AT localhost> <39113D62 DOT 31730 DOT 4F9FF AT localhost>
In-Reply-To: <39113D62.31730.4F9FF@localhost>
Cc: djgpp-workers AT delorie DOT com
MIME-Version: 1.0
Message-Id: <00050415203200.23536@hal>
Content-Transfer-Encoding: 8bit
Reply-To: djgpp-workers AT delorie DOT com

On Thu, 04 May 2000, Mark E. wrote:
> > One bad thing with setting  MD_EXEC_PREFIX to DJGPP binaries directory is that
> > we cannot more install cpp.exe there (the one which normally goes into
> > $prefix/bin). 
> 
> Thanks. Would it be better to just delete it?

Maybe

At least some long time ago there were discussion that gcc will break if
current directory will contain as.exe or ld.exe. Therefore MD_EXEC_PREFIX=$DJDIR/bin
were used. Maybe we can get rid of it. 

One more suggestion:

When testing gcc-2.96 for DJGPP I suggest to comment out LIBRARY_PATH in
DJGPP.ENV.  In earlier message I wrote nonsense about problems with searching
include files:

Really it was so: gcc-2.96 didn't found $DJDIR/lib as gcc tried to use relative
prefix. It seems that it is the same problem You met with MD_EXEC_PREFIX

Andris