From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rootfs building using external toolchain
Date: Wed, 25 Mar 2009 17:41:41 +0100 [thread overview]
Message-ID: <20090325174141.426f9a4e@surf> (raw)
In-Reply-To: <49CA02EA.50200@yahoo.fr>
Le Wed, 25 Mar 2009 11:09:46 +0100,
Hichem Boussetta <boussettahichem@yahoo.fr> a ?crit :
> I am working now on a project where I am asked to generate toolchains
> for various architectures and then build the rootfs for them.
> The problem is that I need to compile using both uclibc and glibc.
> Therefore, I can't really use buildroot to generate the toolchains.
> So far, I decided to use crosstool-ng for the toolchain generation
> and then build the rootfs using buildroot. So, I would like to know
> if it is possible to use the external toolchains generated by
> crosstool-ng inside buildroot, and if it is, can someone show me
> briefly how can I do.
It is possible if your toolchain supports sysroot.
If so, in
Toolchain
-> Toolchain type
select ? External binary toolchain ?.
Then, make sure that the large file, IPv6, RPC, locale, WCHAR and C++
compiler/libstdc++ settings match the configuration of your toolchain.
What I mean is that these settings do *not* change anything in your
toolchain, but you must set them according to how your toolchain was
configured, so that the rest of Buildroot knows about your toolchain
configuration. Some time ago, I changed the naming of these entries to
make it clearer, but it got reverted.
Then, in ? External toolchain path ?, but the path to where your
toolchain is installed. In the case of a crosstool-ng generated
toolchain, I used /usr/local/xtools/arm-unknown-linux-uclibcgnueabi/.
If your toolchain is based on uClibc, that should be sufficient. If
your toolchain is based on glibc, then you will need to adjust the
following settings :
* The core C library from the external toolchain
* Libraries to copy from the external toolchain
I remember having success using a glibc toolchain, but I haven't tried
that recently. Please let us know about your successes and failures.
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-03-25 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 10:09 [Buildroot] rootfs building using external toolchain Hichem Boussetta
2009-03-25 16: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=20090325174141.426f9a4e@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