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<[email protected]>
---
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"
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
