Running "make distclean" first solved it.
./configure --host=aarch64-linux-gnu --prefix=/opt/install-arm64/papi-5.6.1.0 --with-ffsll --with-walltimer=cycle --with-tls=__thread --with-virtualtimer=perfctr --with-perf-events --with-arch=aarch64 --with-CPU=arm
make
sudo make install
To install those binary files in /opt/install-arm64/papi-5.6.1.0.
Answer from LuisM on Stack OverflowDoes anyone here cross compile for arm64 musl? do you get frequent issues doing it?
gcc - cross-compile for ARM64, understanding make TARGET=aarch64 - Stack Overflow
how can I cross compile an assembly and a .c file to arm64 on macos?
Instructions on how to cross compile Windows (amd64 -> arm64)
Videos
I get frequent issues doing it, and I wonder if its just how things are, or if theres something I can do to make it better.
I tried to cross compile portage packages on a amd64 glibc as a binhost thing for the aarch64-musl target. I did this by creating a musl chroot on the amd64 system.
Initially, I could not even get the cross chain to do anything. I eventually figured it out and filed a bug report here https://bugs.gentoo.org/909453
But still, many packages failed compilation. I figured this may be the reality of cross compiling, so I still installed on the arm64 system the ones that did not fail cross compile, But now it does not connect to the internet and can no longer ssh to it (debugging at the moment)
Is this a frequent occurrence with this kind of setup? Am I better off switching away from musl, or is this just amd64 to arm64 issue?
Install gcc-arm-linux-gnueabi and binutils-arm-linux-gnueabi packages, and then just use arm-linux-gnueabi-gcc instead of gcc for compilation.
You need to be careful on what flavour of linux and binutils you have on your target system. The newest stuff is hardfloat, in this case you would do:
sudo apt-get install gcc-arm-linux-gnueabihf
This brings in the complete cross-compile environment, including binutils.
For using this GCC in the build process write:
CC=arm-linux-gnueabihf-gcc make
64-bit ARM
For 64-bit ARM, the toolchain prefix is aarch64 and usage is:
sudo apt install gcc-aarch64-linux-gnu
aarch64-linux-gnu-gcc -o main.out main.c
You can try it out on this C hello world with QEMU:
main.c
#include <stdio.h>
int main(void) {
puts("hello");
}
and then:
sudo apt install qemu-user
qemu-aarch64 main.out
will output:
hello
Then a few fun things you can do to quickly see that ARM is actually running under the hood:
- GDB step debug it: https://stackoverflow.com/questions/20590155/how-to-single-step-arm-assembly-in-gdb-on-qemu/51310791#51310791
- log the executed ARM instructions with:
qemu-aarch64 -d in_asm,out_asm main.outhttps://stackoverflow.com/questions/13005303/how-does-native-android-code-written-for-arm-run-on-x86/44505097#44505097
Tested in Ubuntu 19.10.
For reliability in serious applications, the disk image provider must also provide a compatible cross compiler
Although you can install a cross compiler with apt conveniently, I must warn you that this is not necessarily reliable unless explicitly supported by the image provider.
If you pick the cross compiler wrongly, the following may happen:
- the dynamic linker is at the wrong path: https://stackoverflow.com/questions/31929092/trying-to-run-a-cross-compiled-executable-on-target-device-fails-with-no-such-f/49993116#49993116
- binary incompatibility with the glibc and any other libraries you link against: https://stackoverflow.com/questions/11107263/how-compatible-are-different-versions-of-glibc
Raspberry PI cross compilation
For RPI in particular, the provided cross compilers are available at: https://github.com/raspberrypi/tools and can be used as explained at: https://raspberrypi.stackexchange.com/questions/64273/installing-raspberry-pi-cross-compiler/83215#83215
git clone https://github.com/raspberrypi/tools
export PATH="$(pwd)/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin:${PATH}"
printf '#include <stdio.h>\nint main() { puts("hello world"); }\n' > hello_world.c
printf '#include <iostream>\nint main() { std::cout << "hello world" << std::endl; }\n' > hello_world.cpp
arm-linux-gnueabihf-gcc -std=c99 -o hello_world_c hello_world.c
arm-linux-gnueabihf-g++ -std=c++11 -o hello_world_cpp hello_world.cpp
Ubuntu cross compilation
If you want to cross compile for Ubuntu arm64, I have never been able to find a clear reference on which cross compilers support which distro version: What are the officially supported cross compilers for Ubuntu server alternative architectures like ARM?
Buildroot
My favorite alternative is to build your own image with Buildroot: https://stackoverflow.com/questions/47557262/how-to-download-the-torvalds-linux-kernel-master-recompile-it-and-boot-it-wi/49349237#49349237
This builds everything from source, including the toolchain and the image, and ensures that everything is compatible.
Hello,
I know this is a beginner question - I have been trying for hours to run a small kernel with qemu-system-aarch64 on macos. I want to compile without standard library and have written a linker script to correctly place the _start function.
I have the following files: boot.S kernel.c link.ld
I tried a lot. When using "clang -target aarch64 -nostdlib boot.S kernel.c -o kernel.o" to link it afterwards I get a linker error. I also tried the -c flag as written in the man page of gcc.