From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can Buildroot be configured to use the ELDK toolchain as an External Toolchain?
Date: Wed, 26 Jan 2011 08:45:47 +0100 [thread overview]
Message-ID: <20110126084547.0a47a506@surf> (raw)
In-Reply-To: <2B25428B-FDE1-4E48-A13D-45B6B7E9706B@gmail.com>
Hello Davis,
On Tue, 25 Jan 2011 18:44:58 -0500
Davis Mcpherson <davis.mcpherson@gmail.com> wrote:
> I'm working on a project that is using the ELDK toolchain and would
> like to use these tools to build Buildroot, I followed the
> instructions to configure an external toolchain via 'make menuconfig'
> but when I do 'make' i get an error that the the c library has been
> specified, i'm using glibc
Unfortunately, last time I checked, the ELDK toolchains did not support
the --sysroot option, which is mandatory to use a given toolchain as an
external toolchain in Buildroot. We have tried to support non
sysroot-capable toolchains, but it was the source of various issues,
and since sysroot is now quite ancient and available in most
toolchains, it sounded like a reasonable tradeoff.
> but I think the problem is rooted in the SYSROOT value being used to
> verify glibc...
>
> has anyone configured Buildroot to use ELDK as the external toolchain
> to use for builds?
I wanted to, but I never understood how to get just the ELDK toolchain
and not a complete distribution. I'll try to see if I can test this
toolchain, but if you have some simple setup instructions to get just
the toolchain, that would be great.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-26 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 23:44 [Buildroot] Can Buildroot be configured to use the ELDK toolchain as an External Toolchain? Davis Mcpherson
2011-01-26 7:45 ` Thomas Petazzoni [this message]
2011-01-26 21:08 ` 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=20110126084547.0a47a506@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