This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin's autoconf?
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: Lapo Luchini <lapo at lapo dot it>
- Cc: cygwin at cygwin dot com
- Date: Sun, 01 Dec 2002 12:26:43 -0500
- Subject: Re: cygwin's autoconf?
- References: <3DE8CDE5.firstname.lastname@example.org> <012101c2987f$67c9eb70$78d96f83@pomello> <3DE8E77D.email@example.com> <3DE9114C.firstname.lastname@example.org> <3DE9E769.email@example.com>
Lapo Luchini wrote:
That's not the point: I have no problem on my cybwin developement
machine: the problem is that ./configure-generated Makefile tries to
call the autotools on each different machine, even in no-one changed
configure.in or Makefile.am
Not necessarily. If configure.in doesn't have AM_MAINTAINER_MODE, then
the default behavior is for all of the "maintainer rules" to be active
all the time. That means configure searches for automake, autoconf,
etc. and uses them to rebuild the infrastructure if necessary. Now,
even if the maint-mode rules never get invoked, during *configure* you
might get "test" invocations -- and it looks like those test invocations
The client machine shouldn't need autotools or the know-how to use them,
The behavior YOU are familiar with, where the maint-mode rules are never
invoked and configure doesn't even search for the autotools, requires
that configure.in include the AM_MAINTAINER_MODE macro, and you
configure *without* --enable-maintainer-mode.
Again, automake-1.7.1 requires autoconf-2.54. Make sure you have the
latest versions of auto*-devel installed -- or that NONE of the
following are installed:
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html