On Tue, Dec 1, 2015 at 10:16 AM, Bernd Edlinger
<bernd.edlin...@hotmail.de> wrote:
> Your host_alias looks wrong: isn't it equal to your build_alias ?
Yes. The goal is to basically build a native compiler but prevent it
from trying to run any binaries. There is no fine-grained way to tell
the configuration mechanism to run x86-64 and x86 binaries, but not
x32 binaries.
The config mechanism I use worked nicely for quite a while until this
one change. All the other libraries have no issue with the
configuration. It's been a long time since I dug deeply into all this
autoconf magic. It just seems that in libvtv the settings are applied
differently. I do see this of course:
if test "x$host_alias" != x; then
if test "x$build_alias" = x; then
cross_compiling=maybe
$as_echo "$as_me: WARNING: If you wanted to set the --build type,
don't use --host.
If a cross compiler is detected then cross compile mode will be used." >&2
elif test "x$build_alias" != "x$host_alias"; then
cross_compiling=yes
fi
fi
This will cause cross_compiling not to be set. The question is
whether libvtv is really unique in its requirements or whether the
other configure scripts in the project are doing something more to
prevent this type of problem.
