Sunday, May 26, 2019

USE_LLD=No vs. aarch64?

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 do about this. Add yet another variable
no_lld_on_this_arch to arch-defines.mk and set IGNORE when handling
USE_LLD?

Currently, aarch64 is the only architecture where ld.bfd does not
exist.

--
Christian "naddy" Weisgerber naddy@mips.inka.de

No comments:

Post a Comment