openwrt/scripts/check-toolchain-clean.sh

#!/bin/sh
eval "$(grep CONFIG_GCC_VERSION .config)"
CONFIG_TOOLCHAIN_BUILD_VER="$CONFIG_GCC_VERSION-$(cat toolchain/build_version)"
touch .toolchain_build_ver
CURRENT_TOOLCHAIN_BUILD_VER="$(cat .toolchain_build_ver)"
[ -z "$CURRENT_TOOLCHAIN_BUILD_VER" ] && {
	echo "$CONFIG_TOOLCHAIN_BUILD_VER" > .toolchain_build_ver
	exit 0
}
[ "$CONFIG_TOOLCHAIN_BUILD_VER" = "$CURRENT_TOOLCHAIN_BUILD_VER" ] && exit 0
echo "Toolchain build version changed ($CONFIG_TOOLCHAIN_BUILD_VER != $CURRENT_TOOLCHAIN_BUILD_VER), running make targetclean"
make targetclean
echo "$CONFIG_TOOLCHAIN_BUILD_VER" > .toolchain_build_ver
exit 0
toolchain: add a version that can be bumped to force toolchain/target rebuild This can be used to ensure that the compiled code is up to date, when something important changes in the toolchain. A recent example of this is the gcc 11 fix for a code miscompilation issue Signed-off-by: Felix Fietkau <nbd@nbd.name> 2021-11-16 20:46:21 +00:00			`#!/bin/sh`
check-toolchain-clean.sh: fix shellcheck warnings Fixes following complaints and suggestions: In scripts/check-toolchain-clean.sh line 2: eval `grep CONFIG_GCC_VERSION .config` ^-- SC2046 (warning): Quote this to prevent word splitting. ^-- SC2006 (style): Use $(...) notation instead of legacy backticks `...`. Signed-off-by: Petr Štetiar <ynezz@true.cz> 2022-02-25 10:15:45 +00:00			`eval "$(grep CONFIG_GCC_VERSION .config)"`
toolchain: add a version that can be bumped to force toolchain/target rebuild This can be used to ensure that the compiled code is up to date, when something important changes in the toolchain. A recent example of this is the gcc 11 fix for a code miscompilation issue Signed-off-by: Felix Fietkau <nbd@nbd.name> 2021-11-16 20:46:21 +00:00			`CONFIG_TOOLCHAIN_BUILD_VER="$CONFIG_GCC_VERSION-$(cat toolchain/build_version)"`
			`touch .toolchain_build_ver`
check-toolchain-clean.sh: workaround stray rebuilds It seems, that there are currently some unhandled corner cases in which `.toolchain_build_ver` results in empty file and thus forcing rebuilds, even if the toolchain was build correctly just a few moments ago. Until proper fix is found, workaround that by checking for this corner case and simply populate `.toolchain_build_ver` file. While at it, improve the UX and display version mismatch, so it's more clear what has forced the rebuild: "Toolchain build version changed (11.2.0-1 != ), running make targetclean" References: https://gitlab.com/ynezz/openwrt/-/jobs/2133332533/raw Signed-off-by: Petr Štetiar <ynezz@true.cz> 2022-02-24 16:37:45 +00:00			`CURRENT_TOOLCHAIN_BUILD_VER="$(cat .toolchain_build_ver)"`
			`[ -z "$CURRENT_TOOLCHAIN_BUILD_VER" ] && {`
			`echo "$CONFIG_TOOLCHAIN_BUILD_VER" > .toolchain_build_ver`
			`exit 0`
			`}`
			`[ "$CONFIG_TOOLCHAIN_BUILD_VER" = "$CURRENT_TOOLCHAIN_BUILD_VER" ] && exit 0`
			`echo "Toolchain build version changed ($CONFIG_TOOLCHAIN_BUILD_VER != $CURRENT_TOOLCHAIN_BUILD_VER), running make targetclean"`
toolchain: add a version that can be bumped to force toolchain/target rebuild This can be used to ensure that the compiled code is up to date, when something important changes in the toolchain. A recent example of this is the gcc 11 fix for a code miscompilation issue Signed-off-by: Felix Fietkau <nbd@nbd.name> 2021-11-16 20:46:21 +00:00			`make targetclean`
			`echo "$CONFIG_TOOLCHAIN_BUILD_VER" > .toolchain_build_ver`
			`exit 0`