From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot shared uclibc native compiler only links statically
Date: Sun, 4 Mar 2012 12:00:21 +0100 [thread overview]
Message-ID: <201203041200.21575.arnout@mind.be> (raw)
In-Reply-To: <CAGmOteOykAc56k3F1w9Km+6FJ5wzM9WKTvyGWSxRCb7yZv2cew@mail.gmail.com>
On Sunday 04 March 2012 09:03:58 PHilip RUshik wrote:
> Hello,
> If I build a buildroot system with uClibc as a shared library and with a
> native compiler, the resulting native compiler works great most of the
> time, but it always links with the static libc.a instead of the shared
> library. Why does this happen, anybody know how to fix that?
This has just been solved on the list (but no patch is committed yet).
Basically, the problem is that the symlink of /usr/lib/libc.so to
/lib/libc.so.0 isn't included in the target directory.
As a workaround, you can create that link manually:
ln -s /lib/libc.so.0 target/usr/lib/libc.so
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-04 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 8:03 [Buildroot] Buildroot shared uclibc native compiler only links statically PHilip RUshik
2012-03-04 11:00 ` Arnout Vandecappelle [this message]
[not found] ` <CAGmOteMekR4JRMpYBrP2MVxScDwjkRaNU8KuXkXrDH-T3Cy8oA@mail.gmail.com>
2012-03-04 11:14 ` PHilip RUshik
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=201203041200.21575.arnout@mind.be \
--to=arnout@mind.be \
--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.