From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] toolchain into the root disk
Date: Mon, 7 Mar 2011 18:21:24 +0100 [thread overview]
Message-ID: <20110307182124.555f16ab@surf> (raw)
In-Reply-To: <AANLkTim0Up1xxGFx8AAg-_BWSNXgiJDjRV-3w1eaV9+m@mail.gmail.com>
Hello,
On Mon, 7 Mar 2011 16:54:23 +0000
Max <themaxmail@gmail.com> wrote:
> the BR2_PACKAGE_GCC_TARGET seams to me to work only with the internal
> toolchain.
Yes. Nobody has done the effort on getting BR2_PACKAGE_GCC_TARGET to
work with external toolchain as of today. As said previously, Buildroot
is a cross-compiling environment, so the need of a toolchain on the
target is not very common.
> I'm creating a root disk for a powerpc64 architecture. As build root does
> not support powerpc64, I'm
> using and external toolchain. With few workarounds evething works fine.
Just curious, which toolchain have you used ?
> When I use BR2_PACKAGE_GCC_TARGET=y the tool tries to download gcc but the
> version is not
> define so it tries to get the file gcc-.tar.bz2.
Yes, correct.
> Can you please tell me where in the tool the gcc version is set? I was not
> able to spot the location.
It isn't set in the external toolchain case, that's the problem. I now
Gustavo Zacarias has planned to rework the gcc handling, and it should
probably fix this problem.
In the mean time, you can force the GCC version by modifying the code,
but you'll very likely have issues when building gcc for the target.
Do you really need a native toolchain on the target ? What do you want
to build on the target ?
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-03-07 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:47 [Buildroot] toolchain into the root disk Max
2011-03-07 13:33 ` Thomas Petazzoni
2011-03-07 16:54 ` Max
2011-03-07 17:21 ` Thomas Petazzoni [this message]
2011-03-07 17:46 ` Max
2011-03-07 18:41 ` 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=20110307182124.555f16ab@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