cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1998/06/02/12:23:55

From: pavenis AT lanet DOT lv
Message-ID: <B0000031519@stargate.astr.lu.lv>
To: djgpp AT delorie DOT com, "Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Date: Tue, 2 Jun 1998 19:22:23 +0300
MIME-Version: 1.0
Subject: Re: Compiling in 2.8.1 vs. 2.7.2.1 - two minor problems
CC: Jerzy Witkowski <Jerzy DOT Witkowski AT ii DOT uni DOT wroc DOT pl>
In-reply-to: <6kulka$8kk$1@rosenews.rose.hp.com>

From:           	"Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019