Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:49:10 +0200	[thread overview]
Message-ID: <20090422164910.GF19863@buzzloop.caiaq.de> (raw)
In-Reply-To: <dfb660300904220932i108dd65ey3a899e132d7c8c79@mail.gmail.com>

On Wed, Apr 22, 2009 at 09:32:21AM -0700, Laine Walker-Avina wrote:
> > Daniel
> >
> 
> This is the kernel .config.

Hmm. Another common pitfall is a floating point mismatch between your
kernel and your toolchain, but that one seems to be set correctly in
your case as well. I'm afraid I can't provide a quick solution for you
at this point, but there are still some more things to consider.

- make sure you clean your buildroot tree properly after you changed
  low level settings like the ones discussed. Maybe you're just stuck on
  an old version of anything and br2 failed to rebuild the right bits.

- set CONFIG_DEBUG_USER in your kernel config and pass user_debug=255
  on startup. That will output more details when user space binaries
  crash.

- Consider using gcc 4.3.2 for your tests. I've never used a newer
  version for ARMs, so I can't prove that this is working.

- Try compiling a very simple program which just echos some text and
  cross-compile it for your target. Use the kernel's init= option to
  call it and see if it works.

If you manage to solve your problems, post your findings here for
others, please :)

Daniel

      reply	other threads:[~2009-04-22 16:49 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
     [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 [this message]

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=20090422164910.GF19863@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