https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82092
--- Comment #8 from Jürgen Reuter <juergen.reuter at desy dot de> --- Another thing I observed: one difference between the laptop where the bootstrap worked and the one where it didn't work (besides the different chipsets i5 vs. i7) is that on the one where the bootstrap doesn't work, the MAC OS X Security Integrity Protocol (SIP) is activated, while on the one where the bootstrap worked it is deactivated. Could it be that during the bootstrap procedure the SIP causes some trouble in that some of the settings of the gcc to be bootstrapped are being blocked?