Bug 4225

Summary: Build configuration printed by BitBake does not show correct set of features
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Carlos Rafael Giani <crg7475>
Component: coreAssignee: Richard Purdie <richard.purdie>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: corneliux.stoicescu, meta.mr.watcher, meta.watcher
Version: unspecified   
Target Milestone: 1.5   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Carlos Rafael Giani 2013-04-08 14:45:53 UTC 
When I try to set the DEFAULTTUNE value for a specific machine in local.conf, the build configuration printed by bitbake does not list what I set. Example:

I set  DEFAULTTUNE_beagleboard = "cortexa8hf-neon"  in the local.conf. Running bitbake does not show "callconvention-hard" in the printed TUNE_FEATURES list. But running  bitbake -e | grep "callconvention-hard"  reveals that it actually *is* being used, just not printed by bitbake.

However, when setting DEFAULTTUNE instead of DEFAULTTUNE_<machine> , bitbake prints it correctly.

This behavior has been observed in both danny and master. http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/30164 mentions it, and also mentions this patch: http://patches.openembedded.org/patch/39871/ . The patch does not seem to help.

While the build finishes correctly, the erroneous build configuration output can be very confusing and raise false alarms.
Comment 2 Stoicescu Cornel 2013-10-09 10:55:16 UTC 
Verified in:
poky dora:102bf5e0f640fe85068452a42b85077f1c81e0c9