All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Lambert <dave@lambsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] libgcc_s.so.1 missing from filesystem
Date: Wed, 11 Oct 2006 07:56:12 -0500	[thread overview]
Message-ID: <452CE9EC.4050101@lambsys.com> (raw)

I built several utilities including python using buildroot. A commom 
problem seems to be that they depend on a library libgcc.so.1 which 
appears in buildroot/build_arm/staging_dir/lib/libgcc_s.so.1, but does 
not get transferred to the target filesystem. Manually moving it to the 
target appears to be a workaround. Is there a more elegant solution? 
What is this library?

Regards,

Dave.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dave.vcf
Type: text/x-vcard
Size: 288 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061011/9a160e44/attachment.vcf 

             reply	other threads:[~2006-10-11 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 12:56 David Lambert [this message]
2006-10-11 13:27 ` [Buildroot] libgcc_s.so.1 missing from filesystem Fredrik Roubert
2006-10-11 13:30   ` Ashwin Bihari
2006-10-17 19:04     ` Erik Andersen
2006-10-17 19:36       ` Ashwin Bihari
2006-10-17 19:03 ` Erik Andersen
2006-10-18 12:12   ` David Lambert

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=452CE9EC.4050101@lambsys.com \
    --to=dave@lambsys.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.