https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236900
Mark Millard <marklmi26-f...@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marklmi26-f...@yahoo.com
--- Comment #4 from Mark Millard <marklmi26-f...@yahoo.com> ---
(In reply to Andreas Tobler from comment #3)
Looks like (system) clang rejects the option:
# cc -v -print-multi-os-directory
cc: error: unsupported option '-print-multi-os-directory'
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM
8.0.0)
Target: x86_64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin
# c++ -v -print-multi-os-directory
c++: error: unsupported option '-print-multi-os-directory'
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM
8.0.0)
Target: powerpc64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin
So it appears that a successful build would have had to use the option with
some gcc version instead of (system) clang.
So the question translates to: what contextual difference leads to use with
clang some times vs. gcc other times? Lack of a full bootstrap vs. using
a full bootstrap?
(Note: the powerpc64 context above is based on WITHOUT_LIB32= because of
my llvm-libunwind patch testing.)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
