Bug 11880 - kernel-devsrc: multiple System.map files present in kernel-build-artifacts
Summary: kernel-devsrc: multiple System.map files present in kernel-build-artifacts
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: kernel (show other bugs)
Version: 2.4
Hardware: All Multiple
: Medium normal
Target Milestone: 2.5 M2
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-08-01 13:46 UTC by Jonathan Liu
Modified: 2017-12-11 01:00 UTC (History)
2 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 Jonathan Liu 2017-08-01 13:46:29 UTC 
If you build build linux kernel recipe, change the version and build it again you end up with multiple System.map files in build/tmp/work-shared/*/kernel-build-artifacts.

For example:
System.map-4.12.2
System.map-4.12.3
System.map-4.12.4

If your image recipe has kernel-devsrc in TOOLCHAIN_TARGET_TASK, then bitbake myimage -c populate_sdk will include these System.map files for multiple kernel versions besides the one currently being used.

Probably only the System.map file for the current kernel version should end up in kernel-devsrc?
Comment 1 Bruce Ashfield 2017-08-15 14:14:38 UTC 
Accepting this. But it is unlikely that I'll have cycles for it this release. putting to m4, since this would be a stabilization fix.
Comment 2 Saul Wold 2017-11-22 18:48:07 UTC 
I think that adding a do_shared_workdir[cleandirs] entry for the kernel-build-artifacts, should address this.