Bug 14285 - qemuarmv5 kernel config warnings
Summary: qemuarmv5 kernel config warnings
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-oe-core (show other bugs)
Version: 3.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 3.4 M2
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2021-03-08 18:08 UTC by Ross Burton
Modified: 2021-08-17 16:45 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 Ross Burton 2021-03-08 18:08:52 UTC 
WARNING: linux-yocto-5.10.16+gitAUTOINC+8f72218572_98eda36c96-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:

[NOTE]: 'CONFIG_CC_OPTIMIZE_FOR_SIZE' last val (y) and .config val (n) do not match
[INFO]: CONFIG_CC_OPTIMIZE_FOR_SIZE : n ## .config: 159 :configs/v5.10/standard/ktypes/standard/standard.cfg (n) configs/v5.10/standard/arch/arm/arm.cfg (y) 
[INFO]: raw config text:
        config CC_OPTIMIZE_FOR_SIZE
        	bool "Optimize for size (-Os)"
        	depends on <choice>
        	help
        	  Choosing this option will pass "-Os" to your compiler resulting
        	  in a smaller kernel.
        Config 'CC_OPTIMIZE_FOR_SIZE' has the following Direct dependencies (CC_OPTIMIZE_FOR_SIZE=y):
                <choice>
        Parent dependencies are:
             choice [y]
Comment 1 Bruce Ashfield 2021-03-09 13:13:29 UTC 
I assume that this just didn't start showing up in the past little while ?

I've started a local build and will have a look.
Comment 2 Bruce Ashfield 2021-08-17 12:37:51 UTC 
Ross: are you still seeing these ? I haven't been able to trigger it locally.
Comment 3 Ross Burton 2021-08-17 16:45:16 UTC 
No, not seeing this anymore.  You must have fixed it, thanks :)