X-Spam-Check-By: sourceware.org
Message-ID: <44EB8B19.2E0E4C69@dessent.net>
Date: Tue, 22 Aug 2006 15:54:17 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: A build problem of C++ code on Cygwin
References: <Pine DOT OSF DOT 4 DOT 21 DOT 0608230007580 DOT 31690-100000 AT ax0rm1 DOT roma1 DOT infn DOT it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Angelo Graziosi wrote:

> It tries to build C++ with gcc:
> 
>   gcc   bytes_to_int_flag_generator.o   -o bytes_to_int_flag_generator
> 
> ...
> So the question is : what could be the cause of this different behaviour ?
> 

I've seen this a million times.  It's a makefile that doesn't know about
$EXEEXT and assumes that executables have no extension.  Because of this
one of the stock built-in make rules gets invoked instead of the proper
link command.  Look in the Makefile for the rule that generates the
final binary and I'm willing to bet that it has no $EXEEXT.  This works
fine on linux because there is no extension for executables there.

Brian

--
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/