From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [zeus][PATCH 7/9] security_flags.inc: fix flags missing from SDK toolchain
Date: Thu, 26 Mar 2020 16:53:34 +0800 [thread overview]
Message-ID: <d6df153991c91a1a14b561b3af52dcf96b73e6d7.1585211896.git.anuj.mittal@intel.com> (raw)
In-Reply-To: <cover.1585211896.git.anuj.mittal@intel.com>
In-Reply-To: <cover.1585211896.git.anuj.mittal@intel.com>
From: Tom Hochstein <tom.hochstein@nxp.com>
The security flags were missing from the SDK toolchain
because they were added specifically to class-target.
Add them to class-cross-canadian as well (since the SDK environment
file is created from cross-canadian target flags).
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Antoine Manache <a.manache@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
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 aaf04e9..568d036 100644
--- a/meta/conf/distro/include/security_flags.inc
+++ b/meta/conf/distro/include/security_flags.inc
@@ -57,6 +57,8 @@ SECURITY_STRINGFORMAT_pn-gcc = ""
TARGET_CC_ARCH_append_class-target = " ${SECURITY_CFLAGS}"
TARGET_LDFLAGS_append_class-target = " ${SECURITY_LDFLAGS}"
+TARGET_CC_ARCH_append_class-cross-canadian = " ${SECURITY_CFLAGS}"
+TARGET_LDFLAGS_append_class-cross-canadian = " ${SECURITY_LDFLAGS}"
SECURITY_STACK_PROTECTOR_pn-gcc-runtime = ""
SECURITY_STACK_PROTECTOR_pn-glibc = ""
--
2.7.4
next prev parent reply other threads:[~2020-03-26 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 8:53 [zeus][PATCH 0/9] zeus review Anuj Mittal
2020-03-26 8:53 ` [zeus][PATCH 1/9] icu: fix CVE-2020-10531 Anuj Mittal
2020-03-26 8:53 ` [zeus][PATCH 2/9] screen: fix CVE-2020-9366 Anuj Mittal
2020-03-26 8:53 ` [zeus][PATCH 3/9] sanity: check for more bits of Python Anuj Mittal
2020-03-26 8:53 ` [zeus][PATCH 4/9] nfs-utils: Disable statx if using glibc emulation Anuj Mittal
2020-03-26 8:53 ` [zeus][PATCH 5/9] e2fsprogs: fix CVE-2019-5188 Anuj Mittal
2020-03-26 8:53 ` [zeus][PATCH 6/9] e2fsprogs: backport upstream patch Anuj Mittal
2020-03-26 8:53 ` Anuj Mittal [this message]
2020-03-26 8:53 ` [zeus][PATCH 8/9] linux-yocto/4.19: update to v4.19.107 Anuj Mittal
2020-03-26 8:53 ` [zeus][PATCH 9/9] wic/direct: reserve 2 sector for extended partition Anuj Mittal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6df153991c91a1a14b561b3af52dcf96b73e6d7.1585211896.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.