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 271] New: Library 'libgcc_s.so.1' not installed in search path
Date: Mon, 13 Apr 2009 03:36:36 +0000 (UTC)	[thread overview]
Message-ID: <bug-271-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=271

            Target: x86-64
             Build: buildroot-20090412
           Summary: Library 'libgcc_s.so.1' not installed in search path
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: info at je-eigen-domein.nl
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When booting the target system created by buildroot, I get a lot of "can't load
library 'libgcc_s.so.1'" messages.

The library exists in the folder /usr/lib64, but it seems that folder is not in
the default ld search path.
System works fine after copying the library to /lib


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-04-13  3:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  3:36 bugzilla at busybox.net [this message]
2009-04-28 22:07 ` [Buildroot] [Bug 271] Library 'libgcc_s.so.1' not installed in search path bugzilla at busybox.net
2009-04-29 18:57 ` bugzilla at busybox.net
2009-07-17  9:19 ` 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-271-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