Message-ID: <32614E17.66A5@cs.com>
Date: Sun, 13 Oct 1996 13:16:23 -0700
From: "John M. Aldrich" <fighteer AT cs DOT com>
Reply-To: fighteer AT cs DOT com
Organization: Three pounds of chaos and a pinch of salt
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp-workers AT delorie DOT com
Subject: Re: Linker script (Was Re: binutils 2.7 questions)
References: <Pine DOT SUN DOT 3 DOT 91 DOT 961013170110 DOT 16204F-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Eli Zaretskii wrote:
> 
> 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?

So what you are saying is that the v2.01 binutils will be able to create
a stubbed executable without any external help.  Will there be a
replacement for 'stubedit' and the other stub-related programs, or are
these being kept for compatibility?

Also, if I read what I have seen here correctly, is it true that you
will be able to use a different stub for djgpp executables simply by
changing an environment variable?  If so, will 'stubify', et al., know
about this as well as the binutils, or am I assuming too much?

Thanks.  :)

-- 
John M. Aldrich <fighteer AT cs DOT com>                      

* Anything that happens, happens.
* Anything that, in happening, causes something else to happen,
  causes something else to happen.
* Anything that, in happening, causes itself to happen again, happens
  again.
* It doesn't necessarily do it in chronological order, though.
 
                                       --- Douglas Adams