From: salad AT semaphore DOT com (Salad)
Subject: Re: Default linker output filename
30 Oct 1996 22:00:04 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <32782941.A93.cygnus.gnu-win32@semaphore.com>
References: <199610302317 DOT PAA11028 AT skaro DOT cygnus DOT com>
Reply-To: salad AT semaphore DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0b8Gold (Win95; I)
Original-To: Geoffrey Noer <noer AT cygnus DOT com>
Original-CC: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Geoffrey Noer wrote:
> 
> We are thinking about changing the default linker output filename from
> a.out to aout.exe.  Can anyone think of any bad consequences that might
> result?
> 
> (My gut feeling is that a.out.exe might be problematic so I lean towards
> aout.exe).
> 
> --
> Geoffrey Noer
> noer AT cygnus DOT com
> -
> For help on using this list, send a message to
> "gnu-win32-request AT cygnus DOT com" with one line of text: "help".

 It sounds wonderfull to me... only problem that might happen, is if
some configure scripts rely on the linker compiling to "a.out"... But
I've never delved into the autoconfigure stuff, and the GNU guys are
usually smarter than that...

 Trevor
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".