From: Ted Ts'o <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: Problems building xfsprogs
Date: Thu, 21 Jul 2011 12:31:22 -0400 [thread overview]
Message-ID: <20110721163122.GD3304@thunk.org> (raw)
In-Reply-To: <20110721090619.GA26263@infradead.org>
On Thu, Jul 21, 2011 at 05:06:19AM -0400, Christoph Hellwig wrote:
> I works fine for me on various releases of Debian, Fedsora, RHEL and
> SLES. But all he machines I've quickly checked seem to have an autoconf
> that can handle -I, so could you please send this pach with a proper
> signoff and description?
Sure, will do.
> > 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....
>
> The defaul actually is DEBUG=-DNDEBUG. No sure how you go he debug
> build. but we surely should fix it. I'll add the stub as soon as I get
> some time.
Well, the default from xfstest-dev/m4/package_globals.m4 is:
DEBUG=${DEBUG:-'-DDEBUG'} dnl -DNDEBUG
debug_build="$DEBUG"
AC_SUBST(debug_build)
I'm guessing you're getting the default of DEBUG=-DNDEBUG because
you're getting the package_globals.m4 package from some other m4
directory....
- Ted
next prev parent reply other threads:[~2011-07-21 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 17:59 Problems building xfsprogs Ted Ts'o
2011-07-20 18:32 ` 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 [this message]
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=20110721163122.GD3304@thunk.org \
--to=tytso@mit.edu \
--cc=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).