All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Cc: DAMARLA Satya Swaroop <satyaswaroop.damarla@gmail.com>
Subject: Re: Toolchain... Issues with systemd (probably)
Date: Thu, 20 Jun 2013 09:31:12 +0100	[thread overview]
Message-ID: <1526680.2T1uIfLeRH@helios> (raw)
In-Reply-To: <F7494A5B-922D-43A9-A63B-4F1C83F93E81@gmail.com>

On Thursday 20 June 2013 00:29:23 Khem Raj wrote:
> On Jun 20, 2013, at 12:12 AM, DAMARLA Satya Swaroop
> <satyaswaroop.damarla@gmail.com> wrote:
> > Any reasons why toolchains compile wihtout any issues on sysvinit and not
> > with systemd?
> > 
> > 
> > On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop
> > <swaroop.damarla@gmail.com> wrote: Yes... I thought the same and so, I
> > made two build directories , one for sysvinit and the other for systemd
> > and the errors I get abosulte no error when I try to populate_sdk under
> > sysvinit but I get the following errors when I run the same under
> > systemd.> 
> > | The following packages have unmet dependencies:
> > |  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed
> > |  
> > |             Recommends: libusb-dev but it is not installable
> > |             Recommends: module-init-tools-dev but it is not installable
> > |             Recommends: libkmod-dev but it is not installable
> > | 
> > | E: Unable to correct problems, you have held broken packages.
> 
> it seems you did not choose systemd as provider for udev. You should do that
> when you use systemd

default-providers.inc already does this so you should not need to:

meta/conf/distro/include/default-providers.inc:PREFERRED_PROVIDER_udev ?= 
"${@base_contains('DISTRO_FEATURES','systemd','systemd','udev',d)}"

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2013-06-20  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 12:08 Toolchain... Issues with systemd (probably) DAMARLA Satya Swaroop
2013-06-19 12:11 ` Burton, Ross
2013-06-19 13:11   ` DAMARLA Satya Swaroop
2013-06-20  7:12     ` DAMARLA Satya Swaroop
2013-06-20  7:29       ` Khem Raj
2013-06-20  8:23         ` DAMARLA Satya Swaroop
2013-06-20  8:31         ` Paul Eggleton [this message]
2013-06-20  9:07           ` DAMARLA Satya Swaroop
2013-06-20 10:06             ` Burton, Ross
2013-06-20 12:32               ` DAMARLA Satya Swaroop

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=1526680.2T1uIfLeRH@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=satyaswaroop.damarla@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.