Date: Thu, 13 Dec 2012 13:20:11 +0000 From: David Chisnall <theraven@FreeBSD.org> To: Erik Cederstrand <erik@cederstrand.dk> Cc: "toolchain@freebsd.org" <toolchain@FreeBSD.org>, Pete chou <pete.chou@gmail.com> Subject: Re: Using non-standard linker Message-ID: <99D2C6D2-4C56-4724-875D-31FF41CFA2A4@FreeBSD.org> In-Reply-To: <5337BAB6-7EEE-4A1E-9660-902544CCE3EE@cederstrand.dk> References: <089FCDB5-C0D2-4675-AB71-FD7089BFA031@cederstrand.dk> <5880F938-A9EC-4B2D-8079-42504DFA87F9@FreeBSD.org> <5337BAB6-7EEE-4A1E-9660-902544CCE3EE@cederstrand.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Dec 2012, at 13:18, Erik Cederstrand wrote: >> The easiest way of doing this is to make /usr/bin/ld (in the host = system and in the bootstrap) into a symbolic link that points to = whatever the selected linker is. I had to do this when testing gold as = well (we end up with ld-gold and ld-bfd and ld being a symlink to one of = them). >=20 > Yes, a symlink is of course an easy solution post-install. But 'ld' is = built as part of 'make toolchain', I believe, so this approach wouldn't = work if I wanted mclinker to be used as the linker in 'make buildworld'. = The newly built 'ld' in /usr/obj/ would be used as the linker instead. That's why I said 'and in the bootstrap'. You'd also need to ensure = that the bootstrap build of clang and binutils set up the symlink. = Purely for testing, I think you can do this manually by doing the = bootstrap and then the buildworld as separate make invocations. David=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99D2C6D2-4C56-4724-875D-31FF41CFA2A4>