From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Unable to build e2fsprogs 1.42.11 on RHEL 5
Date: Thu, 24 Jul 2014 22:04:53 +0000 [thread overview]
Message-ID: <CFF6DF2A.B393D%andreas.dilger@intel.com> (raw)
I'm unable to build the latest e2fsprogs on RHEL 5, since it returns an
error running autoconf:
autoconf
aclocal.m4:3095: error: Autoconf version 2.60 or higher is required
aclocal.m4:3095: the top level
The "2.60" version is explicitly checked in aclocal.m4, and changing it
to "2.59" (as is shipped with RHEL5) results in more errors:
autoconf
configure.in:903: warning: AC_PROG_MKDIR_P is m4_require'd but is not
m4_defun'd
configure.in:903: AC_PROG_MKDIR_P is required by...
aclocal.m4:3292: AM_PO_SUBDIRS is expanded from...
configure.in:903: AM_PO_SUBDIRS is required by...
aclocal.m4:626: AM_GNU_GETTEXT is expanded from...
configure.in:903: the top level
[etc]
It looks like this was added in commit 93613951 "aclocal.m4: update to
newer
versions of autoconf macros". Was there a particular reason for that
change
(there is no explanation given in the commit message)? I tried reverting
that patch to build on RHEL5 again, and it also appears to work on RHEL6,
but
there may be issues with newer autoconf versions...
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
next reply other threads:[~2014-07-24 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 22:04 Dilger, Andreas [this message]
2014-07-25 14:33 ` Unable to build e2fsprogs 1.42.11 on RHEL 5 Theodore Ts'o
2014-07-25 21:36 ` Dilger, Andreas
2014-07-26 14:37 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CFF6DF2A.B393D%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).