[OE-core] [PATCH][v4] mmc-utils: fix the building failure when DEBUG_BUILD is 1

Burton, Ross ross.burton at intel.com
Thu Jun 25 09:30:11 UTC 2015


On 25 June 2015 at 07:59, Rongqing Li <rongqing.li at windriver.com> wrote:

> How about the below patch
>
> From 6de0180f5332880195e315fdaf4899406dc54d99 Mon Sep 17 00:00:00 2001
> From: Roy Li <rongqing.li at windriver.com>
> Date: Thu, 25 Jun 2015 14:44:05 +0800
> Subject: [PATCH] mmc-utils: fix the building failure when DEBUG_BUILD is 1
>
> AM_CFLAGS in Makefile includes -D_FORTIFY_SOURCE=2 which will lead
> to building failure when DEBUG_BUILD is 1.
> Cancel the definition of _FORTIFY_SOURCE by passing -U_FORTIFY_SOURCE
> via TARGET_CPPFLAGS; this does not effect the security cflags usage,
> since the cflags is equal to:
> CFLAGS="${TARGET_CPPFLAGS} ${SELECTED_OPTIMIZATION} ${SECURITY_CFLAGS}"
>

You're still globally turning off fortify when it's only a *warning* that
fortify and debug builds are mutually exclusive.  Disabling -Werror is the
best thing to do here.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150625/8e70c139/attachment-0002.html>


More information about the Openembedded-core mailing list