[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: x86_64-redhat-linux-ar not found
From: |
ctarbide |
Subject: |
Re: x86_64-redhat-linux-ar not found |
Date: |
Sun, 26 Jul 2020 15:41:18 +0200 (CEST) |
Jul 26, 2020, 06:19 by bruno@clisp.org:
Hi,
I was able to successfully build libffcall, but only after adding --build="$host_triple" to all configure calls in cross-tools/cross-build.sh
What was the error that you got without this option?
Not all cross tools give error, mips fail, i386, x86_64 and m68k goes fine, the error:
make[2]: x86_64-redhat-linux-ar: Command not found
And what was the --host option that you passed? --host=x64_64-unknown-linux-gnu
or --host=x86_64-redhat-linux?
Here goes the last configure excerpt before the error (full log attached):
config.status: executing default-1 commands
mkdir -p -- ./bfd
Configuring in ./bfd
configure: creating cache ./config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-redhat-linux-gnu
checking target system type... mips64-unknown-linux-gnu
checking for x86_64-redhat-linux-gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
Autoconf seems to suggest [3] using both "build" and "host" flags for cross building, though I don't have many experience in cross building, hope this helps in some way.
This doc section is misleading; it will be corrected in the next Autoconf
release [1].
Bruno
[1] https://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=fc1fe985411216165116520b444cdeaae237b6fb
build.log
Description: Text Data