AES not enabled for cross compilation targeting aarch64

[TuanTranBPK]

I have a x86_64 host machine (Ubuntu 24.04) that is used to cross-compile a program using libsodium to be deployed on ARMv8 machine. I'm using the toolchain toolchain-aarch64_cortex-a53_gcc-8.4.0_musl for cross-compilation.

The target machine supports AES HW acceleration as shown by "cat /proc/cpuinfo" below. The program can't use AES-based ciphers for HW acceleration.

The build script, build log and config log are found in the attachments.

I'm wondering whether it's a misconfiguration. Would you have any hints ?

build-script.txt
config.log
cpuinfo.txt
build.log

[jedisct1]

Does your program call sodium_init() prior to doing anything else with the library?

[TuanTranBPK]

I think there is a cross-compilation issue that's why the crypto_aead_aes256gcm_is_available() failed.

I'll try Zig but I'm not sure this solution is feasible because the target machine is an embedded system where the embedded system provider gives me the toolchain.

[jedisct1]

It will give you a static library, that you can then use with any toolchain.

[TuanTranBPK]

I'll try tomorrow and let you know

[TuanTranBPK]

Thanks a lot for your support, the Zig build works for aarch64.

By the way, I have another environment where the CPU is ARMv8 but the OS and softwares run on 32-bits, is it the right command to build the library in this case ?

zig build -Doptimize=ReleaseFast -Dtarget=arm-linux -Dcpu=cortex_a53

processor : 0 BogoMIPS : 100.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x42 CPU architecture: 8 CPU variant : 0x0 CPU part : 0x100 CPU revision : 0

[jedisct1]

Yes, that's the right command for arm32.

[TuanTranBPK]

Thanks

[TuanTranBPK]

It seems that AES isn't enabled when setting ARM 32-bits target on aarch64 CPU with zig build -Doptimize=ReleaseFast -Dtarget=arm-linux -Dcpu=cortex_a53. I attached the objdump output in 2 cases, would you have any hints ?
objdump-output-aarch64.txt
objdump-output-arm.txt

[jedisct1]

In your configuration script, you define CFLAGS_ARMCRYPTO, but don't seem to use it. These may help to bypass detection.

[TuanTranBPK]

The compilation with "zig build" works so my original build script is not relevant anymore.