Manually specified CROSS_COMPILE no longer works with null runtime

[nathanchance]

Specifying CROSS_COMPILE used to work for setting the triple for a particular environment.

$ uvx --with tuxmake==1.36.0 tuxmake -a arm -k defconfig -t gcc CROSS_COMPILE=arm-linux-gnueabi- default
tuxmake --target-arch=arm --kconfig=defconfig --toolchain=gcc --wrapper=none --environment=KBUILD_BUILD_TIMESTAMP=@1775583229 --environment=KBUILD_BUILD_USER=tuxmake --environment=KBUILD_BUILD_HOST=tuxmake --environment=KCFLAGS=-ffile-prefix-map=/run/host/home/nathan/.cache/tuxmake/builds/2/build/= --runtime=null --image=docker.io/tuxmake/arm_gcc CROSS_COMPILE=arm-linux-gnueabi- config default
make --silent --keep-going --jobs=32 O=/run/host/home/nathan/.cache/tuxmake/builds/2/build ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- defconfig
make --silent --keep-going --jobs=32 O=/run/host/home/nathan/.cache/tuxmake/builds/2/build ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-
...

But now it unconditionally errors.

$ uvx --with tuxmake==1.37.0 tuxmake -a arm -k defconfig -t gcc CROSS_COMPILE=arm-linux-gnueabi- default
E: Compiler not found: arm-linux-gnueabihf-gcc
Install the compiler or use a container-based runtime (e.g. --runtime=docker/podman)

I am not sure which PR broke this.

[roxell]

Hi Nathan,

Thank you for the report.

This is from two commits in 1.37.0:

• 472ce8f ("runtime: null: check if compiler exists on host")
• 9f457b8 ("build: raise CompilerNotFoundError for null runtime")

The null runtime checks if the compiler exists before building.
But it uses the default CROSS_COMPILE from the arch config (arm-linux-gnueabihf-) and ignores the one from the command line (arm-linux-gnueabi-)...

I have a fix on fix-null-runtime-cross-compile-check that passes the user-supplied CROSS_COMPILE to the check.

Please have a look if it make sense and works for you.

[bhcopeland]

Merged, we should add some integration tests here in future to catch these changes. Thanks for the report @nathanchance