USE_LLD=No is confusing on aarch64. The setting creates a wrapper
script ${WRKDIR}/bin/ld that execs /usr/bin/ld.bfd... which does
not exist on aarch64, resulting in build errors like
configure: error: C compiler cannot create executables
See `config.log' for more details
I'm uncertain what to d
On Sun, May 26 2019, Christian Weisgerber wrote:
> USE_LLD=No is confusing on aarch64. The setting creates a wrapper
> script ${WRKDIR}/bin/ld that execs /usr/bin/ld.bfd... which does
> not exist on aarch64, resulting in build errors like
>
> configure: error: C compiler cannot create executables
Jeremie Courreges-Anglas:
> So far we only need this for one arch, maybe a cheaper approach would be
> enough? The diff below just tests whether ld.bfd exists.
On archs other than LLD_ARCHS, that diff would stat() ld.bfd every
time bsd.port.mk is parsed.
Let's do this only when USE_LLD switches
On Tue, May 28 2019, Christian Weisgerber wrote:
> Jeremie Courreges-Anglas:
>
>> So far we only need this for one arch, maybe a cheaper approach would be
>> enough? The diff below just tests whether ld.bfd exists.
>
> On archs other than LLD_ARCHS, that diff would stat() ld.bfd every
> time bsd.
