Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Diem <PCDiem@FoxValley.net>
To: buildroot@busybox.net
Subject: [Buildroot] Multiple Target Architectures
Date: Tue, 08 Nov 2011 17:35:02 -0600	[thread overview]
Message-ID: <4EB9BCA6.4010206@FoxValley.net> (raw)

A few years ago I built a system using uClibc on x86. I used buildroot 
to build the initial filesystem for my development machine. My target 
machines have always been x86 so I've been able build everything 
natively from within that environment.

I'm now looking at building the same system for MikroTik RouterBoards so 
I will need to cross compile to PPC and MIPS. I've having a hard time 
grasping how to do this though. Can I simply build gcc for the other 
architectures on my current development system and then build for the 
target? I know I can use buildroot to build a root filesystem for each 
target architecture but it seems like I would have to run buildroot 
every time I make a small code change and buildroot will go through the 
whole process of rebuilding the toolchain each time.

I'm sure I'm missing something simple but I'm not sure what it is. 
Basically, I have a kernel, uClibc, busybox and some other packages that 
I want to be able to compile/cross-compile on an x86 host for x86, PPC 
and MIPS targets. What's the easiest/best way to do that?

BTW, I tried to use buildroot to build for a target arch of MIPS, the 
build failed with:
/usr/src/naos/buildroot-2011.08/output/host/usr/bin/mips-unknown-linux-uclibc-ar: 
error while loading shared libraries: 
/usr/src/naos/buildroot-2011.08/output/build/binutils-2.21/./bfd/.libs/libbfd-2.21.so: 
ELF file data encoding not little-endian

Thanks in advance for any pointers,
-- 
Paul C Diem
PCDiem at FoxValley.net

                 reply	other threads:[~2011-11-08 23:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4EB9BCA6.4010206@FoxValley.net \
    --to=pcdiem@foxvalley.net \
    --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