From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH V2 4/6] libunwind: Drop adding libssp to linker flags
Date: Fri, 20 Apr 2018 09:33:52 -0700 [thread overview]
Message-ID: <20180420163354.12065-4-raj.khem@gmail.com> (raw)
In-Reply-To: <20180420163354.12065-1-raj.khem@gmail.com>
This is no longer needed as gcc provided libssp
is not built
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
Changes since v1:
- Rebased
meta/recipes-support/libunwind/libunwind.inc | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/recipes-support/libunwind/libunwind.inc b/meta/recipes-support/libunwind/libunwind.inc
index b9c532d3ad..36851d07ed 100644
--- a/meta/recipes-support/libunwind/libunwind.inc
+++ b/meta/recipes-support/libunwind/libunwind.inc
@@ -14,8 +14,6 @@ PACKAGECONFIG[latexdocs] = "--enable-documentation, --disable-documentation, lat
EXTRA_OECONF_arm = "--enable-debug-frame"
EXTRA_OECONF_aarch64 = "--enable-debug-frame"
-SECURITY_LDFLAGS_append_libc-musl = " -lssp_nonshared -lssp"
-
do_install_append () {
oe_multilib_header libunwind.h
}
--
2.17.0
next prev parent reply other threads:[~2018-04-20 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 16:33 [PATCH V2 1/6] libssp-nonshared: Add recipe Khem Raj
2018-04-20 16:33 ` [PATCH V2 2/6] musl: Depend on libssp-nonshared Khem Raj
2018-04-20 16:33 ` [PATCH v3 3/6] gcc-runtime: Disable gcc version of libssp Khem Raj
2018-04-20 16:33 ` Khem Raj [this message]
2018-04-20 16:33 ` [PATCH V3 5/6] musl: Upgrade to latest Khem Raj
2018-04-20 16:33 ` [PATCH 6/6] llvm: Fix [compile-host-path] QA issue Khem Raj
2018-04-30 13:08 ` [PATCH V2 1/6] libssp-nonshared: Add recipe Burton, Ross
2018-04-30 14:17 ` Khem Raj
2018-04-30 15:05 ` Burton, Ross
2018-04-30 15:21 ` Burton, Ross
2018-04-30 15:25 ` Khem Raj
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=20180420163354.12065-4-raj.khem@gmail.com \
--to=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox