On Thu, Jun 12, 2025 at 07:07:09PM +0200, Jose Gomez wrote: > Is arm-linux-gnueabihf-gcc not a cross compiler then?, it is in make output It is a supported configuration. Whether it is a cross-compiler or not depends on what you built it on, and what you will run it on. If build=host=target, this is a "native compiler". You typically configure this by specifying none of --build=, --host=, or --target= . If build=host but not equal to the target, it is a cross-compiler. You usually configure with just a suitable --target= , and not more. If host=target but not equal to the build system, it is a cross-built native compiler, not a usual thing. If build=target but not equal to the host, it is called a "cross-back". *Very* unusual. You can also have all of build, host, and target different, this is known as a "canadian cross". Used by people who want an extra challenge, or who want to test the GCC build system very, very thoroughly :-) You were configuring for a cross-built native. You cannot (successfully) build that unless you already have a cross-compiler for that target, running on your build system You probably wanted to configure for a cross-compiler instead. Just don't use --host= (or any other unnecessary options for that matter), configure itself will figure out what you want to do. Well, it won't read your mind, but it will assume the common case, and criss-compilers are very common :-) Segher