From: pavenis AT lanet DOT lv Message-ID: To: djgpp AT delorie DOT com, "Andrew Crabtree" Date: Tue, 2 Jun 1998 19:22:23 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Compiling in 2.8.1 vs. 2.7.2.1 - two minor problems CC: Jerzy Witkowski In-reply-to: <6kulka$8kk$1@rosenews.rose.hp.com> Precedence: bulk From: "Andrew Crabtree" Subject: Re: Compiling in 2.8.1 vs. 2.7.2.1 - two minor problems Date sent: Mon, 1 Jun 1998 09:41:45 -0700 > > Nate Eldredge wrote in message > <19980529235344 DOT AAC16281 AT ppp116 DOT cartsys DOT com>... > >>First, the way gcc calls other programs changed. > >>after first compilation, when `as.exe' exists in the current > >>directory it is called by `gcc' instead of assembler program (with > >This would seem to be a bug in 2.8.1. 2.7.x uses the COMPILER_PATH This can be easily fixed by telling gcc to look in $DJDIR/bin after looking in version specific directories ($DJDIR/lib/gcc-lib/djgpp/2.81). Simply add line #define MD_EXEC_PREFIX "$DJDIR/bin/" in gnu/gcc-2.81/config/i386/xm-go32.h before compiling gcc and this problem goes away. (I copied find.exe to current directory with name as.exe but patched gcc.exe was working perfectly anyway) > Actually, this is more of a feature. It makes it more similar to unix style > gcc. Type 'gcc -print-search-dirs' to see where it is searching. It > actually uses a target/version system first, and then falls back on others. > Don't know why it is searching the current directory though. I would avoid > the cpp, cc1, cc1plus, ld, ... names as suggested. > As I told above this problem is fixed in version on my HDD. Andris