From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building external i586 ARM cross toolchain on x64 Linux
Date: Mon, 9 Aug 2010 14:37:47 +0000 (UTC) [thread overview]
Message-ID: <i3p3rq$ve8$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTi=cJmoQ=45zMBcS2pQeyEENWgtXtic8=Z-U8TLT@mail.gmail.com
On 2010-08-09, James Ronald <james.ronald@gmail.com> wrote:
> On Fri, Aug 6, 2010 at 4:36 PM, Grant Edwards <grant.b.edwards@gmail.com>wrote:
>
>> On 2010-08-06, James Ronald <james.ronald@gmail.com> wrote:
>>
>>> Building such on 32 bit Linux distribution works great but I would
>>> like to switch to using a 64 bit Linux distribution and still be able
>>> to build an 32bit (i586) external (portable) tool chain.
>>
>> I don't know why the procedure would be any different. What exactly
>> failed?
>
> Buildroot will automatically build a 64 bit cross toolchain when run
> on 64 bit Linux and a 32 bit cross toolchain when run on 32 bit
> Linux. I am asking if there is a buildroot "preferred method" or
> "best practice" for building a 32 bit cross toolchain on on 64 bit
> Linux.
I think I'm confused. When you say a "64 bit cross toolchain" I read
that as a toolchain for a 64-bit target, and I didn't think the "bit
size" of the host made any difference to Buildroot.
If what you want to do is use Buildroot on architecture A to build a
compiler to run on architecture B for for a target with architecture
C, then that's called a "Canadian Cross", and I don't think buildroot
will do that (unless there's some special case in gcc/binutils for the
IA32 and AMD64 architectures).
You can do it with Crosstool-NG:
http://ymorin.is-a-geek.org/projects/crosstool#canadian_build
--
Grant Edwards grant.b.edwards Yow! ... the MYSTERIANS are
at in here with my CORDUROY
gmail.com SOAP DISH!!
next prev parent reply other threads:[~2010-08-09 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 20:08 [Buildroot] Building external i586 ARM cross toolchain on x64 Linux James Ronald
2010-08-06 20:36 ` Grant Edwards
2010-08-09 14:18 ` James Ronald
2010-08-09 14:37 ` Grant Edwards [this message]
2010-08-10 18:25 ` 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='i3p3rq$ve8$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.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