Bug 13037 - devtool finish busybox fails
Summary: devtool finish busybox fails
Status: RESOLVED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.6
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-11-22 03:06 UTC by chandana kalluri
Modified: 2018-11-22 19:09 UTC (History)
3 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 chandana kalluri 2018-11-22 03:06:20 UTC 
When user runs devtool build busybox, the object files built are stored within the devtool workspace for busybox. As a result, when user runs devtool finish the following error is generated:
ERROR: Source tree is not clean:

?? .busybox_unstripped.cmd
?? .config
?? .config.old
?? .kconfig.d
?? .kernelrelease
?? applets/.applet_tables.cmd
?? applets/.applets.o.cmd
?? applets/.built-in.o.cmd
?? applets/.usage.cmd
?? applets/.usage_pod.cmd
?? applets/Kbuild
?? applets/applet_tables
?? applets/applets.o
?? applets/built-in.o
.
.
.
.
Ensure you have committed your changes or use -f/--force if you are sure there's nothing that needs to be committed

Steps to reproduce:
1. devtool modify busybox
2. devtool build busybox
3. devtool finish busybox meta
Comment 1 Paul Eggleton 2018-11-22 19:09:09 UTC 
This is expected. devtool does not know whether any of these files are uncommitted changes or not, and so takes the precaution of getting you to check. As the message says, if you look at the list and are sure none of these are files you need to commit, then you can use the -f option to bypass the error.