Bug 6630 - linux-yocto: kernel-dev package does not include target arch scripts binaries
Summary: linux-yocto: kernel-dev package does not include target arch scripts binaries
Status: RESOLVED DUPLICATE of bug 4389
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: linux-yocto (show other bugs)
Version: 1.7
Hardware: All Multiple
: Undecided enhancement
Target Milestone: 4.99
Assignee: Juro Bystricky
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-08-14 15:25 UTC by Darren Hart
Modified: 2018-10-11 15:04 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 Darren Hart 2014-08-14 15:25:46 UTC 
In order to build modules on the target, you first have to build the scripts binaries on the target:

$ cd /usr/src/kernel
$ make scripts

This is unexpected and tends to confuse developers.

The kernel-dev package should have these binaries built for the target arch.
Comment 1 Saul Wold 2016-07-25 20:52:20 UTC 
See also#4389
Comment 2 Bruce Ashfield 2017-06-21 18:35:53 UTC 
Cycles are questionable to get to this. If someone else can look into it, that would be great.
Comment 3 Bruce Ashfield 2018-02-16 00:00:44 UTC 
See my update to https://bugzilla.yoctoproject.org/show_bug.cgi?id=4389, there are technical issues in the way of doing this.
Comment 4 Juro Bystricky 2018-02-16 23:34:31 UTC 
I also added some comments in
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4389,
I believe fixing 4389 will also address this one (6630).
In any case, the changes will affect kernel-devsrc (not kernel-dev).
Comment 5 Robin Jordan 2018-03-15 11:01:24 UTC 
Please update this milestone.  If it is not going into 2.5 push to 2.99.
Comment 6 Richard Purdie 2018-10-11 15:04:47 UTC 
I believe fixing 4389 will also fix this.

*** This bug has been marked as a duplicate of bug 4389 ***