From: Theodore Ts'o <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>, xfs@oss.sgi.com
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH XFSPROGS 2/3] Build without enabling DEBUG by default
Date: Thu, 21 Jul 2011 19:50:36 -0400 [thread overview]
Message-ID: <1311292237-4155-2-git-send-email-tytso@mit.edu> (raw)
In-Reply-To: <1311292237-4155-1-git-send-email-tytso@mit.edu>
The tree currently will blow out with a build failure if -DDEBUG is
specified.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
m4/package_globals.m4 | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/m4/package_globals.m4 b/m4/package_globals.m4
index e469671..d2a3e2f 100644
--- a/m4/package_globals.m4
+++ b/m4/package_globals.m4
@@ -17,7 +17,7 @@ AC_DEFUN([AC_PACKAGE_GLOBALS],
test -z "$BUILD_VERSION" || pkg_release="$BUILD_VERSION"
AC_SUBST(pkg_release)
- DEBUG=${DEBUG:-'-DDEBUG'} dnl -DNDEBUG
+ DEBUG=${DEBUG:-'-DNDEBUG'} dnl -DNDEBUG
debug_build="$DEBUG"
AC_SUBST(debug_build)
--
1.7.4.1.22.gec8e1.dirty
next prev parent reply other threads:[~2011-07-21 23:50 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 ` Theodore Ts'o [this message]
2011-07-22 14:17 ` [PATCH XFSPROGS 2/3] Build without enabling DEBUG by default 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
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=1311292237-4155-2-git-send-email-tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).