Hi Masahiro,
On Sat, May 12, 2018 at 01:46:15PM +0900, Masahiro Yamada wrote:
This seems to happen because the Kbuild updates apparently didn't make room for both "*shipped"-based builds and flex/bison-based builds. A similar problem has been reported for genksyms parser in v4.17-rc1 commit 833e622459432e ("genksyms: generate lexer and parser during build instead of shipping"). I have figured out empirically that the warnings are healed after updating the in-tree U-boot DTC to upstream v1.4.6-9, same as done by Linux v4.17-rc1 commit 9130ba88464032 ("scripts/dtc: Update to upstream version v1.4.6-9-gaadd0b65c987"). Whether fixing the DTC-related yacc warnings should be done together with the Kconfig re-sync, I would like to hear from community.
I agree.
Re-sync of scripts/dtc/ should follow.
Included in v2.
# Help text used by make help help: @echo ' config - Update current config utilising a line-oriented program' @@ -152,7 +169,6 @@ help: @echo ' oldconfig - Update current config utilising a provided .config as base' @echo ' localmodconfig - Update current config disabling modules not loaded' @echo ' localyesconfig - Update current config converting local mods to core'
@echo ' silentoldconfig - Same as oldconfig, but quietly, additionally update deps' @echo ' defconfig - New config with default from ARCH supplied defconfig' @echo ' savedefconfig - Save current config as ./defconfig (minimal config)' @echo ' allnoconfig - New config where all options are answered with no'@@ -161,7 +177,7 @@ help: @echo ' alldefconfig - New config with all symbols set to default' @echo ' randconfig - New config with random answer to all options' @echo ' listnewconfig - List new options'
@echo ' olddefconfig - Same as silentoldconfig but sets new symbols to their'
@echo ' olddefconfig - Same as oldconfig but sets new symbols to their' @echo ' default value'Linux commit cedd55d49dee added 'without prompting' after 'default value'
Could you do likewise please?
Missed that one! Fixed in v2. Thanks!
Best regards, Eugeniu.