[Bug 223551] for external toolchain support, X prefix is not setting build utils for make buildworld

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223551

--- Comment #7 from Mark Millard <markmi at dsl-only.net> ---
(In reply to sid from comment #0)

I used -v to check include paths searched for
devel/llvm50 :

#include <...> search starts here:
 /usr/include/c++/v1
 /usr/local/llvm50/lib/clang/5.0.0/include
 /usr/include

As I would expect for devel/* it looks like
teh devel/llvm* 's were adjusted to use the
system include files by default.

(If there was a lang/llvm50 then it likely would
not have such an adjustment, just like lang/gcc7
does not look there by default.)

So it appears that the following paragraph does
not apply to your context:

As I remember I had to do things to force
the system include files and libraries to
be used for what I used as the substitute
for the "host system compiler/toolchain".
The files from the compiler's own environment
were not appropriate/sufficient.


I will note that currently lld from devel/llvm* 's
are broken on zfs from the fallocate change (ZFS
does not actually support it but lld tries to
use it without detecting the problem). The
devel/llvm* 's need to be updated so that they
build usable lld 's even for use in a zfs
context.

What lld does on zfs after a given version is:

 "/usr/local/llvm50/bin/ld" --eh-frame-hdr -dynamic-linker /libexec/ld-elf.so.1
--hash-style=both --enable-new-dtags -o a.out /usr/lib/crt1.o /usr/lib/crti.o
/usr/lib/crtbegin.o -L/usr/lib /tmp/exception_test-baadc9.o -lc++ -lm -lgcc
--as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed
/usr/lib/crtend.o /usr/lib/crtn.o
/usr/local/llvm50/bin/ld: error: cannot open output file a.out: Invalid
argument
clang-5.0: error: linker command failed with exit code 1 (use -v to see
invocation)

At soem point this will apply to 11.x instead of
just 12.0. (I've not been tracking 11.x and so
do not know the status of zfs and fallocate there.)

-- 
You are receiving this mail because:
You are the assignee for the bug.