Broken arm support in clang now?

[Dimitry Andric]

On 11 Aug 2018, at 19:31, Warner Losh <imp at bsdimp.com> wrote:
> 
> On Sat, Aug 11, 2018, 10:20 AM Dimitry Andric <dim at freebsd.org> wrote:
> On 11 Aug 2018, at 16:55, Warner Losh <imp at bsdimp.com> wrote:
> >
> > It looks like armv5 clang bogusly uses lld:
> >
> > From a 'make buildkernel' of the RT1310 kernel config:
> >
> > cc -target arm-gnueabi-freebsd12.0
...
> > ld: warning: lld uses extended branch encoding, no object with architecture
> > supporting feature detected.
> > ld: warning: lld may use movt/movw, no object with architecture supporting
> > feature detected.
...
> Host is amd64. Target is arm. No src.conf. Did a full buildworld TARGET=arm a few days ago. /usr/bin/ld is lld.

Okay, so in the above "cc" command, can you somehow figure out which cc
executable it is using? And please add a -v to the "linking kernel.full"
command line, so it shows exactly which linker it runs?

I have the idea that it is preferring your /usr/bin/ld over
${WORLDTMP}/usr/bin/ld...

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-toolchain/attachments/20180811/0416c646/attachment.sig>