Hello, Others as well as myself have encountered issues with cross compiling various programs making use of configuration scripts created with autoconf. The main issue is that the cross compilation environment causes configuration scripts to produce feature detection binaries matching the architecture of the compilation target, not the compilation host. E.g. the script will try to run an ARM binary on an x86 processor.
Here are two example bugs, filed with the respective project in the hopes of an interim solution: https://savannah.gnu.org/bugs/?50385 https://gitlab.com/jas/libidn2/issues/6 Per my reasoning in those bug reports, my suggestion is to provide another way to pass information to the configuration script. While it seems possible to make configuration scripts compile and run binaries of the proper architecture any results they obtain are irrelevant as they reflect the capabilities of the host, not the target. R0b0t1.
