forked from Ivasoft/openwrt
busybox: update to version 1.34.0
Update busybox to version 1.34.0 * Remove upstreamed patches (205, 530, 540) * Remove one old patch that does not apply any more. (203) That was originally introduced in 2008 with563d23459, but does not apply after busybox restructuring with https://git.busybox.net/busybox/commit/networking/udhcp/dhcpc.c?h=1_34_stable&id=e6007c4911c3ea26925f9473b9f156a692585f30 and https://git.busybox.net/busybox/commit/networking/udhcp/dhcpc.c?h=1_34_stable&id=1c7253726fcbab09917f143f0b703efbd2df55c3 * Refresh config and patches. * Backport upstream fixes for - MIPS compilation breakage and - process substitution regression Config refresh: Refresh commands, run after busybox is first built once: cd utils/busybox/ cd config/ ../convert_menuconfig.pl ../../../../build_dir/target-aarch64_cortex-a53_musl/busybox-default/busybox-1.34.0 cd .. ./convert_defaults.pl < ../../../build_dir/target-aarch64_cortex-a53_musl/busybox-default/busybox-1.34.0/.config > Config-defaults.in Manual edits needed afterward: * Config-defaults.in: OpenWrt config symbol IPV6 logic applied to BUSYBOX_DEFAULT_FEATURE_IPV6 * Config-defaults.in: OpenWrt configTARGET_bcm53xx logic applied to BUSYBOX_DEFAULT_TRUNCATE (commit547f1ec) * Config-defaults.in: OpenWrt logic applied to BUSYBOX_DEFAULT_LOGIN_SESSION_AS_CHILD (commitdc92917) BUSYBOX_DEFAULT_UDHCPC_DEFAULT_INTERFACE (just "") * config/editors/Config.in: Add USE_GLIBC dependency to BUSYBOX_CONFIG_FEATURE_VI_REGEX_SEARCH (commitf141090) * config/shell/Config.in : change at "Options common to all shells" the symbol SHELL_ASH --> BUSYBOX_CONFIG_SHELL_ASH (discussion in http://lists.openwrt.org/pipermail/openwrt-devel/2021-January/033140.html Apparently our script does not see the hidden option while prepending config options with "BUSYBOX_CONFIG_" which leads to a missed dependency when the options are later evaluated.) * Edit Config.in files by adding quotes to sourced items in config/Config.in, config/networking/Config.in and config/util-linux/Config.in (commit1da014f) Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
This commit is contained in:
committed by
Hans Dedecker
parent
43f0e386d4
commit
b6cbbbb6ef
@@ -12,6 +12,12 @@ config BUSYBOX_CONFIG_ADJTIMEX
|
||||
help
|
||||
Adjtimex reads and optionally sets adjustment parameters for
|
||||
the Linux clock adjustment algorithm.
|
||||
config BUSYBOX_CONFIG_ASCII
|
||||
bool "ascii"
|
||||
default BUSYBOX_DEFAULT_ASCII
|
||||
help
|
||||
Print ascii table.
|
||||
|
||||
config BUSYBOX_CONFIG_BBCONFIG
|
||||
bool "bbconfig (9.7 kb)"
|
||||
default BUSYBOX_DEFAULT_BBCONFIG
|
||||
@@ -788,4 +794,19 @@ config BUSYBOX_CONFIG_WATCHDOG
|
||||
certain amount of time, the watchdog device assumes the system has
|
||||
hung, and will cause the hardware to reboot.
|
||||
|
||||
config BUSYBOX_CONFIG_FEATURE_WATCHDOG_OPEN_TWICE
|
||||
bool "Open watchdog device twice, closing it gracefully in between"
|
||||
depends on BUSYBOX_CONFIG_WATCHDOG
|
||||
default BUSYBOX_DEFAULT_FEATURE_WATCHDOG_OPEN_TWICE # this behavior was essentially a hack for a broken driver
|
||||
help
|
||||
When enabled, the watchdog device is opened and then immediately
|
||||
magic-closed, before being opened a second time. This may be necessary
|
||||
for some watchdog devices, but can cause spurious warnings in the
|
||||
kernel log if the nowayout feature is enabled. If this workaround
|
||||
is really needed for you machine to work properly, consider whether
|
||||
it should be fixed in the kernel driver instead. Even when disabled,
|
||||
the behaviour is easily emulated with a "printf 'V' > /dev/watchdog"
|
||||
immediately before starting the busybox watchdog daemon. Say n unless
|
||||
you know that you absolutely need this.
|
||||
|
||||
endmenu
|
||||
|
||||
Reference in New Issue
Block a user