Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] meaning of BR2_arm_dunno
Date: Thu, 29 Jan 2009 17:11:03 +0100	[thread overview]
Message-ID: <1233245463.15375.41.camel@sven> (raw)
In-Reply-To: <87eiymru7j.fsf@macbook.be.48ers.dk>

Hi,

On Thu, 2009-01-29 at 16:46 +0100, Peter Korsgaard wrote:

>         default apcs-gnu        if BR2_ARM_OABI
>         default atpcs           if BR2_arm_dunno
>         default aapcs           if BR2_arm_dunno
>         default aapcs-linux     if BR2_ARM_EABI

That looks more reasonable to me and it is in line with what was
suggested on the linux-arm-kernel mailing-list, see
http://lists.arm.linux.org.uk/lurker/message/20090124.152540.2d9a4947.en.html

As you can see from the linked thread, the compiler we ended up with
works nicely for userspace, but it cannot be used to build a kernel. It
may be a good idea to set BR2_GCC_TARGET_ABI to aapcs-linux even if
BR2_iwmmxt is selected.

> Could you give it a try with those 2 lines changed?

What exactly do you want me to try? I guess I would have to remove
my .config and go thru menuconfig, select ARM iwmmxt and then check what
gets sets for BR2_GCC_TARGET_TUNE, BR2_GCC_TARGET_ARCH and
BR2_GCC_TARGET_ABI? Is that correct?


Sven

  reply	other threads:[~2009-01-29 16:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 15:30 [Buildroot] meaning of BR2_arm_dunno Sven Neumann
2009-01-29 15:46 ` Peter Korsgaard
2009-01-29 16:11   ` Sven Neumann [this message]
2009-01-29 16:16     ` Peter Korsgaard
2009-01-30 10:01   ` Sven Neumann
2009-01-30 10:14     ` Sven Neumann
2009-01-30 10:23       ` Peter Korsgaard
2009-01-30 11:25         ` Sven Neumann
2009-01-30 11:28           ` Peter Korsgaard
2009-01-31 10:26             ` Bernhard Reutner-Fischer
2009-01-31 22:28               ` Peter Korsgaard

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=1233245463.15375.41.camel@sven \
    --to=s.neumann@phase-zero.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