On 10 Mar 2017 09:03, Basin Ilya wrote:
> Some authors indeed forget about cross compilation when they publish
> their m4 to autoconf-archive.
>
> Good example is byte order check aka endianness. Before endian.h one way
> to check it was to run a program. But the cross-compile alternative was
> to
Hi.
Some authors indeed forget about cross compilation when they publish
their m4 to autoconf-archive.
Good example is byte order check aka endianness. Before endian.h one way
to check it was to run a program. But the cross-compile alternative was
to grep the binary for a magic byte sequence witho
On 03/09/2017 09:20 PM, R0b0t1 wrote:
> Per my reasoning in those bug reports, my suggestion is to provide
> another way to pass information to the configuration script.
Such a mechanism already exists: cache variables, that you can override
either on the command line (./configure xx_foo=value) or
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 architec
