Date: Sun, 13 Oct 1996 14:33:48 -0400
Message-Id: <199610131833.OAA00245@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il
CC: fighteer AT cs DOT com, djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.961013170110.16204F-100000@is> (message from Eli
	Zaretskii on Sun, 13 Oct 1996 17:04:50 +0200 (IST))
Subject: Re: Linker script (Was Re: binutils 2.7 questions)


> > Is this a workable solution?  I thought that stubify existed for a
> > reason - if it is this easy to set up your own custom stub I don't see
> > why we bother with a specialized program.
> 
> It is only so easy *now* that Robert has taught Binutils about stubbed
> executables on MSDOS.  Previous ports didn't know about such creatures.  I
> suspect that `stubify' (and its predecessor in v1.x, `coff2exe') were a
> quick way of accomplishing the same without adding a new target to
> Binutils.  DJ? 

stubify existed because it was difficult to support it in binutils.
Binutils is probably one of the hardest packages to port, and writing
stubify was much easier.  It also removed a dependency in binutils on
the stub code, so I didn't have to recompile ld.exe each time the stub
changed.