From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] building for x86
Date: Thu, 27 Jan 2011 08:33:49 +0100 [thread overview]
Message-ID: <20110127083349.166be1dd@surf> (raw)
In-Reply-To: <AANLkTin2T-7uSanijcVE1hNGKz-tYjSMP2r0GhOE5X_M@mail.gmail.com>
Hello Ravi,
On Thu, 27 Jan 2011 18:27:17 +1300
Ravi Chemudugunta <chemuduguntar@gmail.com> wrote:
> I am wanting to compile for an x86 target, and my host system is also
> x86, is it advisable to try and use the tool chain that comes with the
> distribution? (Debian Lenny).
>
> I tried to do this by selecting external and getting rid of the
> prefix, however I get errors like the following:
>
> -gcc command not found, my guess is that buildroot expects the
> 'arch-platform-' format.
>
> I am assuming it would be easy enough to hack the make files so they
> don't affix an '-', however I am wondering whether this is even a good
> idea. For example what happens at the staging to target area when for
> e.g. libc needs to be copied?
Definitely, using the host toolchain (that comes with the distribution)
as an external toolchain isn't supported.
For the external toolchain support, we need a "pure" toolchain, i.e a
toolchain with just the compiler, the binutils and the C and C++
libraries, because we copy the complete toolchain sysroot into
Buildroot's staging area. And the complete toolchain sysroot of your
host toolchain is /, which means that it would copy all your system
into Buildroot's staging directory.
So if you want to build a system for x86 with Buildroot and an external
toolchain, my recommandation would be to build a pure toolchain with
Crosstool-NG.
Regards,
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-27 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 5:27 [Buildroot] building for x86 Ravi Chemudugunta
2011-01-27 7:33 ` Thomas Petazzoni [this message]
2011-01-27 7:55 ` Ravi Chemudugunta
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=20110127083349.166be1dd@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