Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] Tool building problem EABI+PXA270
Date: Tue, 24 Mar 2009 15:39:04 +0100	[thread overview]
Message-ID: <20090324143904.GD22599@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090324135302.GY27893@whatever.nu>

On Tue, Mar 24, 2009 at 02:53:02PM +0100, Per-Henrik Lundblom wrote:
> > 
> >   http://lists.arm.linux.org.uk/lurker/message/20090123.185306.b2c4bb05.en.html
> > 
> > Conclusion is: do not build your kernel using a compiler that generates
> > iwmmxt code. As these extensions can't be used from both the kernel and
> > userspace at the same time, it is reserved for user's binaries and hence
> > forbidden in the kernel.

I was a little unprecise here: you can use the same compiler to build
your kernel and iwmmxt enabled user space binaries, the important thing
is that gcc does not generate code with these extensions unless it was
explicitly asked to do so. Screwed up br2 configs in conjunction with
some broken internal dependencies in buildroot (which habe been fixed
already) made gcc to do than unprovoked, which caused the built of
unbootable kernels.

> That makes sense... Shouldn't buildroot automagically just solve this
> for me? ;)
> 
> In build_arm/staging_dir/usr/bin I only have arm-linux-uclibcgnueabi-*
> gcc tools. I guess those is not the right ones to build the kernel then?

You can't judge from the names, but the location is fine. Just make
sure you get a EABI enabled gcc that does not use the fancy iwmmxt
extensions _by_default_. Play around with the br2-settings, your problem
is certainly somewhere there. And could you post the solution here for
others? :)

Daniel

  reply	other threads:[~2009-03-24 14:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 11:23 [Buildroot] Tool building problem EABI+PXA270 Per-Henrik Lundblom
2009-03-18 11:47 ` Daniel Mack
2009-03-18 12:25   ` Per-Henrik Lundblom
2009-03-18 12:30     ` Daniel Mack
     [not found]       ` <20090318131349.GD27893@whatever.nu>
2009-03-18 13:25         ` Daniel Mack
2009-03-18 14:25           ` Per-Henrik Lundblom
2009-03-18 14:46             ` Daniel Mack
2009-03-18 15:53               ` Per-Henrik Lundblom
2009-03-19  8:39                 ` Daniel Mack
2009-03-24 12:37                   ` Per-Henrik Lundblom
2009-03-24 13:11                     ` Daniel Mack
2009-03-24 13:19                       ` Per-Henrik Lundblom
2009-03-24 13:29                         ` Daniel Mack
2009-03-24 13:53                           ` Per-Henrik Lundblom
2009-03-24 14:39                             ` Daniel Mack [this message]
2009-03-24 14:46                               ` Per-Henrik Lundblom
2009-03-18 12:31     ` Sven Neumann
2009-03-18 13:09       ` Per-Henrik Lundblom
     [not found] ` <37c712e0903180742k6dbee6a4q48e3a4e023089e0@mail.gmail.com>
2009-03-18 14:54   ` Per-Henrik Lundblom
  -- strict thread matches above, loose matches on Subject: below --
2009-03-20  6:49 Christian Eggers

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=20090324143904.GD22599@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