Bug 1690

Summary:	Building an image for qemu* machines always builds X11
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Paul Eggleton <bluelightning>
Component:	core	Assignee:	Paul Eggleton <bluelightning>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	jessica.zhang, meta.mr.watcher, meta.watcher
Version:	unspecified
Target Milestone:	1.3
Hardware:	Other
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Paul Eggleton 2011-10-21 08:53:31 UTC

Because building an image for a qemu machine requires qemu-config, and qemu-config requires dbus-x11, distcc (which for some reason needs gtk+) and oprofileui-server (requiring a build of oprofileui), it requires X11 to be built. If you have removed x11 from DISTRO_FEATURES then this will fail.

Comment 1 Paul Eggleton 2011-11-04 08:20:10 UTC

I have a fix for the oprofileui-server X11 dependency; however it requires a patch to oprofileui itself (specifically its configure script). I've submitted that "upstream" and will wait until it gets merged, and will then submit the corresponding metadata patch.

The other half of this problem is due to anjuta-remote-run requiring dbus. Since we no longer support anjuta should this just be removed?

Comment 2 Paul Eggleton 2011-11-23 09:18:10 UTC

The oprofileui upstream fix has been merged, but the proposed fix for the metadata received some negative feedback. After discussion with a few people I'm going to rework qemu-config into a task which is a little more generic and tidy that does not always install distcc; this will mean splitting out its components into separate recipes.

Comment 3 Jessica 2012-01-03 10:42:57 UTC

Paul, thought saw some patches from you regarding these? are they finalized yet? if so, please update the bug accordingly. thx

Comment 4 Paul Eggleton 2012-01-03 14:42:04 UTC

I produced a new set of patches for this but they are not yet finished.

Comment 5 Jessica 2012-03-08 20:32:02 UTC

Paul, is this bug fixed by now? please update the status if there's change

Comment 6 Paul Eggleton 2012-03-23 18:02:58 UTC

So it's worth noting at this point that the underlying problem of not being able to build for a qemu machine has since been fixed by Xiaofeng Yan in commit 8de191d64aa7fa3a6c3e3fde2acca5949f36c95e. We still build a bunch of things that demand x11 for qemu machines when x11 *is* in DISTRO_FEATURES though, even if we're building a minimal images. I'm convinced we can still improve here.

Comment 7 Paul Eggleton 2012-03-24 15:49:57 UTC

Moving to 1.3.

Comment 8 Paul Eggleton 2012-08-15 12:44:18 UTC

Noted here because it hasn't been already - the workaround for this is to force POKYQEMUDEPS to "" (you may need to use an override such as forcevariable). This issue is specific to Poky and does not affect OE-Core.

Comment 9 Paul Eggleton 2012-08-20 10:39:41 UTC

New RFC patch sent to the OE-Core list:

http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/028236.html

Comment 10 Paul Eggleton 2012-09-05 15:00:21 UTC

This has finally been fixed and merged to poky master in the following revisions:

f6ae5d8b04f126e4de89b9d98b1bc115bc543869
80908c9f83660c10e39bd5ffb48bb6e417d14006
125650776991e40168dcab1dca372cc3ebe1d490
c2e68c6fb9be169f274453412565cb6376770b2b
54b8e84356b513b0fa6e5bcdfed75000ff8e0575
c8d739488574e422751f8d0f6052cdc0ef1429de
cbd1d867524dd86bb1b6922b5694e960db263e06

Note, despite earlier comments, before these changes it was still the case that the system would start to build components such as GTK+ on a system without x11 in DISTRO_FEATURES, that is now fixed.