From: Saul Wold <sgw@linux.intel.com>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: Andrei Gherzan <andrei.gherzan@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] eglibc: nscd support depends on OPTION_EGLIBC_INET
Date: Mon, 26 Aug 2013 14:47:04 -0700 [thread overview]
Message-ID: <521BCCD8.6080804@linux.intel.com> (raw)
In-Reply-To: <1377542924-1605-1-git-send-email-andrei.gherzan@windriver.com>
On 08/26/2013 11:48 AM, Andrei Gherzan wrote:
> Add --disable-nscd if DISTRO_FEATURES does not contain ipv4. This features is
> mapped to OPTION_EGLIBC_INET.
> The default behavior is to activate nscd (if --disable-nscd is not passed to
> configure script). But nscd depends on OPTION_EGLIBC_INET, so compilation will
> fail if this option is not activated.
>
Does this also need the Package to be set for ALLOW_EMPTY?
Sau!
> Signed-off-by: Andrei Gherzan <andrei.gherzan@windriver.com>
> ---
> meta/recipes-core/eglibc/eglibc_2.18.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/eglibc/eglibc_2.18.bb b/meta/recipes-core/eglibc/eglibc_2.18.bb
> index 17b651f..771f3e7 100644
> --- a/meta/recipes-core/eglibc/eglibc_2.18.bb
> +++ b/meta/recipes-core/eglibc/eglibc_2.18.bb
> @@ -79,6 +79,7 @@ EXTRA_OECONF = "--enable-kernel=${OLDEST_KERNEL} \
> --without-selinux \
> --enable-obsolete-rpc \
> --with-kconfig=${STAGING_BINDIR_NATIVE} \
> + ${@base_contains('DISTRO_FEATURES', 'ipv4', '', '--disable-nscd', d)} \
> ${GLIBC_EXTRA_OECONF}"
>
> EXTRA_OECONF += "${@get_libc_fpu_setting(bb, d)}"
>
next prev parent reply other threads:[~2013-08-26 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 18:48 [PATCH 1/1] eglibc: nscd support depends on OPTION_EGLIBC_INET Andrei Gherzan
2013-08-26 21:47 ` Saul Wold [this message]
2013-08-27 7:19 ` Andrei Gherzan
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=521BCCD8.6080804@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=andrei.gherzan@windriver.com \
--cc=andrei@gherzan.ro \
--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