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 15:01:25 -0700 [thread overview]
Message-ID: <AANLkTimo1BwySoObG0fcPIR7jWiwtmkE22jucMfafjll@mail.gmail.com> (raw)
In-Reply-To: <1278624724.15825.32.camel@lenovo.internal.reciva.com>
On Thu, Jul 8, 2010 at 2:32 PM, Phil Blundell <philb@gnu.org> wrote:
> On Thu, 2010-07-08 at 14:12 -0700, Khem Raj wrote:
>> 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.
>
> I do think it is fairly undesirable to have the same thing configured in
> two places. If a DISTRO sets THUMB_INTERWORK to off on a v4t platform
> then I think they would have a reasonable expectation that this would
> cause bx to not be used. If uclibc is looking at some other place to
> decide then it will not behave in the expected fashion.
should we make THUMB_INTERWORK a distro feature ? currently its an independent
variable. This should be set in consent with chosen machine so if a machine
does not support interworking then distro should remove it from a possible
set of distro features. Then uclibc can rely on this distro feature to turn
bx support on|off.
>
> p.
>
>
>
>
next prev parent reply other threads:[~2010-07-09 9:27 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
2010-07-08 21:32 ` Phil Blundell
2010-07-08 22:01 ` Khem Raj [this message]
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=AANLkTimo1BwySoObG0fcPIR7jWiwtmkE22jucMfafjll@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.