Date:	Fri, 23 Aug 1996 13:42:21 -0400
From:	dj (DJ Delorie)
Message-Id:	<199608231742.NAA00670@delorie.com>
To:	robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<Pine.HPP.3.91.960823161523.25987E-100000@newton.mathematik.tu-chemnitz.de> (message from Robert Hoehne on Fri, 23 Aug 1996 16:23:03 +0200 (METDST))
Subject:	Re: Binutils 2.7

> Now I found a way, to allow the BFD library for reading and
> writing stubbed COFF images (.exe files). Now I have question:

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.

> How should this target be called? I named it 'go32stubbed-coff', but
> this name seems to be too long.

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.

> And on other question: Why is the normal COFF target for DJGPP
> called 'coff-go32' and not 'coff-i386'? As far as I saw at the
> code, there is no big difference between these two targets but
> there are is many work when building the targets on a cross
> platform (on linux the configuration for the 'coff-i386' target
> work).

The difference is leading underscores.  coff-i386 doesn't use them;
coff-go32 does.

- Raw text -