Date: Tue, 21 Sep 1999 14:56:30 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Davin McCall <DavMac AT iname DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP viruses (Re: HELP! "invalid page exception"??)
In-Reply-To: <37e1095f.42095613@newsserver.cc.monash.edu.au>
Message-ID: <Pine.SUN.3.91.990921145612.19568C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 16 Sep 1999, Davin McCall wrote:

> Suppose you compile and link a program - which process is responsible
> for creating the excecutable file that you use to run (that *is*) your
> program? I though it was LD.

No, it's usually STUBIFY.  LD generates a raw COFF image that DOS
cannot run.  STUBIFY then prepends a stub to it and writes both to a
.exe file.

At least this is how things work with the stock djgpp.djl linker
script that is supplied with djdevNNN.zip.  If you edited or replaced
that script, your setup might be different.  LD *does* know how to
create .exe files directly, we just don't use that feature by default
(for some subtle but important reasons).