Message-ID: <325F1009.2004@cs.com>
Date: Fri, 11 Oct 1996 20:27:05 -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: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
CC: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>, djgpp-workers AT delorie DOT com
Subject: Re: binutils 2.7 questions
References: <Pine DOT HPP DOT 3 DOT 91 DOT 961011125652 DOT 9168C-100000 AT newton DOT mathematik DOT tu-chemnitz DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert Hoehne wrote:
> 
> 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.

How about just saying '-o foo' to get 'foo', and '-o foo.exe' to get
'foo.exe'?  Why all the fuss?

-- 
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