Date: Sun, 13 Oct 1996 17:04:50 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "John M. Aldrich" <fighteer AT cs DOT com>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Linker script (Was Re: binutils 2.7 questions)
In-Reply-To: <325F0F5D.627@cs.com>
Message-Id: <Pine.SUN.3.91.961013170110.16204F-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 11 Oct 1996, John M. Aldrich wrote:

> > 4) Until stubify is not changed to use the optional external stub, you
> >    can use the following to build an exe file with your stub:
> >    - create the stub (name it mystub or something else)
> >    - set the environment variable STUB to point to this file
> >    - link your program with gcc and outputfile without the exe suffix
> >    - now use objcopy to create the exe (objcopy knows about the
> >      STUB variable)
> >      objcopy --output-target=coff-go32-exe foo foo.exe
> 
> 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?