Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: "Andre Oliveira da Costa" <costa@cade.com.br>
To: <earnie_boyd@yahoo.com>, <cygwin@sourceware.cygnus.com>
Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable na me         (a.exe now)
Date: Thu, 13 Jan 2000 18:55:27 -0200
Message-ID: <002f01bf5e08$85316760$8400000a@costa.cadenet.com.br>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Importance: Normal
In-Reply-To: <20000113202630.19220.qmail@web124.yahoomail.com>

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Earnie Boyd
> Sent: Thursday, January 13, 2000 6:27 PM
> To: Andre Oliveira da Costa; cygwin@sourceware.cygnus.com
> Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable
> na me (a.exe now)
>
> I agree, Andre.  I suggested, years ago now, that the .exe suffix be an
> optional configuration whose default is off.  It isn't needed by
> the Bourne
> shells we use to execute the programs.  I would like to see this
> as optional
> with say a GCC_SUFFIX=.exe environment variable.  If GCC_SUFFIX
> exists it uses
> the value to append to the executable output file.

It seems like a good (and simple) solution to me. With that, UNIX software
compiled directly from source would compile/install flawlessly if GCC_SUFFIX
is undefined or defined as an empty var. And, the folks who need the .exe
suffix (as stated by Matthew on a message to this thread) could just add
"export GCC_SUFFIX=" to their .bashrc startup files.

Andre
--
André Oliveira da Costa
(costa@cade.com.br)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com