From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] PXA270 and gcc-4.3.3 for iwMMXt
Date: Wed, 22 Apr 2009 18:14:56 +0200 [thread overview]
Message-ID: <20090422161456.GD19863@buzzloop.caiaq.de> (raw)
In-Reply-To: <dfb660300904220908x17502c02xad3358a6c64cb3f9@mail.gmail.com>
On Wed, Apr 22, 2009 at 09:08:28AM -0700, Laine Walker-Avina wrote:
> I've been trying to build a busybox system with buildroot for a
> PXA270-based system. I tried to use the latest gcc version in svn to
> generate the kernel and rootfs, however when I try to run the system I
> can't login and it doesn't run any of the init scripts in init.d. I
> tried to chroot to the new rootfs from a previously built rootfs
> compiled for a armv4 arch and it gave me a "Illegal Instruction" error
> when trying to run ash. Most other commands from that busybox run
> fine. And ash runs fine if i don't do the chroot and use the shared
> libs from the other rootfs. Any thoughts?
Check that your kernel and toolchain binaries are both built for EABI
and check for the following entries in your busybox .config:
BR2_iwmmxt=y
BR2_ARM_TYPE="ARM_IWMMXT"
# BR2_ARM_OABI is not set
BR2_ARM_EABI=y
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_TUNE="iwmmxt"
BR2_GCC_TARGET_ARCH="iwmmxt"
BR2_GCC_TARGET_ABI="aapcs-linux"
What you describe to see is very likely that kind of problem, we had
that many times already. The above settings should do well, though.
Daniel
next prev parent reply other threads:[~2009-04-22 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 16:08 [Buildroot] PXA270 and gcc-4.3.3 for iwMMXt Laine Walker-Avina
2009-04-22 16:14 ` Daniel Mack [this message]
[not found] ` <dfb660300904220929r41351171x258cee3484cd8f@mail.gmail.com>
2009-04-22 16:31 ` Laine Walker-Avina
[not found] ` <20090422163112.GE19863@buzzloop.caiaq.de>
2009-04-22 16:32 ` Laine Walker-Avina
2009-04-22 16:49 ` Daniel Mack
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=20090422161456.GD19863@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--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