Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Can we drop eglibc-utils from LIBC_DEPENDENCIES?
Date: Fri, 16 Dec 2011 10:30:48 -0800	[thread overview]
Message-ID: <4EEB8E58.3030806@linux.intel.com> (raw)

I'm working on a minimal distro definition, and found that eglibc-utils
pulls in bash (needed for tzconfig and xtrace apparently) which pulls in
gettext, which requires wchar support. I'd like to remove eglibc-utils
from my distro definition. I could override the default I suspect, but I
wonder if eglibc-utils should be made an optional package that distro
definitions, images, or users should specifically add if needed?

The relevant bit of code appears to be:

meta/conf/distro/include/tclibc-eglibc.inc

LIBC_DEPENDENCIES = "libsegfault \
		     eglibc \
    		     eglibc-dbg \
    		     eglibc-dev \
    		     eglibc-utils \
    		     eglibc-thread-db \
    		     eglibc-localedata-i18n \
    		     eglibc-gconv-ibm850 \
    		     eglibc-gconv-cp1252 \
    		     eglibc-gconv-iso8859-1 \
    		     eglibc-gconv-iso8859-15 \
    		     locale-base-en-us \
    		     locale-base-en-gb "

eglibc-dbg and eglibc-dev also seem like they could be made optional.

Thoughts? Would anyone object to me removing at least eglibc-utils from
LIBC_DEPENDENCIES?

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



             reply	other threads:[~2011-12-16 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 18:30 Darren Hart [this message]
2011-12-16 21:07 ` Can we drop eglibc-utils from LIBC_DEPENDENCIES? Koen Kooi
2011-12-16 23:20   ` Darren Hart
2011-12-16 23:34     ` Darren Hart
2011-12-17  1:29       ` Richard Purdie
2011-12-17  2:37         ` Darren Hart

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=4EEB8E58.3030806@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --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