External toolchain support broken for devel/llvm38 but not devel/llvm37

Brooks Davis brooks at freebsd.org
Tue Aug 30 21:08:48 UTC 2016

On Mon, Aug 29, 2016 at 08:12:08PM -0700, Matthew Macy wrote:
> It looks like there is something broken with the devel/llvm38 port or external toolchain support has regressed:
> This works:
> make  XCC=/usr/local/bin/clang37 XCXX=/usr/local/bin/clang++37 XCPP=/usr/local/bin/clang-cpp37  buildworld -j12 -s
> This fails:
>  make  XCC=/usr/local/bin/clang38 XCXX=/usr/local/bin/clang++38 XCPP=/usr/local/bin/clang-cpp38 buildworld -j12 -s
> with:
> /home/mmacy/devel/build/mnt/storage/mmacy/devel/drm-next-merge/tmp/usr/bin/ld: /usr/local/llvm38/bin/../lib/clang/3.8.1/lib/freebsd/libclang_rt.ubsan_standalone-x86_64.a: No such file: No such file or directory
> clang-3.8: error: linker command failed with exit code 1 (use -v to see invocation)

I've fixed the install problem.  I'm rather confused about why clang
would try to link with sanitizer libraries when building source.  That's
certainly not default behavior.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20160830/0202a1a2/attachment.sig>

More information about the freebsd-current mailing list