All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Hans Beckerus <hans.beckerus@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Problems building util-linux when wide character support is disabled in distro
Date: Wed, 18 Sep 2013 09:12:32 +0100	[thread overview]
Message-ID: <8312953.BrE7t8V9ee@helios> (raw)
In-Reply-To: <5238AA2A.8020302@gmail.com>

Hi Hans,

On Tuesday 17 September 2013 21:14:50 Hans Beckerus wrote:
> The way forward as I can see right
> now is to revert and put back the wide character support in libc. Unless I
> can figure out why util-linux is actually being built in the first place?
> What can cause dependencies to this package? It is not part of our
> IMAGE_FEATURES directly, nor indirectly and is not installed in our rootfs.
> But something requires it. Any hints on how to trace this back?

Look at the dot graphs produced by bitbake -g (too large to be viewed in a 
viewer, but you can look at them in text form) or use bitbake -g -u depexp 
which provides a UI for exploring dependencies.

FWIW, looking at the graphs here for core-image-minimal, udev is the most 
likely culprit unless you have something else that needs it (e.g. e2fsprogs).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-09-18  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 15:09 Problems building util-linux when wide character support is disabled in distro Hans Beckérus
2013-09-17 19:14 ` Hans Beckerus
2013-09-18  8:12   ` Paul Eggleton [this message]
2013-09-18  9:00     ` Hans Beckérus

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=8312953.BrE7t8V9ee@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=hans.beckerus@gmail.com \
    --cc=yocto@yoctoproject.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.