Date: Mon, 26 Aug 1996 14:31:31 +0200 (METDST)
From: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
To: DJ Delorie <dj AT delorie DOT com>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Binutils 2.7
In-Reply-To: <199608231742.NAA00670@delorie.com>
Message-Id: <Pine.HPP.3.91.960826141309.10171A-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 23 Aug 1996, DJ Delorie wrote:

> Where does the stub come from?  I'd rather not have it hard coded in
> the linker image if there is a way to allow the user to read it from a
> file.
>

Currently it is hardcoded in the BFD library, but I will try to find a
way of reading it from a file. But here is the next problem/question.
From which file?? In the current DJGPP distribution is no such file.
Should it be read from a file with a fixed name or take the filename
from an environment variable and if all of this fails, take the hardcoded
stub?
 
> If it automatically puts the stub on executables, and gdb can still
> read those executables, why change the name?  Just make it the default
> behavior.
>

If you mean, that the linker should produce every time an .exe file,
this is correct. But what about people, who want to get a raw COFF
image? In this case you must tell ld the correct bfd-output-format and
so you need two different targets and names for them.
 
> The difference is leading underscores.  coff-i386 doesn't use them;
> coff-go32 does.
>

Ah.