Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Jerzy Witkowski <Jerzy DOT Witkowski AT ii DOT uni DOT wroc DOT pl>, djgpp AT delorie DOT com
From: Nate Eldredge <nate AT cartsys DOT com>
Subject: Re: Compiling in 2.8.1 vs. 2.7.2.1 - two minor problems
Date: Fri, 29 May 1998 16:53:58 -0700
Message-ID: <19980529235344.AAC16281@ppp116.cartsys.com>
Precedence: bulk

At 02:19  5/29/1998 +0200, Jerzy Witkowski wrote:
>Since the introduction of 2.8.1 version of gcc I found two
>differences in the way it compiles programs.  
>
>First, the way gcc calls other programs changed.  I had a little
>program called `as.cc' in one of my projects and it worked.  Now
>after first compilation, when `as.exe' exists in the current
>directory it is called by `gcc' instead of assembler program (with
>poor results).  I had to change the name of my `as.cc' to
>something else.  I'm slightly afraid what other names are in
>danger?

This would seem to be a bug in 2.8.1. 2.7.x uses the COMPILER_PATH
environment variable from DJGPP.ENV to find the assembler, linker, etc, and
that should only have $DJDIR/bin.

Somebody who has 2.8.1 will have to investigate why this takes place. Until
then, avoid the names `cpp', `cc1*', `as', `ld', and `stubify'.

>Second, in 2.7.2.1, after compilation with a command `gcc a.c -o
>a' there were two files left: `a' and `a.exe' (image and stubified
>image, both rather big, second slightly bigger).  Now these two
>files are identical (both are stubified).  Is it intended
>behaviour or simple side effect?

That also would seem to be a bug. Is it possible your specs file is somehow
broken? I believe GCC 2.8.x uses a builtin (and usually wrong) specs when it
can't find the real one.

Nate Eldredge
nate AT cartsys DOT com