On Monday, November 22, 2021, <mnieuw@zap.a2000.nl> wrote:

Building CinGG for aarch64.

In multiple places in the build tree, ./configure reports that it cannot
guess the build type. This is because "uname -p" returns unknown. I just
found out that this is quite common. On arm, only a few distributions
patch uname to return the same value as "uname -m" . Debian does not,
but Fedora does. So I am ditching the Debian VM, and create a Fedora
aarch64 VM instead. That will hopefully fix the "cannot build" error.

try to study attached patch I made as part of effort to build Cin on elbrus machine.

there was plenty of places where autoreconf fixes things...

BUT i have not tested those modifications on more standard and older x86 distros.... (you hopefully can ignore nasm pieces, this was part of another patch)

A second point is that any nasm call is obviously for the wrong
CPU, so any product build that uses nasm should be disabled with a
configure options.

well, at least libopus as configured by cingg was building fine here ...

MatN