[lvm-devel] fix for link pthread-related link failure on Debian

[Alasdair G Kergon]

On Mon, Sep 17, 2007 at 08:15:23PM +0200, Jim Meyering wrote:
> How about making it so autoconf is required, only if you modify
> configure.in or otherwise fiddle with mtimes to make it look like
> configure is out of date?
 
I still think that is too much risk for the build environment.
A warning message, yes, but blocking the build, no.
I don't want any chance of autoconf running unless people specifically
ask for it.

> Why cater to developers who lack the required version of autoconf?

It's the build/packaging environment I consider primary here.  I do not
want builds from tarball to acquire an autoconf dependency, and if
there's a rule saying that 'configure' sometimes needs rebuilding
automatically then that dependency exists - even if you consider
the possibility only theoretical, timestamps may get messed up under
some configurations.

Another way to do this would be to flip the --enable-autoreconf default
setting in the release tarballs.  (E.g. Only attempt the autoreconf if
the version ends in -cvs.)

Alasdair
-- 
agk at redhat.com