This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: A build problem of C++ code on Cygwin
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: <cygwin at cygwin dot com>
- Date: Tue, 22 Aug 2006 19:54:47 -0500
- Subject: RE: A build problem of C++ code on Cygwin
> From: Brian Dessent
> Sent: Tuesday, August 22, 2006 6:30 PM
> Subject: Re: A build problem of C++ code on Cygwin
>
> Brian Dessent wrote:
>
> > 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.
>
> Indeed. The attached patch (and then re-running automake at the
> top-level) causes the build to work correctly -- or at least
> get past the problem you reported, I don't feel like waiting
> for the full build.
>
> You should report this upstream. The change should be safe
> for any platform.
>
> Brian
Another very similar one to watch out for are makefiles that actually do
support $EXEEXT, but for whatever reason $EXEEXT gets set to nothing. I
think it's mainly hand-rolled makefiles these days, but IIRC if somebody's
using crusty enough autotools they'll get configures that do this to you.
--
Gary R. Van Sickle
--
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/