I noticed that there exists several deprecated and irrelevant flags passed to both binutils and GCC's configuration scripts; hence, I removed them:
Everything related to PPL/CLooG was removed in favor of ISL in newer versions of binutils and GCC due to ISL being much more advanced and having a better open source licensing scheme (even the version checking flags). This means that the flags that were passed to disable version checking for both of them were removed as well.
--disable-gnu-indirect-function is only relevant on systems with glibc (it's always disabled on systems that use any other libc like musl):
https://gcc.gnu.org/install/configure.html
I noticed that there exists several deprecated and irrelevant flags passed to both binutils and GCC's configuration scripts; hence, I removed them:
Everything related to PPL/CLooG was removed in favor of ISL in newer versions of binutils and GCC due to ISL being much more advanced and having a better open source licensing scheme (even the version checking flags). This means that the flags that were passed to disable version checking for both of them were removed as well.
--disable-libmpx
isn't relevant as MPX support was removed from GCC starting from GCC 9: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg01225.html--disable-libmudflap
is also not relevant as the mudflap run time checker was removed starting from GCC 4.9: https://gcc.gnu.org/gcc-4.9/changes.html--disable-gnu-indirect-function
is only relevant on systems with glibc (it's always disabled on systems that use any other libc like musl): https://gcc.gnu.org/install/configure.html--enable-__cxa_atexit
is only available on systems with glibc: https://gcc.gnu.org/install/configure.html--disable-libcilkrts
I couldn't find a good reason to pass this flag to GCC's configure script.