From: Christoph Hellwig <hch@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: hch@infradead.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [PATCH] Build using CFLAGS passed in at configure
Date: Tue, 2 Aug 2011 06:03:59 -0400 [thread overview]
Message-ID: <20110802100359.GA8028@infradead.org> (raw)
In-Reply-To: <1312235904-21187-1-git-send-email-tytso@mit.edu>
On Mon, Aug 01, 2011 at 05:58:24PM -0400, Theodore Ts'o wrote:
> In order to build xfsprogs in a hermetic build, we need be able to
> pass in -I and -L flags to the compiler and linker, respectively.
> This needs to be used by the configure script, but we also need to
> make sure these flags are used by the Makefiles as well.
Thanks a lot a Ted!
I've added this to xfsprogs, xfsdump and dmapi. xfstests actually
already has it, sent in in 2009 by Arek for the same reason you want
it in xfsprogs. Wish we would have been a bit better to propagate build
system fixes.
next prev parent reply other threads:[~2011-08-02 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 23:50 [PATCH XFSPROGS 1/3] configure.in: Declare a requirement for at least autoconf 2.50 Theodore Ts'o
2011-07-21 23:50 ` [PATCH XFSPROGS 2/3] Build without enabling DEBUG by default Theodore Ts'o
2011-07-22 14:17 ` Christoph Hellwig
2011-07-22 18:30 ` Ted Ts'o
2011-07-22 18:38 ` Christoph Hellwig
2011-07-22 22:30 ` Alex Elder
2011-07-22 22:34 ` Ted Ts'o
2011-07-23 1:32 ` Christoph Hellwig
2011-07-26 15:10 ` Christoph Hellwig
2011-07-30 16:55 ` Christoph Hellwig
2011-08-01 21:58 ` [PATCH] Build using CFLAGS passed in at configure Theodore Ts'o
2011-08-02 10:03 ` Christoph Hellwig [this message]
2011-07-21 23:50 ` [PATCH XFSPROGS 3/3] mkfs: Link against libuuid after liblkid Theodore Ts'o
2011-07-22 14:29 ` Christoph Hellwig
2011-07-22 14:28 ` [PATCH XFSPROGS 1/3] configure.in: Declare a requirement for at least autoconf 2.50 Christoph Hellwig
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=20110802100359.GA8028@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.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).