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 22:08:33 +0100 [thread overview]
Message-ID: <20110126220833.24a1c7ea@surf> (raw)
In-Reply-To: <20110126084547.0a47a506@surf>
On Wed, 26 Jan 2011 08:45:47 +0100
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> 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.
Ok, I had a look at ELDK, and unfortunately, it cannot work. I will
updated the documentation accordingly, but here is the diff of what I
will push into the documentation:
+ <p>We do not support toolchains from
+ the <a href="http://www.denx.de/wiki/DULG/ELDK">ELDK of Denx</a>,
+ for two reasons:</p>
+
+ <ul>
+
+ <li>The ELDK does not contain a pure toolchain (i.e just the
+ compiler, binutils, the C and C++ libraries), but a toolchain
+ that comes with a very large set of pre-compiled libraries and
+ programs. Therefore, Buildroot cannot import the <i>sysroot</i>
+ of the toolchain, as it would contain hundreds of megabytes of
+ pre-compiled libraries that are normally built by
+ Buildroot.</li>
+
+ <li>The ELDK toolchains have a completely non-standard custom
+ mechanism to handle multiple library variants. Instead of using
+ the standard GCC <i>multilib</i> mechanism, the ARM ELDK uses
+ different symbolic links to the compiler to differentiate
+ between library variants (for ARM soft-float and ARM VFP), and
+ the PowerPC ELDK compiler uses a <code>CROSS_COMPILE</code>
+ environment variable. This non-standard behaviour makes it
+ difficult to support ELDK in Buildroot.</li>
+
+ </ul>
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-01-26 21:08 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
2011-01-26 21:08 ` 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=20110126220833.24a1c7ea@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 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.