gcc: don't bootstrap if the version is bigger than min required about repo HOT 3 CLOSED

I guess the only reason you might want to do this bootstrap is if there is a compiler bug that propagates from the old version to the new, but in practice this can happen even when going from minor version to minor, so then it's just pointless. That whole check might as well be commented out.

from repo.

The best solution might be to add a prompt to ask if the user wants the bootstrap, set using KISS_PROMPT. Thing is if the user avoids bootstrap, updates gcc, then uses that gcc to compile same gcc, statistically it's very unlikely for a bug to double propagate, but even then you are looking at compiling for 8 minutes VS 18 minutes.

from repo.

I've fixed the version check with 631bb4b, so that bootstrapping is only enabled for major version changes.

Given the infrequency of major version changes and the importance of such a sanity check for a source-based distribution, I'd like to keep this check non-optional -- you can of course still fork the package if you insist.

from repo.