Date: Mon, 14 Oct 1996 09:55:59 +0000
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: binutils 2.7 questions
To: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
Cc: djgpp-workers AT delorie DOT com
Message-id: <32620E2F.280A@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: 
 <Pine DOT HPP DOT 3 DOT 91 DOT 961011125652 DOT 9168C-100000 AT newton DOT mathematik DOT tu-chemnitz DOT de>

Robert Hoehne wrote:
> > Do I need to configure binutils 2.7 to rebuild, or is it already done and
> > I can just run make?
> It is ready configured.

Cool, now I can go debug gas... (the jecxz thingy)

> 
> At first my question: For what do you need a raw coff image? All the binutils
> and GDB 4.16 can handle now the exe files. This was also the reason, to
> make the 'coff-go32-exe' target as the default target for ld. I (we) had
> discussed about this problem in the past in this group and came to the
> fact, that  producing the exe file should be the deafult, and every one,
> who realy need a raw coff image can either use the exe2coff or must
> do some work (thinking about the correct commandline switches) to
> produce direct a coff image.
> 

I want the raw coff for my bootstrap loader which is already fairly stable and making it handle a 
stubbed coff would cause more trouble than it's worth (a command line option or script file is 
MUCH easier (and needed anyway)).

I guess I just wanted to know if it was an actual decision or a slip.  I can live with the 
change, it just took me by supprise.

Bill