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 16:30:53 +0100	[thread overview]
Message-ID: <1233243053.15375.33.camel@sven> (raw)

Hi,

I wonder if anyone could explain to me the purpose of BR2_arm_dunno as
used in target/Config.in.arch. The reason I am asking is that we've run
into the problem of ending up with a misconfigured gcc (as reported
earlier on this list). I would like to find out how this can be avoided
in the future, but I seem to be unable to understand the mechanism that
selects the default values for BR2_GCC_TARGET_TUNE, BR2_GCC_TARGET_ARCH
and BR2_GCC_TARGET_ABI.


Sven

             reply	other threads:[~2009-01-29 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 15:30 Sven Neumann [this message]
2009-01-29 15:46 ` [Buildroot] meaning of BR2_arm_dunno Peter Korsgaard
2009-01-29 16:11   ` Sven Neumann
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=1233243053.15375.33.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