From: Rongqing Li <rongqing.li@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][V3] mmc-utils: fix the building failure when DEBUG_BUILD is 1
Date: Wed, 3 Jun 2015 08:51:35 +0800 [thread overview]
Message-ID: <556E4F97.7000004@windriver.com> (raw)
In-Reply-To: <CAJTo0La2TaPM2TiAucZXJ4jmZbxY82m4OpcE94E+8SGXVunM0Q@mail.gmail.com>
On 2015年06月02日 18:38, Burton, Ross wrote:
>
> On 1 June 2015 at 02:37, Rongqing Li <rongqing.li@windriver.com
> <mailto:rongqing.li@windriver.com>> wrote:
>
> +EXTRA_OEMAKE = 'AM_CFLAGS="-D_FILE_OFFSET_BITS=64"'
>
>
> This seems fragile as you're relying on future maintainers checking that
> upstream don't change the value of AM_CFLAGS. Would passing
> -U_FORTIFY_SOURCE via CPPFLAGS solve the problem in a neater way?
>
> Ross
what should I do? make a patch which remove _FORTIFY_SOURCE from
AM_CFLAGS in
Makefile?
-Roy
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2015-06-03 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 0:14 [PATCH][V3] mmc-utils: fix the building failure when DEBUG_BUILD is 1 rongqing.li
2015-05-21 0:43 ` Rongqing Li
2015-05-26 1:02 ` Rongqing Li
2015-06-01 1:37 ` Rongqing Li
2015-06-02 10:38 ` Burton, Ross
2015-06-03 0:51 ` Rongqing Li [this message]
2015-06-03 0:57 ` Rongqing Li
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=556E4F97.7000004@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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