All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] eglibc: Make it configurable by tuning eglibc	options
Date: Fri, 07 Jan 2011 15:17:29 +0100	[thread overview]
Message-ID: <4D272079.5000402@opendreambox.org> (raw)
In-Reply-To: <AANLkTi=UUDxkTNDoWBoOxaCPDyupG8BazYtt6nGs3-7E@mail.gmail.com>

On 01/07/2011 02:47 PM, Otavio Salvador wrote:
> On Fri, Jan 7, 2011 at 07:28, Khem Raj <raj.khem@gmail.com> wrote:
>> * Look for disabled features in DISTRO_FEATURES and disable them while building eglibc
>> * By default all features are built
>> * One can disable a feature by specifying DISTRO_FEATURES += "noinet6 nobsd ...." e.g.
> 
> Awesome.
> 
> Do you think we could do something similar to busybox to avoid having
> many defconfigs?
> 

Maybe it would be better to introduce EGLIBC_FEATURES and
BUSYBOX_FEATURES, possibly presetting some values with options already
present in DISTRO_FEATURES.

Now it seems to be possible to specify both ipv6 and noipv6, which seems
inintuitive to me. It's not defined, which one would take precedence
over the other, or whether such conflicts could be catched to display an
error message.

Also, as an example, nobsd's name doesn't contain an implicit
relationship to eglibc, so one might think that it would affect other
packages as well.

Regards,
Andreas



  reply	other threads:[~2011-01-07 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  9:28 [PATCH] eglibc: Make it configurable by tuning eglibc options Khem Raj
2011-01-07 13:47 ` Otavio Salvador
2011-01-07 14:17   ` Andreas Oberritter [this message]
2011-01-07 17:24     ` Otavio Salvador
2011-01-07 17:30     ` Khem Raj
2011-01-07 18:15       ` Otavio Salvador
2011-01-07 19:29         ` Khem Raj
2011-01-08 12:42           ` Otavio Salvador
2011-01-08 13:39 ` Bernhard Reutner-Fischer
2011-01-08 20:41   ` Khem Raj

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=4D272079.5000402@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=openembedded-devel@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 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.