All of lore.kernel.org
 help / color / mirror / Atom feed
From: Euan Harris <euan.harris@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] tools: work around collision of -O0 and -D_FORTIFY_SOURCE
Date: Thu, 5 Feb 2015 15:47:53 +0000	[thread overview]
Message-ID: <20150205154753.GF3823@citrix.com> (raw)
In-Reply-To: <21715.35720.456332.832317@mariner.uk.xensource.com>

On Thu, Feb 05, 2015 at 03:26:00PM +0000, Ian Jackson wrote:
> Jan Beulich writes ("Re: [PATCH] tools: work around collision of -O0 and -D_FORTIFY_SOURCE"):
> > For one, PY_XCFLAGS='' wouldn't help, as we get -O0 from the
> > incoming CFLAGS.
> 
> Sorry, I meant PY_XCFLAGS='' or -O1 (as appropriate).
> 
> > And then I'm not really intending to fiddle with
> > the configure scripts (albeit, having done the patch in the presented
> > form, I expected you to want it done that way) - this and alike is
> > what I specifically want to stay out of if at all possible. Since in any
> > event commit 1166ecf781 introduced a regression for multiple
> > people, perhaps if that is not supposed to be reverted Euan should
> > look into addressing that regression?
> 
> Since I'm being difficult, how about if I prepare patch to configure.
> Would you be able to test it ?

If it's not too much trouble, I'd be very grateful if you could do this.
My autotools knowledge is rusty, and I don't know when I'll have the 
opportunity to set up a machine which reproduces the problem (clearly
mine doesn't, otherwise I would have run into this problem before!)

Thanks,
Euan

  parent reply	other threads:[~2015-02-05 15:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 17:01 [PATCH] tools: work around collision of -O0 and -D_FORTIFY_SOURCE Jan Beulich
2015-02-04 23:33 ` Don Slutz
2015-02-05 10:17   ` Jan Beulich
2015-02-05 14:55     ` Don Slutz
2015-02-05 11:08 ` Ian Jackson
2015-02-05 11:18   ` Jan Beulich
2015-02-05 12:25     ` Ian Campbell
2015-02-05 15:26     ` Ian Jackson
2015-02-05 15:46       ` Jan Beulich
2015-02-05 15:47       ` Euan Harris [this message]
2015-02-05 16:36         ` Ian Jackson
2015-02-05 16:52           ` Jan Beulich
2015-02-05 16:56             ` Ian Jackson
2015-02-05 17:01               ` Jan Beulich
2015-02-06  8:19               ` Jan Beulich
2015-02-06  8:22                 ` Jan Beulich
2015-02-06 11:04                   ` [PATCH] tools: work around collision of -O0 and -D_FORTIFY_SOURCE [and 1 more messages] Ian Jackson
2015-02-06 11:04                     ` [PATCH v4] tools: work around collision of -O0 and -D_FORTIFY_SOURCE Ian Jackson
2015-02-06 16:13                       ` Don Slutz
2015-02-06 17:28                         ` Ian Jackson
2015-02-06 15:24                     ` [PATCH] tools: work around collision of -O0 and -D_FORTIFY_SOURCE [and 1 more messages] Don Slutz
2015-09-01 14:54             ` [PATCH] tools: work around collision of -O0 and -D_FORTIFY_SOURCE George Dunlap
2015-09-01 15:10               ` Ian Campbell
2015-09-01 16:21                 ` George Dunlap

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=20150205154753.GF3823@citrix.com \
    --to=euan.harris@citrix.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.