From: Fredrik Roubert <roubert@df.lth.se>
To: buildroot@busybox.net
Subject: [Buildroot] ld.real: cannot find -lgcc_s
Date: Tue, 10 Oct 2006 13:16:50 +0200 [thread overview]
Message-ID: <20061010111650.GH27810@igloo.df.lth.se> (raw)
In-Reply-To: <901e5e350610100356t2524befep22a71d924c4961ce@mail.gmail.com>
On Tue 10 Oct 12:56 CEST 2006, Michael wrote:
> How do I need to do to resolve the "cannot find -lgcc_s" problem?
One possible solution is to unset BR2_GCC_SHARED_LIBGCC in the buildroot
configuration, to get rid of the shared libgcc alltogether.
Cheers // Fredrik Roubert
--
Visserij 192 | +32 473 344527 / +46 708 776974
BE-9000 Gent | http://www.df.lth.se/~roubert/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 303 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061010/ba122567/attachment.pgp
next prev parent reply other threads:[~2006-10-10 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 10:56 [Buildroot] ld.real: cannot find -lgcc_s Michael
2006-10-10 11:16 ` Fredrik Roubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-10 13:25 Michael
2006-10-10 13:30 Michael
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=20061010111650.GH27810@igloo.df.lth.se \
--to=roubert@df.lth.se \
--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