Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9411] New: MUSL build with RT Error relocating /lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found
Date: Wed, 09 Nov 2016 17:07:51 +0000	[thread overview]
Message-ID: <bug-9411-163@https.bugs.busybox.net/> (raw)

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

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-11-09 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 17:07 bugzilla at busybox.net [this message]
2016-11-25 20:53 ` [Buildroot] [Bug 9411] MUSL build with RT Error relocating /lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found bugzilla at busybox.net
2018-06-07 15:28 ` 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-9411-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