From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10586] New: musl gcc has ifunc enabled when musl doesn't support it
Date: Wed, 13 Dec 2017 10:53:17 +0000 [thread overview]
Message-ID: <bug-10586-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10586
Bug ID: 10586
Summary: musl gcc has ifunc enabled when musl doesn't support
it
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: nathan.renniewaldock at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
musl doesn't support ifunc[1], so needs to be specifically disabled as it
defaults to enabled.
Test case[2]:
$ cat >a.c <<EOD
int main(){ return 0; }
EOD
$ gcc -o a a.c -latomic
$ ./a
Error relocating /lib/libatomic.so.1: __atomic_store_8: symbol not found
Error relocating /lib/libatomic.so.1: __atomic_exchange_8: symbol not found
Error relocating /lib/libatomic.so.1: __atomic_load_8: symbol not found
Error relocating /lib/libatomic.so.1: __atomic_compare_exchange_8: symbol not
found
[1] http://www.openwall.com/lists/musl/2014/11/11/2
[2] http://www.openwall.com/lists/musl/2015/11/17/9
(tested buildroot 2017.11)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-12-13 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 10:53 bugzilla at busybox.net [this message]
2019-08-12 1:33 ` [Buildroot] [Bug 10586] musl gcc has ifunc enabled when musl doesn't support it bugzilla at busybox.net
2019-08-12 3:10 ` bugzilla at busybox.net
2019-08-12 3:17 ` bugzilla at busybox.net
2019-09-07 1:25 ` bugzilla at busybox.net
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=bug-10586-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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