New: MUSL build with RT Error relocating /lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found
https://bugs.busybox.net/show_bug.cgi?id=9411
Bug ID: 9411
Summary: MUSL build with RT Error relocating
/lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found
Product: buildroot
Version: 2016.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: buildroot at komadev.de
CC: buildroot at uclibc.org
Target Milestone: ---
building minimal buildroot with musl + gcc 6.x compiles completely fine. in the runtime though, all binaries linked against libgcc_s.so.1 fail with i.e.
gbm: Last dlopen error: Error relocating /lib/libgcc_s.so.1:__cpu_indicator_init: symbol not found
This error is also referenced incl. a patch here
https://gcc.gnu.org/ml/gcc-patches/2015-05/msg00899.html
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9411] MUSL build with RT Error relocating /lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found
https://bugs.busybox.net/show_bug.cgi?id=9411
--- Comment #1 from Thomas Petazzoni <[email protected]> --- Can you give an example Buildroot package that exhibits the problem, so that it's easier for us to reproduce and investigate the issue? Thanks!
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9411] MUSL build with RT Error relocating /lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=9411
Thomas Petazzoni <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED--- Comment #2 from Thomas Petazzoni <[email protected]> --- This problem has been fixed in upstream gcc as of commit 6e6c7fc1e15525a10f48d4f5ac2edd853e2f5cb7, which was part of 7.x.
It was backported to the gcc 6.x branch as of commit 0fbe404007e6ef32d4d95c74a6c84b9166946ca3, available since gcc 6.3.0.
And the problem didn't exist in gcc 6.x. Therefore, I'm happy to say that this problem seems to be fixed.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.