From: Otavio Salvador <otavio@ossystems.com.br>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] initramfs-framework: provides a modular initramfs
Date: Tue, 20 Dec 2011 08:46:50 -0200 [thread overview]
Message-ID: <CAP9ODKqC1TzB+rw4HDoRZFPoOqnpo3zhGqvY5Ap5afq14LAXkg@mail.gmail.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A12ED44B60F@shsmsx501.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Mon, Dec 19, 2011 at 11:02, Xu, Dongxiao <dongxiao.xu@intel.com> wrote:
> Hi Otavio and Saul,
>
> I tried to build initramfs-framework in Yocto master, and it reports the
> following multiple provider issue:
>
> ERROR: Multiple .bb files are due to be built which each provide udev
> (/home/dongxiao/poky/meta/recipes-core/udev/udev_164.bb/home/dongxiao/poky/meta/recipes-core/udev/
> udev_145.bb).
>
The proper fix IMO is to update udev to what we are using at meta-oe.
> I saw initramfs-framework RDEPENDS on package udev-utils, which doesn't
> exist in latest udev-164, thus it will try to include udev-145. This caused
> the multiple provider issue.
>
> Could you help to have a look at that?
>
Sure.
Sau, you told me you were looking at udev IIRC. Did you checked it?
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
[-- Attachment #2: Type: text/html, Size: 1727 bytes --]
prev parent reply other threads:[~2011-12-20 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1323292966.git.otavio@ossystems.com.br>
2011-12-07 21:23 ` [PATCH 1/1] initramfs-framework: provides a modular initramfs Otavio Salvador
2011-12-08 18:16 ` Saul Wold
2011-12-19 13:02 ` Xu, Dongxiao
2011-12-20 10:46 ` Otavio Salvador [this message]
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=CAP9ODKqC1TzB+rw4HDoRZFPoOqnpo3zhGqvY5Ap5afq14LAXkg@mail.gmail.com \
--to=otavio@ossystems.com.br \
--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 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.