Re: [OE-core][PATCH] security_flags.inc: fix flags missing from SDK toolchain

, Tom Hochstein a écrit : > > > > -Original Message- > > From: Richard Purdie > > Sent: Tuesday, March 24, 2020 1:03 PM > > To: Antoine Manache ; Tom Hochstein < > tom.hochst...@nxp.com> > > Cc: openembedded-core@lists.openembedded.org > > Su

Re: [OE-core][PATCH] security_flags.inc: fix flags missing from SDK toolchain

I've already sent this patch few months ago but not taken into account yet. AM >From : Antoine Manache Date: mer. 20 nov. 2019 at 16:44 Subject: [OE-core] [PATCH v2] sdk: environment script doesn't set security options in CC and LDFLAGS variables To: When building a SDK from a DIS

[OE-core] sdk: backport of ba2df1f on thud ?

Hi all, Is it already planned to backport this fix to the thud branch ? ba2df1fa43b79c4959911c1b0bcad996f255b7a8 I see it is OK in Yocto 3.0 but not in 2.6.4, and I have an issue with my eSDK

[OE-core] [PATCH v2] sdk: environment script doesn't set security options in CC and LDFLAGS variables

once integrated to the core image built with the full Yocto stack. Signed-off-by: Antoine Manache --- meta/conf/distro/include/security_flags.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc index

[OE-core] [yocto] [PATCH] SDK environment script doesn't set security options in CC and LDFLAGS variables

once integrated to the core image built with the full Yocto stack. Signed-off-by: Antoine Manache --- meta/conf/distro/include/security_flags.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc index