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

[Volodymyr Kostyrko]

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 second this - I also faced it. I think this is not a problem with a 
ports but rather with a build as correspondent files can be found in 
/usr/obj under /usr/obj/usr/src/tmp/usr/lib/clang/3.8.0/lib/freebsd/. 
Looks like this files are compiled during build but taken from 
compilers's directory. Linking 'em to the target directory makes build 
succeed.

-- 
Sphinx of black quartz judge my vow.