From: cheekai@gen.co.jp (Chin Chee-Kai) Subject: Re: Default linker output filename 5 Nov 1996 00:20:07 -0800 Sender: daemon@cygnus.com Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: gensstc.gen.co.jp: smap set sender to using -f Original-To: Geoffrey Noer Original-Cc: gnu-win32@cygnus.com In-Reply-To: <1.5.4.32.19961102233717.006998c4@mail.direct.ca> Original-Sender: owner-gnu-win32@cygnus.com IMHO, if it doesn't sound too far-fetched, perhaps creating the default output with filename "a.out" and then create a link file "a.out.exe-->a.out" will preserve most semantics that prep-scripts expect, and will allow human to just type the following : gcc test.c a.out as expected on Unix. Chin Chee-Kai (Last, First) Internet Email-ID: cheekai@gen.co.jp Gen Tech Corporation > 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). - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".