[meta-intel] [PATCH] rmc: remove stack-protector-strong from CFLAGS

[Jianxun Zhang]

> On Dec 2, 2016, at 2:19 PM, Saul Wold <sgw at linux.intel.com> wrote:
> 
> Since the rmc is used standalone from systemd-boot and does not
> use libc which provides the stack_chk_fail code that causes an
> undefined symbol
> 
> Signed-off-by: Saul Wold <sgw at linux.intel.com>
> ---
> common/recipes-bsp/rmc/rmc.bb | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/common/recipes-bsp/rmc/rmc.bb b/common/recipes-bsp/rmc/rmc.bb
> index 41062bf..8c89a99 100644
> --- a/common/recipes-bsp/rmc/rmc.bb
> +++ b/common/recipes-bsp/rmc/rmc.bb
> @@ -22,6 +22,7 @@ COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux*"
> 
> TARGET_CFLAGS +="-Wl,--hash-style=both"
> 
> +SECURITY_CFLAGS_remove_class-target = "-fstack-protector-strong”
Saul,
I believe this will fix the issue with the current OE security setting. There could be other similar cases too:
-fstack-protector           -fstack-protector-all       -fstack-protector-explicit 
gcc (5.4) from my ubuntu. You may want to test/add these this time or put them in a watch list...

Thanks


> do_compile_class-target() {
> 	oe_runmake
> 	oe_runmake -f Makefile.efi
> -- 
> 2.7.4
> 
> -- 
> _______________________________________________
> meta-intel mailing list
> meta-intel at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel