<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 25 June 2015 at 07:59, Rongqing Li <span dir="ltr"><<a href="mailto:rongqing.li@windriver.com" target="_blank">rongqing.li@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1vk" class="a3s" style="overflow:hidden">How about the below patch<br>
<br>
>From 6de0180f5332880195e315fdaf4899406dc54d99 Mon Sep 17 00:00:00 2001<br>
From: Roy Li <<a href="mailto:rongqing.li@windriver.com" target="_blank">rongqing.li@windriver.com</a>><br>
Date: Thu, 25 Jun 2015 14:44:05 +0800<br>
Subject: [PATCH] mmc-utils: fix the building failure when DEBUG_BUILD is 1<span class=""><br>
<br>
AM_CFLAGS in Makefile includes -D_FORTIFY_SOURCE=2 which will lead<br>
to building failure when DEBUG_BUILD is 1.<br>
Cancel the definition of _FORTIFY_SOURCE by passing -U_FORTIFY_SOURCE<br></span>
via TARGET_CPPFLAGS; this does not effect the security cflags usage,<br>
since the cflags is equal to:<br>
CFLAGS="${TARGET_CPPFLAGS} ${SELECTED_OPTIMIZATION} ${SECURITY_CFLAGS}"</div></blockquote></div><br>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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>