Bug 1925 - oprofileui should DEPEND on avahi
Summary: oprofileui should DEPEND on avahi
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.1
Hardware: Other arm
: Medium normal
Target Milestone: 1.2 M3
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-01-19 04:26 UTC by Freakrob
Modified: 2012-01-26 14:26 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Freakrob 2012-01-19 04:26:52 UTC 
Hi,

I recently pulled the latest version of yocto (1.1+snapshot-20120119) and oprofileui doesn't pass do_configure, citing it cannot find avahi-glib and avahi-client.

I think this might be related to a commit by Saul Wold (comit c89aa6a2b22e05e98991cc5b56d6ec869cf9c69a; http://cgit.openembedded.org/openembedded-core/commit/?id=c89aa6a2b22e05e98991cc5b56d6ec869cf9c69a), when he changed the dependency from avahi to avahi-ui.
I added the dependency back in, so now oprofileui.inc includes DEPENDS avahi as well as avahi-ui and everything works now.
Comment 1 Saul Wold 2012-01-20 15:26:55 UTC 
I would need more information about what target and machine you are building, I just tried a clean build here to check this issue and avahi built belfore avahi-ui since avahi-ui depends on avahi, and then oprofileui built correctly.
Comment 2 Freakrob 2012-01-21 14:50:27 UTC 
I build core-image-sato for an overo machine using the meta-texasinstruments and meta-gumstix layers...

The funny thing is that avahi seemingly did build for me, the pkgconfig files were in the sysroot, yet, the configure failed to find them. It did find them as soon as I made the dependency explicit in there.
Comment 3 Saul Wold 2012-01-26 14:26:15 UTC 
I build this both using oe-core (no distro) and poky, they both worked correctly and dependencies set up via avahi-ui and avahi where found by configure.