Bug 2020

Summary:	bitbake meta-toolchain fails when removing x11 from DISTRO_FEATURES
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	David Nyström <david.nystrom>
Component:	graphics	Assignee:	Paul Eggleton <bluelightning>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	bjst, bluelightning, meta.mr.watcher, meta.watcher, sgw
Version:	1.1
Target Milestone:	1.2
Hardware:	All
OS:	Multiple
Whiteboard:	Patch merged (24 Feb)
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description David Nyström 2012-02-22 01:21:09 UTC

On Tuesday 21 February 2012 11:31:54 John Toomey wrote:
> I am getting the following error when trying to build meta-toolchain:
>
>     NOTE: Resolving any missing task queue dependencies
>     ERROR: Nothing PROVIDES 'libx11-nativesdk' (but
>    
> virtual:nativesdk:[path]/jtoomey/poky/meta/recipes-graphics/libsdl/libsdl_1
> .2.14.bb DEPENDS on or otherwise requires it)
>     ERROR: libx11-nativesdk was skipped: X11 not enabled for this DISTRO
>     NOTE: Runtime target 'qemu-nativesdk' is unbuildable, removing...
>     Missing or unbuildable dependency chain was: ['qemu-nativesdk',
>     'libsdl-nativesdk', 'libx11-nativesdk']
>     NOTE: Runtime target 'task-sdk-host-nativesdk' is unbuildable,
>     removing...
>     Missing or unbuildable dependency chain was:
>     ['task-sdk-host-nativesdk', 'qemu-nativesdk', 'libsdl-nativesdk',
>     'libx11-nativesdk']
>     ERROR: Required build target 'meta-toolchain' has no buildable
>     providers.
>     Missing or unbuildable dependency chain was: ['meta-toolchain',
>     'task-sdk-host-nativesdk', 'qemu-nativesdk', 'libsdl-nativesdk',
>     'libx11-nativesdk']
>
> I dont really need or want X11 but the toolchain seems to depend on
> parts of it.
I'm guessing this is because we haven't tested building meta-toolchain when 
x11 has been removed from DISTRO_FEATURES; at minimum it seems we would need 
to fix the libsdl recipe to be able to build without libx11 when x11 is not in 
DISTRO_FEATURES.

Would you mind filing a bug for this in the Yocto Project bugzilla 
(http://bugzilla.yoctoproject.org)?

Comment 1 David Nyström 2012-02-22 01:27:07 UTC

I see this bug on edison. I think the bug is valid in poky-latest as well.

Comment 2 Paul Eggleton 2012-02-22 09:11:19 UTC

This does affect latest master as well. Unfortunately this is probably too late to get a fix into the upcoming 1.1.1 edison release but I think there may be a 1.1.2 release planned which it could potentially be a candidate for.

I've now got two patches here which allow meta-toolchain to build successfully without x11:

http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/meta-toolchain-nox

I'm just waiting on an answer about tidying up the QEMU recipes before sending the patches out to the mailing list.

FYI some tweaks are also required to the runqemu script to make it useful without X, I plan to fix those as a separate exercise.

Comment 3 David Nyström 2012-02-23 00:18:00 UTC

(In reply to comment #2)

Patch submitted 8 hours after initial bugreport. I'm impressed.

I actually started working with this after I filed it, and Paul was considerably faster :).

For future reference to avoid double working:
  
How can I as a yocto newbie detect if work is ongoing for bug X ?
How can someone external (such as me), opt to fix a bug ?
Is there any documentation on how bugzilla is used within the yocto project?

Comment 4 Paul Eggleton 2012-02-23 01:25:49 UTC

There is indeed:

https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking

Basically, when the bug status is changed to "accepted" it's a good bet the bug is being worked on, although for the benefit of the bug triage team and management we try to keep the "Whiteboard" field up-to-date as well. That said if there's an "accepted" bug and you're already working on it / would like to work on it / already have a fix then it's fine to just comment on the bug to that effect. We're pretty flexible :)

In the case of this bug I saw that several people were waiting on it, it was along the lines of some other work I've done recently, and the solution didn't appear to be too tricky, so I dug straight in.

Comment 5 Paul Eggleton 2012-02-24 10:07:48 UTC

Fix merged to master in commits ef36dc896d57c8c002222224ac468ac87ef9963e and 189a854e8deff6c6ffa3f1e22725a038ec83471f.

I'll make a note to consider this for 1.1.2.