From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] recipes-devtools/qemu/qemu.inc: Add jpeg as a dependency
Date: Tue, 22 May 2012 11:46:48 -0700 [thread overview]
Message-ID: <4FBBDF18.9030500@linux.intel.com> (raw)
In-Reply-To: <1337709995-13798-1-git-send-email-jason.wessel@windriver.com>
On 05/22/2012 11:06 AM, Jason Wessel wrote:
> If you use a shared state cache and build a large file system,
> followed by a small one, the qemu will be built with jpeg support.
>
Is jpeg optional for qemu? Do you know why it's included in the first
place? Can it be disabled via a --disable in the configure stage?
Sau!
> Building ultra small file systems leaves out jpeg as a dependency
> for the host tool, and when using a sstate cache you end up with
> the following error using runqemu:
>
> qemu: error while loading shared libraries: libjpeg.so.8: cannot open shared object file: No such file or directory
>
> The work around is to execute:
> bitbake jpeg-native
>
> Signed-off-by: Jason Wessel<jason.wessel@windriver.com>
> ---
> meta/recipes-devtools/qemu/qemu.inc | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc
> index 93325c3..bd9e5bf 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -1,7 +1,7 @@
> DESCRIPTION = "open source processor emulator"
> HOMEPAGE = "http://qemu.org"
> LICENSE = "GPLv2& LGPLv2.1"
> -DEPENDS = "glib-2.0 zlib alsa-lib virtual/libx11"
> +DEPENDS = "glib-2.0 zlib alsa-lib virtual/libx11 jpeg"
>
> # QEMU_TARGETS is overridable variable
> QEMU_TARGETS ?= "arm i386 mips mipsel mips64 mips64el ppc sh4 x86_64"
next prev parent reply other threads:[~2012-05-22 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 18:06 [PATCH] recipes-devtools/qemu/qemu.inc: Add jpeg as a dependency Jason Wessel
2012-05-22 18:46 ` Saul Wold [this message]
2012-05-22 23:39 ` Jason Wessel
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=4FBBDF18.9030500@linux.intel.com \
--to=sgw@linux.intel.com \
--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.