Date: Sun, 31 Mar 2019 19:52:53 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 236900] lang/gcc8: BOOTSTRAP=off fails to build after r497254 Message-ID: <bug-236900-29464-yNapScBhlo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236900-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-236900-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236900 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #4 from Mark Millard <marklmi26-fbsd@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=3D because of my llvm-libunwind patch testing.) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236900-29464-yNapScBhlo>