Comments

On Debian/Ubuntu systems, if autoconf version 2.13 is installed,
autoconf will try to automatically figure out whether autoconf 2.13 or
something more modern is required (since the autoconf maintainers,
curses be upon them, didn't bother to maintain compatibility between
autoconf 2.13 and 2.50). Unfortunately, the hueristics aren't
perfect, and although the configure.in file looks superficially like
it will be compatible with autoconf 2.13, it isn't. You will end up
with a number of very subtle compilation failures if you use autoconf
2.13.
So declare a requirement for autoconf 2.50 using AC_PREREQ(2.50).
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
configure.in | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)

On Thu, Jul 21, 2011 at 07:50:35PM -0400, Theodore Ts'o wrote:
> On Debian/Ubuntu systems, if autoconf version 2.13 is installed,> autoconf will try to automatically figure out whether autoconf 2.13 or> something more modern is required (since the autoconf maintainers,> curses be upon them, didn't bother to maintain compatibility between> autoconf 2.13 and 2.50). Unfortunately, the hueristics aren't> perfect, and although the configure.in file looks superficially like> it will be compatible with autoconf 2.13, it isn't. You will end up> with a number of very subtle compilation failures if you use autoconf> 2.13.> > So declare a requirement for autoconf 2.50 using AC_PREREQ(2.50).
Thanks a lot, I've applied our xfsprogs and xfstests patches, and also
ported the change to the xfsdump and dmapi repositories.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html