From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Questions related to "Incorrect selection of the C library" error
Date: Thu, 15 Sep 2011 11:41:54 +0200 [thread overview]
Message-ID: <20110915114154.5a738a61@skate> (raw)
In-Reply-To: <CAOPDcRwGMUaA0SuGc09XiQoweF9aMwbSeYKqoD4wj_NwY+i9Rw@mail.gmail.com>
Le Thu, 15 Sep 2011 11:20:44 +0200,
stl <st.lambert02@gmail.com> a ?crit :
> Effectively, my port of uClibc is not installed in the same directory
> than my toolchain.
> Because, the version of the toolchain I use is compiled with newlib
> as C library, instead of uClibc.
>
> And my problem with the ld-uclibc.so.* comes from I have not done
> anything yet that deals with
> dynamic linker in my port of uClibc.
>
> It seems that some work remains to be done...
With a bit tuning, Buildroot can work with a toolchain that does not
support shared libraries (so you can postpone the work on the dynamic
linker later on). But it needs to be a real toolchain, not a bare-metal
compiler on one side and the C library on the other side.
So before diving into the dynamic linking stuff and shared libraries, I
would recommend you to work on getting a proper toolchain built, either
with Buildroot or Crosstool-NG (I would suggest the latter). If you
have a working binutils/gcc/uClibc port, integrating the support for
your arch in Crosstool-NG should not be very complicated.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-09-15 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 8:16 [Buildroot] Questions related to "Incorrect selection of the C library" error stl
2011-09-14 9:52 ` Thomas Petazzoni
2011-09-14 16:19 ` Arnout Vandecappelle
2011-09-15 9:20 ` stl
2011-09-15 9:41 ` Thomas Petazzoni [this message]
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=20110915114154.5a738a61@skate \
--to=thomas.petazzoni@free-electrons.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.