Date: Tue, 27 Jun 2000 15:39:11 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Ben Chong <bluesky6 AT ix DOT netcom DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Modifying ld for standalone binaries
In-Reply-To: <envflscd08chm650chapqv64s38o3etn1c@4ax.com>
Message-ID: <Pine.SUN.3.91.1000627153853.19259L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 26 Jun 2000, Ben Chong wrote:

> After looking at the a.out file, I noticed that there is a huge go32
> stub. Now, this is what I DONT'T want.

How huge is ``huge''?  The DJGPP stub is only 2KB, and it shouldn't be
in a.out, only in a.exe.

What command did you use to link the program?  If you invoked ld.exe
directly, use the --output=coff-go32 command-line option to prevent
the linker from prepending the stub.

> The system will already be in
> some sort of 32-bit mode, so all I would like is that the first
> instruction be in location 0 of the binary file and so on.

This means you will need to rewrite (or toss) the startup code
(crt0.S), and roll your own linker script (lib/djgpp.djl).