c3c4b3dfa8
The C program inside check-kernel-headers.sh has two checking mode: a strict and a loose one. In strict mode, we want the kernel headers version declared by the user to match exactly the one of the toolchain. In loose mode, we want the kernel headers version of the toolchain to be greater than or equal to the one declared by the user: this is used when we have a toolchain that has newer headers than the latest version known by Buildroot. However, in loose mode, we continue to show the "Incorrect kernel headers version" message, even though we then return a zero error code. This is very confusing: you see an error displayed on the terminal, but the build goes on. We fix that by first doing the loose check first, and returning 0 if it succeeds. And then we move on with the strict check where we want the version to be identical. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
---|---|---|
.. | ||
apply-patches.sh | ||
br2-external | ||
brpkgutil.py | ||
check-bin-arch | ||
check-host-rpath | ||
check-kernel-headers.sh | ||
check-merged-usr.sh | ||
eclipse-register-toolchain | ||
expunge-gconv-modules | ||
fix-configure-powerpc64.sh | ||
fix-rpath | ||
generate-gitlab-ci-yml | ||
genimage.sh | ||
graph-build-time | ||
graph-depends | ||
hardlink-or-copy | ||
mkmakefile | ||
mkusers | ||
pkg-stats | ||
pycompile.py | ||
setlocalversion | ||
size-stats |