Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Questions related to "Incorrect selection of the C library" error
Date: Wed, 14 Sep 2011 18:19:59 +0200	[thread overview]
Message-ID: <201109141820.00295.arnout@mind.be> (raw)
In-Reply-To: <20110914115217.5a64e8d0@skate>


On Wednesday 14 September 2011 11:52:17, Thomas Petazzoni wrote:
> > The following lib (ld*-uClibc.so.*) is missing in my lib dir.
> > Where does this lib come from?
> 
> From the external toolchain.
> 
> > In my .config, I have selected BR2_TOOLCHAIN_EXTERNAL=y
> > and I have set the path for my toolchain, and the prefix.
> >
> > 
> >
> > But where can I set the path for my installed uClibc directory?
> > ( /usr/<arch>-linux-uclibc )
> 
> In the toolchain menu:
>  * Select "External toolchain" as Toolchain type
>  * Select "Custom toolchain" as Toolchain
>  * Put the path of your toolchain in Toolchain path

 What Thomas means is: you have to install uClibc in the same place as the 
cross compiler.  

Cross-compiler and libc (and various other things like dynamic library loader 
and debugger) are intimately linked. Together they are called the toolchain.  

 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:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43

  reply	other threads:[~2011-09-14 16:19 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 [this message]
2011-09-15  9:20     ` stl
2011-09-15  9:41       ` Thomas Petazzoni

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=201109141820.00295.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox