All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][v3 3/4] uClibc: redo configuration
Date: Thu, 8 Jul 2010 14:12:16 -0700	[thread overview]
Message-ID: <AANLkTinJLDCgt2ku0lIoHiT0EPlYMH8HDJLI-hAaXMvG@mail.gmail.com> (raw)
In-Reply-To: <1278622050.15825.18.camel@lenovo.internal.reciva.com>

On Thu, Jul 8, 2010 at 1:47 PM, Phil Blundell <philb@gnu.org> wrote:
> On Thu, 2010-07-08 at 12:02 -0700, Khem Raj wrote:
>> I would have a feature called 'nobx' because most of the machines
>> we support actively in OE has BX. With current state this needs to
>> be added to MACHINE features for almost all arm machines. We can instead
>> have nobx and keep USE_BX enabled and only disable it if nobx appears
>> in machine_features. Otherwise I have tested the patches myself
>> and they seems to work well.
>
> I'm not sure that putting bx (or nobx) in MACHINE_FEATURES really
> conveys any information that you can't already get from TARGET_ARCH plus
> THUMB_INTERWORK.  It's also worth noting that the latter is a DISTRO
> variable so, if you did add a competing bx flag to MACHINE_FEATURES, it
> would be difficult to ensure that the two were consistent.

hmm TARGET_ARCH wouldnt be the one but BASE_PACKAGE_ARCH does have sub-arch
info. Although I would agree with you that we can build this information from
BASE_PACKAGE_ARCH but its not as bad to have it as a machine feature either.

>
> p.
>
>
>



  parent reply	other threads:[~2010-07-09  8:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 19:32 [PATCH][v3 0/4] honour {MACHINE, DISTRO}_FEATURES for configuration Bernhard Reutner-Fischer
2010-07-06 19:32 ` [PATCH][v3 1/4] busybox: configure according to {MACHINE, DISTRO}_FEATURES Bernhard Reutner-Fischer
2010-07-06 19:32 ` [PATCH][v3 2/4] busybox: picking IPv6 per default is not up to the package Bernhard Reutner-Fischer
2010-07-06 19:32 ` [PATCH][v3 3/4] uClibc: redo configuration Bernhard Reutner-Fischer
2010-07-08 19:02   ` Khem Raj
2010-07-08 20:28     ` Bernhard Reutner-Fischer
2010-07-08 20:31       ` Khem Raj
2010-07-08 20:44         ` Bernhard Reutner-Fischer
2010-07-08 20:41       ` Khem Raj
2010-07-08 20:47     ` Phil Blundell
2010-07-08 21:03       ` Khem Raj
2010-07-08 21:29         ` Phil Blundell
2010-07-08 21:31           ` Khem Raj
2010-07-08 21:34             ` Phil Blundell
2010-07-08 22:03               ` Khem Raj
2010-07-08 22:16                 ` Bernhard Reutner-Fischer
2010-07-08 22:55                   ` Khem Raj
2010-07-08 21:12       ` Khem Raj [this message]
2010-07-08 21:32         ` Phil Blundell
2010-07-08 22:01           ` Khem Raj
2010-07-06 19:32 ` [PATCH][v3 4/4] uclibc: add 0.9.31 Bernhard Reutner-Fischer

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=AANLkTinJLDCgt2ku0lIoHiT0EPlYMH8HDJLI-hAaXMvG@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=philb@gnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.