Date: Tue, 27 Mar 2018 18:21:16 -0400 From: Ed Maste <emaste@freebsd.org> To: Antoine Brodin <antoine@freebsd.org> Cc: "freebsd-toolchain@FreeBSD.org" <freebsd-toolchain@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Heads-up: linker (lld) changes for amd64 coming soon Message-ID: <CAPyFy2D24Qq8gzDYbcz4EXBCBG0MEEd9S7-vYQ0y=y-zRkhjew@mail.gmail.com> In-Reply-To: <CAPyFy2ActcryGsok%2BLiYbG6%2BP_jTaE8L%2BqAh4ZpoVYu%2Bip_O1A@mail.gmail.com> References: <CAPyFy2AjEJjryjgGCHAo107mkOUnFbKmkcMVFWQEKKbTEuu8AA@mail.gmail.com> <CAALwa8kfdg31-Vt=v78ZHV1Us9_%2BN01PC7cwiKFe81720Hguhw@mail.gmail.com> <CAPyFy2ActcryGsok%2BLiYbG6%2BP_jTaE8L%2BqAh4ZpoVYu%2Bip_O1A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
(Moved from -current to -ports) On 27 March 2018 at 13:15, Ed Maste <emaste@freebsd.org> wrote: > > Fair enough - this was the reason I sent the email. I've now gone > through and submitted a PR for for each failure that did not already > have one. I've also added LLD_UNSAFE to a few ports where where it was > straightforward. Via tobik's commit to lang/myrddin (r465725) I discovered BINARY_ALIAS=ld=ld.bfd, which is a usable workaround for some ports which don't honour $LD or -fuse-ld=bfd in CFLAGS. As you point out in reply to my r465755 BINARY_ALIAS alone is not sufficient, because arm64 does not provide ld.bfd by default and LLD_UNSAFE automatically brings in ports binutils if /usr/bin/ld.bfd does not exist. So we need both LLD_UNSAFE and BINARY_ALIAS. Should we just have LLD_UNSAFE also set BINARY_ALIAS=ld=ld.bfd?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2D24Qq8gzDYbcz4EXBCBG0MEEd9S7-vYQ0y=y-zRkhjew>