I also gave Autotools a spin with an updated config.sub. Autotools rewrites the triplet and provides an accurate machine:
armv7l-unknown-linux-gnueabihf
The -dumpmachine option is very important. It is the option that tells us what we are building for. It may be different than the host architecture. Personally, I don't care about the host arch and cross-compiles. Everything is just a compile to me, and all GNUmake and Autoconf decisions are based on MACHINE in the triplet.
I tested a LePotato, which is an Aarch64 dev-board from the same maker (https:/ /www.amazon. com/gp/ product/ B074N5B8KZ). Here are the results. They look OK:
$ gcc -dumpmachine linux-gnu
aarch64-
$ clang -dumpmachine unknown- linux-gnu
aarch64-
I also gave Autotools a spin with an updated config.sub. Autotools rewrites the triplet and provides an accurate machine:
armv7l- unknown- linux-gnueabihf
The -dumpmachine option is very important. It is the option that tells us what we are building for. It may be different than the host architecture. Personally, I don't care about the host arch and cross-compiles. Everything is just a compile to me, and all GNUmake and Autoconf decisions are based on MACHINE in the triplet.