This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: program target missing $(EXEEXT)
search through the archives of both automake and libtool for my cygwin
patches, robert, for my particular method of dealing with this.
cheers,
edward
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Akim Demaille" <akim@epita.fr>
Cc: <automake@gnu.org>
Sent: Monday, March 26, 2001 7:52 AM
Subject: Re: program target missing $(EXEEXT)
> ----- Original Message -----
> From: "Akim Demaille" <akim@epita.fr>
> To: "Robert Collins" <robert.collins@itdomain.com.au>
> Cc: <automake@gnu.org>
> Sent: Monday, March 26, 2001 11:03 PM
> Subject: Re: program target missing $(EXEEXT)
>
>
> > >>>>> "Robert" == Robert Collins <robert.collins@itdomain.com.au>
> writes:
> >
> > Robert> AC_EXEEXT was already present. I added AC_OBJEXT and ran
> > Robert> automake --foreign again, no change.
> >
> > Sorry, I think I was confused. I checked, and it seems to be what was
> > designed: compile as foo, but *install* as foo.$(EXEEXT). I might be
> > wrong again, but at least 1.4 behaves this way.
> >
> > Someone else's input would be welcome here.
> >
>
> If it's compile as foo, then the bin_PROGRAMS dependency should be on
> foo, not foo$(EXEEXT), and the transformation should occur on the
> install line. That's not how it does it now... (Although I'm looking at
> CVS...)
>
> Rob
>