From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>,
Euan Harris <euan.harris@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH for 4.6] tools: Honor Config.mk debug value, rather than setting our own
Date: Wed, 2 Sep 2015 14:27:27 +0100 [thread overview]
Message-ID: <1441200447.26292.191.camel@citrix.com> (raw)
In-Reply-To: <20150902112546.GF18474@zion.uk.xensource.com>
On Wed, 2015-09-02 at 12:25 +0100, Wei Liu wrote:
> On Wed, Sep 02, 2015 at 12:24:31PM +0100, Ian Campbell wrote:
> > On Wed, 2015-09-02 at 12:08 +0100, Wei Liu wrote:
> > > On Wed, Sep 02, 2015 at 10:34:55AM +0100, George Dunlap wrote:
> > > > Changeset 1166ecf ('tools/Rules.mk: Don't optimize debug builds;
> > > > add
> > > > macro debugging information') exposed a bug whereby the autoconf
> > > > stuff
> > > > in tools was setting its own debug value (defaulting to ENABLED,
> > > > even
> > > > for releases) instead of honoring the value set in Config.mk.
> > > >
> > > > After that changeset, if the global build has -D_FORTIFY_SOURCE
> > > > enabled (as is the default in CentOS 7 rpmbuild), then the tools
> > > > build
> > > > will fail (because debug builds default to on).
> > > >
> > > > There should be only one place to specify whether to build debug or
> > > > not, and Config.mk is already included by the relevant makefiles.
> > > > So
> > > > simply remove the tools/configure debug option and everything falls
> > > > into place naturally.
> > > >
> > > > Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
> > >
> > > Acked-by: Wei Liu <wei.liu2@citrix.com>
> >
> > Release-ack too?
>
> Release-acked-by: Wei Liu <wei.liu2@citrix.com>
Thx, applied.
prev parent reply other threads:[~2015-09-02 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 9:34 [PATCH for 4.6] tools: Honor Config.mk debug value, rather than setting our own George Dunlap
2015-09-02 10:08 ` George Dunlap
2015-09-02 11:05 ` Ian Campbell
2015-09-02 11:08 ` Wei Liu
2015-09-02 11:24 ` Ian Campbell
2015-09-02 11:25 ` Wei Liu
2015-09-02 13:27 ` Ian Campbell [this message]
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=1441200447.26292.191.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=euan.harris@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).