can not support CROSS_COMPILE about yadcc HOT 6 OPEN

IIRC if CROSS_COMPILE is specified, make invokes whatever compiler pointed by this argument, rather than the plain GCC. So I suspect in your build process yadcc is not invoked at all.

Besides, due to the way yadcc works and how fast C code compiles, using yadcc to speed up Linux kernel building process may not see a huge speed up. Last time I try this it gives me about 2x speed up, but that’s it - It was far from what I’d expect from a linear boost.

from yadcc.

icecream support Cross-Compiling, https://github.com/icecc/icecream
Do we have plans to support arm64 cross-compilation? Or provide related documents.

from yadcc.

ADBCC_LOG_LEVEL=0 ADBCC_COMPILE_ON_CLOUD_SIZE_THRESHOLD=0 /opt/buildtools/adbcc_client/bin/adbcc-cxx aarch64-none-linux-gnu-gcc helloworld.c -c
task_dispatcher.cc:327] Unrecognized compilation environment [] is requested by .

from yadcc.

I couldn’t see much difference between cross compilation and a native one regarding distributed compilation.

However, from the log you provided, the compile cluster seemed fail to recognize the compiler. This may have something to do with how compiler is found on compile server.

Because cross-compiler’s executable is usually prefixed with a target triplet, it’s unlikely to be recognized by what’s currently implemented.

Try adding your compiler executable name there and see if that makes any difference.

We may need to reimplement compiler-scanning by enumerating executables and check their suffix, instead of hardcoding executable names.

from yadcc.

fix it by compiler_registry.cc
static constexpr auto kCompilerExecutables = {"gcc",
"g++",
"aarch64-none-linux-gnu-gcc",
"aarch64-none-linux-gnu-g++",
"arm-none-linux-gnueabihf-gcc",
"arm-none-linux-gnueabihf-g++",
// I'm not sure if we support Clang, TBH.
"clang",
"clang++"};

from yadcc.

reopening as this needs improvement in the future.

from yadcc.