http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61101
--- Comment #17 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Maxime Boissonneault from comment #5) > Basically, we started with the system GCC. We compiled GCC, GMP, MPFR, > MPC_V, with that system GCC. Then, we uninstalled the system GCC and its > libstdc++ and recompiled those with the GCC we had just compiled. This sounds like a big waste of time. (In reply to Maxime Boissonneault from comment #6) > Here is our complete installation document : > https://docs.google.com/a/calculquebec.ca/document/d/ > 1hcddCXGnm6OgTwRxRDU2akb-AxKx2aursppLp2JPwWo/edit > > It went : > - System GCC compiled GCC 4.8.1 > system GCC was removed. This step might have broken your system. > - GCC 4.8.1 compiled GCC 4.8.2 > - GCC 4.8.2 compiled GCC 4.6.4 > > Each time we bootstrapped, so that in the end, I believe GCC 4.8.2 was > compiled with 4.8.2, etc. (In reply to Maxime Boissonneault from comment #15) > The reason we bootstrap is to remove as many dependencies as possible on the > OS-provided packages. We've been bitten in the past with updates of packages > (even on CentOS6) that broke user's codes. GCC should have almost no dependencies on system libraries, just libc.so (although I note you've used --with-system-zlib, so that adds one dependency) Installing GMP, MPFR and MPC instead of linking statically also adds avoidable dependencies.
