From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 2/2] eglibc: migrate configurability from oe
Date: Wed, 8 Jun 2011 08:42:39 +0200 [thread overview]
Message-ID: <20110608064239.GF23137@jama.jama.net> (raw)
In-Reply-To: <4DEF1826.7020004@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 3563 bytes --]
On Wed, Jun 08, 2011 at 02:35:18PM +0800, Kang Kai wrote:
> On 2011年06月08日 14:25, Koen Kooi wrote:
> > Op 8 jun 2011, om 03:45 heeft Kang Kai het volgende geschreven:
> >
> >> On 2011年06月07日 17:48, Koen Kooi wrote:
> >>> Op 7 jun 2011, om 11:42 heeft Kang Kai het volgende geschreven:
> >>>
> >>>> From: Kang Kai<kai.kang@windriver.com>
> >>>>
> >>>> Migrate configurability from oe, try to shrink minimal image size
> >>>>
> >>>> Update to get eglibc configuration options from DISTRO_FEATURES and enable them. All
> >>>> the options are enabled by default.
> >>>>
> >>>> Uncomment the line in conf/local.extended.conf to define DISTRO_FEATURES, so put
> >>>> what options you want to enable there.
> >>>>
> >>>> Signed-off-by: Kang Kai<kai.kang@windriver.com>
> >>>> ---
> >>>> meta/conf/distro/include/default-distrovars.inc | 8 ++-
> >>>> .../eglibc-2.13-fix-macro-RTLD_DEBUG.patch | 20 ++++++
> >>>> meta/recipes-core/eglibc/eglibc-options.inc | 62 ++++++++++++++++++++
> >>>> meta/recipes-core/eglibc/eglibc.inc | 6 ++
> >>>> meta/recipes-core/eglibc/eglibc_2.13.bb | 4 +-
> >>>> 5 files changed, 98 insertions(+), 2 deletions(-)
> >>>> create mode 100644 meta/recipes-core/eglibc/eglibc-2.13/eglibc-2.13-fix-macro-RTLD_DEBUG.patch
> >>>> create mode 100644 meta/recipes-core/eglibc/eglibc-options.inc
> >>>>
> >>>> diff --git a/meta/conf/distro/include/default-distrovars.inc b/meta/conf/distro/include/default-distrovars.inc
> >>>> index 4b68a0a..16ac681 100644
> >>>> --- a/meta/conf/distro/include/default-distrovars.inc
> >>>> +++ b/meta/conf/distro/include/default-distrovars.inc
> >>>> @@ -10,7 +10,13 @@ LIMIT_BUILT_LOCALES ?= "POSIX en_US en_GB"
> >>>> ENABLE_BINARY_LOCALE_GENERATION ?= "1"
> >>>> LOCALE_UTF8_ONLY ?= "0"
> >>>>
> >>>> -DISTRO_FEATURES ?= "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci"
> >>>> +DISTRO_FEATURES ?= "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci \
> >>>> + libc-ipv6 libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \
> >>>> + libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
> >>>> + libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm libc-libm-big libc-locales libc-locale-code \
> >>>> + libc-memusage libc-nis libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams libc-sunrpc \
> >>>> + libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
> >>>> + libc-posix-wchar-io"
> >> Hi Koen,
> >>> I think a seperate DISTRO_LIBC_FEATURES var would be cleaner and easier to override.
> >> I used DISTRO_FEATURES_EGLIBC before, but it didn't make Richard happy. :)
> > So how does one easily override LIBC features without touching other features?
> That is why use libc-spawn not "spawn" itself.
I agree with koen, when distro wants to keep all default libc-* but
alter other DISTRO_FEATURES it has to list all libc-* in it's own
config.
IMHO DISTRO_FEATURES_EGLIBC had wrong only suffix as it's not _EGLIBC
specific,
DISTRO_FEATURES_LIBC or proposed DISTRO_LIBC_FEATURES will allow
distributions to override it like this:
DISTRO_FEATURES = "foo bar ${DISTRO_FEATURES_LIBC}" which is much better
then 6 lines of libc-* features which need to resync when someone adds
new feature with new *libc version.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-06-08 6:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 9:42 [PATCH 0/2] eglibc: migrate configurability from oe V3 Kang Kai
2011-06-07 9:42 ` [PATCH 1/2] bitbake: add another local configuration file Kang Kai
2011-06-07 15:56 ` Saul Wold
2011-06-07 9:42 ` [PATCH 2/2] eglibc: migrate configurability from oe Kang Kai
2011-06-07 9:48 ` Koen Kooi
2011-06-08 1:45 ` Kang Kai
2011-06-08 6:25 ` Koen Kooi
2011-06-08 6:35 ` Kang Kai
2011-06-08 6:42 ` Martin Jansa [this message]
2011-06-07 9:53 ` Phil Blundell
2011-06-08 1:59 ` Kang Kai
2011-06-08 2:34 ` Khem Raj
2011-06-07 17:50 ` Khem Raj
2011-06-08 2:04 ` Kang Kai
-- strict thread matches above, loose matches on Subject: below --
2011-06-08 5:56 [PATCH 0/2] eglibc: migrate configurability from oe V4 Kang Kai
2011-06-08 5:56 ` [PATCH 2/2] eglibc: migrate configurability from oe Kang Kai
2011-06-10 3:13 ` Khem Raj
2011-06-10 3:25 ` Kang Kai
2011-06-13 9:01 [PATCH 0/2] eglibc: migrate configurability from oe V5 Kang Kai
2011-06-13 9:01 ` [PATCH 2/2] eglibc: migrate configurability from oe Kang Kai
2011-06-13 9:05 ` Phil Blundell
2011-06-13 9:15 ` Kang Kai
2011-06-13 9:27 ` Phil Blundell
2011-06-13 9:34 ` Kang Kai
2011-06-13 9:42 ` Phil Blundell
2011-06-13 10:00 ` Martin Jansa
2011-06-13 11:07 ` Phil Blundell
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=20110608064239.GF23137@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox