Date: Mon, 11 Jun 2012 10:42:52 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: make: .exe handling breaks kernel cross-compile
Message-ID: <20120611144252.GA4004@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4FD4E21A DOT 2080809 AT users DOT sourceforge DOT net> <20120610182927 DOT GB32575 AT ednor DOT casa DOT cgf DOT cx> <4FD50A3D DOT 9040201 AT users DOT sourceforge DOT net> <20120611042637 DOT GB590 AT ednor DOT casa DOT cgf DOT cx> <4FD58A66 DOT 5060000 AT users DOT sourceforge DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FD58A66.5060000@users.sourceforge.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Jun 11, 2012 at 01:04:22AM -0500, Yaakov (Cygwin/X) wrote:
>>
>On 2012-06-10 23:26, Christopher Faylor wrote:
>> If there is a bug it is with make ever equating foo.exe with foo.  It's
>> undoubtedly happening because of Cygwin's attempts at transparency.
>>
>> I'm not kidding about EXEEXT.  Surely you know about this from having
>> maintained cygport.
>
>Am I ever, but I suspect *you* know that incorporating EXEEXT into the 
>Linux kernel buildsystem will likely never be accepted upstream.

>>On 2012-06-10 14:29, Christopher Faylor wrote:
>>>Makefiles which expect .exe extensions usually use the EXEEXT variable
>>>for just this purpose.  Linux's makefile doesn't do that for probably
>>>obvious reasons.


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