https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #128 from Sergey Fedorov <vital.had at gmail dot com> --- (In reply to Iain Sandoe from comment #126) > agreed if adding the PATH to the bootstrap compiler enables a whole bunch of > other tool changes - once again we are in the "too many variables" land... The solution that Kirill made for MacPorts (and I use it in my fork too) is safe in this regard, since gcc10-bootstrap lives in an isolated subprefix, /opt/local/libexec/gcc10-bootstrap/bin, and has zero dependencies. So it can be used as the bootstrap compiler for a build outside of ports, without pulling in the whole zoo. But with gcc7 or any other "normal" gcc in MacPorts it will be different: all of them pull in a lot of stuff and binaries are in /opt/local/bin, together with everything else.
