ERROR: Unknown host CPU architecture: arm64
When compiling the android ndk project built on Android.mk, I found that the following error occurs on the m1 macbook pro
ERROR: Unknown host CPU architecture: arm64
Need to modify the ndk-build file in the ndk root directory (presumably because the m1 belongs to the arm architecture)
#!/bin/sh
DIR="$(cd "$(dirname "$0")" && pwd)"
$DIR/build/ndk-build "$@"
Change to
#!/bin/sh
DIR="$(cd "$(dirname "$0")" && pwd)"
arch -x86_64 /bin/bash $DIR/build/ndk-build "$@"
Read More:
- [Solved] RT-Thread Transplant Error: Error: A1854E: Unknown opcode ‘VSTMFDEQ’, maybe wrong target CPU?
- [Solved] Could not resolve host: yum.dockerproject.org; Unknown error
- [Errno 14] curl#6 – “Could not resolve host: yum.dockerproject.org; Unknown error“
- [Solved] C++ Error: Undefined symbols for architecture x86_64:
- CentOS8 Run rabbitmq-server Error: epmd error for host 172: badarg (unknown POSIX error)
- [Solved] QGC Error: Fail: No CPU load information
- QGC Error: Fail: No CPU load information [How to Solve]
- How to Solve Valgrind 3.14 error on ARM 64
- [Solved] java.lang.UnsatisfiedLinkError: dlopen failed: /lib/arm64/libc++_shared.so not found
- [Solved] RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cpu and
- RabbitMQ:address (cannot connect to host/port) [How to Solve]
- Error: Host Key Verification Failed [How to Solve]
- [Solved] keil arm_math Error: error: #35: #error directive: “Define according the used Cortex cor
- [Solved] ERROR RocketmqCommon-Failed to obtain the host name
- [SpringBoot] Maven Error: Connection refused to host: 127.0.0.1
- Failed to parse host mirrors.opencas.cn [How to Solve]
- [Solved] matlab Error: Error in port widths or dimensions. ‘Output Port 1‘ of ‘sl_arm_ibvs/camera‘
- [Solved] UE4 Error: Serial loading Unknown structure
- if a proxy or similar is necessary `net.git-fetch-with-cli`, Rust Complete `Couldn‘t resolve host name (Coul
- [Solved] Arm Server kibana7.4.1 Error: Sending Logstash logs to /home/logstash-6.8.4/logs which is now configured via log4j2.properties