From: "Ted Ts'o" <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Problems building xfsprogs
Date: Wed, 20 Jul 2011 13:59:18 -0400 [thread overview]
Message-ID: <20110720175918.GB17971@thunk.org> (raw)
I was trying to build xfsprogs in preparation for building xfstests in
an hermetic environment (as opposed to depending on magic XFS headers
being installed in /usr/include...)
What I found first of all (building on Ubuntu 10.10) was
a) "make configure" doesn't work until I patch the top-level Makefile:
diff --git a/Makefile b/Makefile
index c40fb2c..37973f5 100644
--- a/Makefile
+++ b/Makefile
@@ -82,7 +82,7 @@ configure:
libtoolize -c $(LIBTOOLIZE_INSTALL) -f
cp include/install-sh .
aclocal -I m4
- autoconf
+ autoconf -I m4
include/builddefs: configure
./configure $$LOCAL_CONFIGURE_OPTIONS
b) By default xfsprogs builds with DEBUG, and this causes building
libxfs/xfs_ialloc.c to blow up since there a reference of
xfs_stack_trace() which is undefined under a #ifdef DEBUG. The way to
fix this is to build with DEBUG=-DNDEBUG, but it took me an hour or
two figure this out....
- Ted
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-07-20 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 17:59 Ted Ts'o [this message]
2011-07-20 18:32 ` Problems building xfsprogs Eric Sandeen
2011-07-20 21:33 ` Ted Ts'o
2011-07-20 22:25 ` Greg Freemyer
2011-07-21 4:19 ` Ted Ts'o
2011-07-21 4:27 ` Ted Ts'o
2011-07-21 9:06 ` Christoph Hellwig
2011-07-21 16:31 ` Ted Ts'o
2011-07-21 22:57 ` Ted 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=20110720175918.GB17971@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--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