Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | check-toolchain-clean.sh: workaround stray rebuilds | Petr Štetiar | 2022-02-28 | 1 | -2/+7 |
| | | | | | | | | | | | | | | | | 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> | ||||
* | check-toolchain-clean.sh: fix shellcheck warnings | Petr Štetiar | 2022-02-28 | 1 | -1/+1 |
| | | | | | | | | | | | 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> | ||||
* | toolchain: add a version that can be bumped to force toolchain/target rebuild | Felix Fietkau | 2021-11-16 | 1 | -0/+9 |
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> |