External toolchain support broken for devel/llvm38 but not devel/llvm37
kmacy at freebsd.org
Tue Aug 30 20:30:07 UTC 2016
On Monday, August 29, 2016, Volodymyr Kostyrko <arcade at b1t.name> wrote:
> 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
>> g_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
> 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.
The point of using the external toolchain for me is to bypass building
clang in src. ~31 of the ~47 minutes in buildworld are spent compiling
pieces of llvm/clang. I'd much rather fix the ports than make buildworld
require additional work. For the moment I've disconnected the two pieces
that fail: svn and libc/tests. They don't really belong in base any more
than git and piglit do.
> Sphinx of black quartz judge my vow.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current