Bug 5852 - binconfig.bbclass patch didn't affect signatures as it should have
Summary: binconfig.bbclass patch didn't affect signatures as it should have
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.5.1
Hardware: All Multiple
: Medium minor
Target Milestone: 1.6
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-02-20 11:40 UTC by Paul Eggleton
Modified: 2014-03-31 10:06 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

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 Paul Eggleton 2014-02-20 11:40:47 UTC 
Poky rev 9203c879b333e7b1c390f43389cb917ae065185e ought to have resulted in libusb-compat being rebuilt (or, to be strictly correct, the appropriate tasks to be re-executed). For some reason it did not and the result was that existing sstate-cache was re-used for libusb-compat and the issue wasn't fixed (libftdi failed with the QA error referred to in the commit message). I'd like us to investigate why that happened.
Comment 1 Paul Eggleton 2014-03-31 10:06:13 UTC 
The problem was a missing dependency. The fix has now been merged to master, plus a related warning fix:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=5d8552e1b4378dbde8439b2b7eb20c882e166a62
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=169d67e282d80a242f5ba6efb9c9738f54a51eb4