X-Spam-Check-By: sourceware.org
Message-ID: <43A420B4.60506@byu.net>
Date: Sat, 17 Dec 2005 07:29:08 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Keith Moore <keithmo AT exmsft DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: autoconf and exeext behavior
References: <43A349C5 DOT 6070606 AT exmsft DOT com>
In-Reply-To: <43A349C5.6070606@exmsft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Keith Moore on 12/16/2005 4:12 PM:
> 
> That said, another possible solution would be to
> rip out the lines mentioned above, and replace all
> occurances of "exeext" with "EXEEXT" (the variable
> set by the autoconf-generated magic).

That sounds right to me.  Use what autoconf has already provided, then you
won't have to do platform-specific hacks that miss specific platforms like
cygwin.

> 
> I'll try to get the "most correct" solution pushed
> upstream.

If you ask me, the "most correct" solution is to have upstream use EXEEXT
consistently.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDpCCz84KuGfSFAYARAoKCAJ9+OG9KIb94s37F8LDfOSemlbAgUgCfaXhk
ql+6MYKDKbkjIofVsU8a//Q=
=7X45
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/