https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114105
--- Comment #9 from Mark Millard <markmigm at gmail dot com> --- (In reply to Andrew Pinski from comment #2) > . . . > > >Part of the reason FreeBSD puts effort into making --disable-bootstrap work > This should not be done unless you are building with GCC itself. The reason > is only the C, C++ front-ends are supposed to be able to compile with a > (non-GCC) C++11 compiler. So FreeBSD is doing it wrong anyways. Looks like https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 fixed the issue and enabled non-bootstrapped again. It's comment 12 reported about the official status of such: QUOTE Jonathan Wakely 2024-03-06 13:48:13 UTC (In reply to Dimitry Andric from comment #10) > Note there are other issues with poisoned identifiers, so I'll ask again: is > a non-bootstrapped build even supposed to work, and officially supported, or > not? Yes. > Or more qualified, is a non-bootstrapped build only officially supported > when building on a host with gcc and libstdc++? No. But just because something is officially supported doesn't mean it's a high priority for everybody involved. Some things just take longer to resolve. END QUOTE
