This is because when using fortify warnings we need to have some level of optimization, while we append warnings to CC we dont do the same for optimization, which results in compile failures when doing build with hardened flags
Signed-off-by: Khem Raj <[email protected]> --- meta-oe/recipes-kernel/crash/crash_7.1.9.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-oe/recipes-kernel/crash/crash_7.1.9.bb b/meta-oe/recipes-kernel/crash/crash_7.1.9.bb index 93208e398..d40937e93 100644 --- a/meta-oe/recipes-kernel/crash/crash_7.1.9.bb +++ b/meta-oe/recipes-kernel/crash/crash_7.1.9.bb @@ -35,6 +35,7 @@ SRC_URI[gdb.sha256sum] = "8070389a5dcc104eb0be483d582729f98ed4d761ad19cedd3f17b5 inherit gettext BBCLASSEXTEND = "native cross" +TARGET_CC_ARCH_append = " ${SELECTED_OPTIMIZATION}" # crash 7.1.3 and before don't support mips64 COMPATIBLE_HOST = "^(?!mips64).*" -- 2.13.2 -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
