From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] using crosstool-ng with glibc and buildroot
Date: Tue, 15 Sep 2009 06:58:16 +0200 [thread overview]
Message-ID: <20090915065816.235240d0@surf> (raw)
In-Reply-To: <20090914213907.326740@gmx.net>
Le Mon, 14 Sep 2009 23:39:07 +0200,
"Florian Schimmer" <slaanch@gmx.de> a ?crit :
> Checking external toolchain settings
> Cannot find
> cross-compiler /home/flo/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/-gcc
> make: ***
> [/home/xx/xx/buildroot/buildroot-2009.08/build_x86_64/stamps/ext-toolchain-installed]
> Error 1
Instead of pointing Buildroot
to /home/flo/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/,
could you point it to /home/flo/x-tools/x86_64-unknown-linux-gnu/ ? The
bin/ directory in this directory should contain the cross-compiling
tools with prefix.
> ext-tool.mk :
> if ! test -f $${SYSROOT_DIR}/lib/ld-linux.so.* ; then \
> echo "Incorrect selection of the C library"; \
> exit -1; \
> fi; \
>
> but crosstools output for ld is:
> /lib/ld.so.1 and /lib/ld-2.9.so
Can you give me the full list of libraries in $${SYSROOT_DIR}/lib/ ?
Here, on an ARM toolchain, I have a lib/ld-linux.so.3 symbolic link.
Maybe it's different per architecture, in which case I could relax the
test.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2009-09-15 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 21:39 [Buildroot] using crosstool-ng with glibc and buildroot Florian Schimmer
2009-09-15 4:58 ` 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=20090915065816.235240d0@surf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox