From: Richard Purdie <rpurdie@rpsys.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [CONSOLIDATED PULL 02/20] self-hosted: Fix multiple libx11 error
Date: Tue, 06 Mar 2012 11:42:05 -0800 [thread overview]
Message-ID: <1331062925.25887.14.camel@ted> (raw)
In-Reply-To: <4efd2e00d0cd6cc765da809b47d239664fc8922d.1331053126.git.sgw@linux.intel.com>
On Tue, 2012-03-06 at 09:03 -0800, Saul Wold wrote:
> From: Zhai Edwin <edwin.zhai@intel.com>
>
> Self-hosted needs package libx11-dev, which is ambiguous as virtual/libx11 is
> provided by libx11 or libx11-trim. This patch explictly set the perferred one,
> libx11-trim-dev, to avoid this.
>
> Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
> ---
> meta/recipes-core/tasks/task-self-hosted.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Please drop this patch. An alternative patch went in:
next prev parent reply other threads:[~2012-03-06 19:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 17:03 [CONSOLIDATED PULL 00/20] Kernel and GCC Updates included Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 01/20] libsdl: add DirectFB support Saul Wold
2012-03-08 19:48 ` Richard Purdie
2012-03-06 17:03 ` [CONSOLIDATED PULL 02/20] self-hosted: Fix multiple libx11 error Saul Wold
2012-03-06 19:42 ` Richard Purdie [this message]
2012-03-08 19:45 ` Richard Purdie
2012-03-06 17:03 ` [CONSOLIDATED PULL 03/20] image_types: add IMAGE_ROOTFS_ALIGNMENT Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 04/20] image.bbclass: fix rootfs generation without package management tools Saul Wold
2012-03-06 17:15 ` Otavio Salvador
2012-03-06 17:03 ` [CONSOLIDATED PULL 05/20] linux-yocto: respect FILESPATH directories Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 06/20] linux-yocto: use bareclone option Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 07/20] linux-yocto: v3.2.9, v3.0.23 + fixes and updates Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 08/20] logrotate 3.7.9: Allow rotate log across filesystems Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 09/20] gcc: Upgrade to 4.6.3 release Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 10/20] psplash: Add mising commands module import Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 11/20] linux-yocto/meta: fix incorrect config references Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 12/20] linux-yocto/rt: udpate SRCREVs to 3.2.9-rt16 Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 13/20] multilib: extend all recipes in multilib.conf Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 14/20] shadow-sysroot: Fix for multilib Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 15/20] gdk-pixbuf: Pick up ${NM} from the environment Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 16/20] mime.bbclass: Fix bracket error Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 17/20] xz: split out liblzma as seperate packages Saul Wold
2012-03-06 21:01 ` Andreas Oberritter
2012-03-06 22:00 ` Khem Raj
2012-03-07 5:55 ` Koen Kooi
2012-03-07 9:45 ` Paul Menzel
2012-03-06 17:03 ` [CONSOLIDATED PULL 18/20] valgrind: Support compilation without X11 Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 19/20] glib-2.0: Add Upstream Status for nodbus.patch Saul Wold
2012-03-06 17:03 ` [CONSOLIDATED PULL 20/20] polkit: Fix Upstream-Status tag Saul Wold
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=1331062925.25887.14.camel@ted \
--to=rpurdie@rpsys.net \
--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