From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] libunwind: Do not use gold for linking
Date: Mon, 8 Aug 2016 15:51:01 -0700 [thread overview]
Message-ID: <20160808225101.32385-2-raj.khem@gmail.com> (raw)
In-Reply-To: <20160808225101.32385-1-raj.khem@gmail.com>
This effectively reverts the commit
3dd233ac0c80393824100c54bb525236f8290fd2
gold now emits errors on copy relocs against
protected symbols what ld.bfd did in past, however
it seems its too conservative.
This does not fix the case for folks who
use gold as default linker, however it
does make bintuls 2.27 work with default
configuration of OE
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta/recipes-support/libunwind/libunwind.inc | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/meta/recipes-support/libunwind/libunwind.inc b/meta/recipes-support/libunwind/libunwind.inc
index 1c342d3..e4ae8df 100644
--- a/meta/recipes-support/libunwind/libunwind.inc
+++ b/meta/recipes-support/libunwind/libunwind.inc
@@ -18,15 +18,6 @@ ATOMICOPS_armv5 = "-DAO_USE_PTHREAD_DEFS=1"
ATOMICOPS_armv4 = "-DAO_USE_PTHREAD_DEFS=1"
ATOMICOPS ?= ""
-LDFLAGS_append_x86 = " -fuse-ld=gold"
-LDFLAGS_append_x86-64 = " -fuse-ld=gold"
-
-LDFLAGS_append_arm = " -fuse-ld=gold"
-LDFLAGS_append_aarch64 = " -fuse-ld=gold"
-
-LDFLAGS_append_powerpc = " -fuse-ld=gold -mbss-plt"
-LDFLAGS_append_powerpc64 = " -fuse-ld=gold -mbss-plt"
-
SECURITY_LDFLAGS_append_libc-musl = " -lssp_nonshared -lssp"
BBCLASSEXTEND = "native"
--
2.9.2
next prev parent reply other threads:[~2016-08-08 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 22:51 [PATCH 1/2] webkitgtk: Disable gold for mips/mips64 Khem Raj
2016-08-08 22:51 ` Khem Raj [this message]
2016-08-08 23:25 ` [PATCH 2/2] libunwind: Do not use gold for linking Burton, Ross
2016-08-09 1:48 ` Khem Raj
2016-08-09 8:29 ` [PATCH 1/2] webkitgtk: Disable gold for mips/mips64 André Draszik
2016-08-09 8:53 ` 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=20160808225101.32385-2-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