From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Cleanup some common CFLAGS
Date: Mon, 27 Aug 2007 17:22:10 -0400 [thread overview]
Message-ID: <20070827212210.GH17551@redhat.com> (raw)
In-Reply-To: <46D1111C.1010803@ubuntu.com>
On Sun, Aug 26, 2007 at 07:35:24AM +0200, Fabio Massimo Di Nitto wrote:
> diff -Naurd redhat-cluster-suite-2.20070823/cman/qdisk/Makefile cluster/cman/qdisk/Makefile
> --- redhat-cluster-suite-2.20070823/cman/qdisk/Makefile 2007-08-26 07:02:55.000000000 +0200
> +++ cluster/cman/qdisk/Makefile 2007-08-26 07:10:30.000000000 +0200
> @@ -13,7 +13,7 @@
> include ../../make/defines.mk
>
> CFLAGS += -D_GNU_SOURCE
> -CFLAGS += -Werror -Wstrict-prototypes -Wshadow -g
> +CFLAGS += -Werror -Wstrict-prototypes -Wshadow
> CFLAGS += -I${ccsincdir} -I${cmanincdir}
> CFLAGS += -I.
> CFLAGS += -I${incdir}
-DDEBUG is usually done by developers and is normally "printf" sort of
run-time debugging.
In my mind, for most distributors, -g always needs to be done, even w/o
-DDEBUG in order for support personnel to able to look at core files.
ACK if you've got a super easy to add CFLAGS, which it looks like you
do:
./configure --extracflags="-g"
Once your patch is applied, I'll look at the stuff in rgmanager that
croaks with --debug enabled.
-- Lon
next prev parent reply other threads:[~2007-08-27 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 5:35 [Cluster-devel] [PATCH] Cleanup some common CFLAGS Fabio Massimo Di Nitto
2007-08-27 6:40 ` Fabio Massimo Di Nitto
2007-08-27 15:45 ` Bob Peterson
2007-08-27 17:38 ` Fabio Massimo Di Nitto
2007-08-27 21:22 ` Lon Hohberger [this message]
2007-08-28 4:22 ` Fabio Massimo Di Nitto
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=20070827212210.GH17551@redhat.com \
--to=lhh@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.