[The problem during buildworld via aarch64-xtoolchain-gcc still occurs
for -r322287 of head and -r447082 of /usr/ports. It is because of using
the default static-link of devel/aarch64-binutils utilities, including
/usr/local/bin/aarch64-freebsd-ld . A non-default devel/aarch64-binutils
is required.
Attempting buildworld with devel/aarch64-xtoolchain-gcc
and devel/aarch64-binutils I got:
/usr/src/crypto/openssl/crypto/arm64cpuid.S: Assembler messages:
/usr/src/crypto/openssl/crypto/arm64cpuid.S:23: Error: selected processor does
not support `aese v0.16b,v0.16b'
/usr/src/crypto/openssl/crypto
[A top post about the failing R_PPC_PLTREL24 since
the material does not flow well as a sequential
read from prior material. I found that the .kld
does not match the contributing .o for GLOBAL
status for routines and the LOCAL in the .kld is
rejected by ld in ppc_elf_check_relocs.]
There is someth
[clang 5 generates R_PPC_PLTREL24 in the .o files
for global symbols in places gcc 4.2.1 generates
R_PPC_ADDR16_HA / R_PPC_ADDR16_LO pairs.]
On 2017-Aug-10, at 7:22 PM, Mark Millard wrote:
> [A top post about the failing R_PPC_PLTREL24 since
> the material does not flow well as a sequential
> re
