From: Theodore Ts'o <tytso@mit.edu>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Generated files in e2fsprogs git repo
Date: Tue, 1 Jul 2014 11:22:33 -0400 [thread overview]
Message-ID: <20140701152233.GA2775@thunk.org> (raw)
In-Reply-To: <CAJTo0Lb9cxfE4bt6qLXzg5C8_j-9MUtiE2se+PMbYSeE=Gjasw@mail.gmail.com>
On Tue, Jul 01, 2014 at 10:55:51AM +0100, Burton, Ross wrote:
>
> My context is that we're building distributions and for every package
> that uses autotools we forcibly autoreconf because the
> upstream-provided configure is generally insufficient: for example
> upstream libtool needs patches to cross-compile correctly, and there's
> a long lag (several years) between a new architecture being developed
> (two recent examples: x32 and aarch64) and it being wide-spread enough
> to be in every generated configure script.
I don't use libtool at all, because I'm not a masochist.
https://plus.google.com/+TheodoreTso/posts/89xgTY49Rvk
I assume the real issue is that you need an updated version of
config.guess and config.sub. That can be easily updated without
having to use autoreconf, which is using an elephant gun to kill a
flea.
> e2fsprogs is one of the handful that breaks when we do this, because
> aclocal.m4 contains macros that don't come from the system (AX_TLS and
> CHECK_GNU_MAKE). Simply moving these macros to acinclude.m4 should
> solve this problem for us: autoconf defines that aclocal.m4 contains
> copies of macros from the system, but acinclude.m4 contains
> project-specific macros. I'll send a patch shortly to implement this
> split.
I'll look at that patch; if it's clean, I won't have a problem with
it. But I'd strongly encourage you to consider just updating
config.guess and config.sub for those projects that have the good
taste not to use libtool.
Regards,
- Ted
prev parent reply other threads:[~2014-07-01 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 16:52 Generated files in e2fsprogs git repo Burton, Ross
2014-07-01 1:02 ` Theodore Ts'o
2014-07-01 9:55 ` Burton, Ross
2014-07-01 15:22 ` Theodore Ts'o [this message]
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=20140701152233.GA2775@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=ross.burton@intel.com \
/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).