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

Burton, Ross ross.burton at intel.com
Tue May 5 15:43:21 UTC 2015


On 23 April 2015 at 04:18, <rongqing.li at windriver.com> wrote:

> +export FORITY="${@base_conditional( "DEBUG_BUILD", "1", "",
> "-D_FORTIFY_SOURCE=2", d )}"
> +EXTRA_OEMAKE = 'AM_CFLAGS="-D_FILE_OFFSET_BITS=64 ${FORITY}"'
>

"FORTIFY" not "FORITY", and why does that need to be exported?

I'm also curious as to why fortify and debug builds are incompatible, and
if there's a sufficient number of problems should we just disable fortify
in security_flags.inc when debug builds are enabled?

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


More information about the Openembedded-core mailing list