All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Re: DEPEND creep breaking poky-tiny
Date: Fri, 24 Feb 2012 22:26:33 -0800	[thread overview]
Message-ID: <4F487F19.2000309@linux.intel.com> (raw)
In-Reply-To: <4F4877BF.7070903@linux.intel.com>



On 02/24/2012 09:55 PM, Darren Hart wrote:
> I'm working through some issues with a poky-tiny build of
> core-image-minimal failing. The first error is attributable to"
> 
> commit f3677d679e5c74f9877f36cdb170bbfea9b7b9bb
> glib-2.0: Add missing DEPENDS on dbus
> 
> dbus eventually pulls in shadow, which fails configure with the minimal
> libc configuration in poky-tiny. Removing this dependency allows us to
> make progress. (I understand a proper fix is needed, as the dependency
> was added for a reason).
> 
> Next up is popt failing due to missing native language or widechar
> support. pkgconfig is what brings in popt, and also what brought in glib
> above. Nothing in popt suggests it changed recently, which leads me to
> believe that the pkgconfig bit is new as I'm pretty sure I didn't need
> glib in poky-tiny originally at all.
> 
> Has pkgconfig been added recently? Seems silly to ask, but that is where
> things are pointing...
> 


commit 76640582e8ba114d4e80a494f6680fd0ce57ca58
Date:   Tue Jan 31 15:52:27 2012 +0000

    pkgconfig: Ensure pkgconfig RDEPENDS are tracked

RP, is this meant to force the building of pkgconfig? It changes the
requirement from pkgconfig-native to both pkgconfig and
pkgconfig-native.


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


  parent reply	other threads:[~2012-02-25  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25  5:55 DEPEND creep breaking poky-tiny Darren Hart
2012-02-25  6:12 ` Darren Hart
2012-02-25  6:26 ` Darren Hart [this message]
2012-02-25 11:40 ` Richard Purdie
2012-02-25 16:05   ` 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=4F487F19.2000309@linux.intel.com \
    --to=dvhart@linux.intel.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.