http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58260
--- Comment #7 from Mikael Pettersson <mikpe at it dot uu.se> --- (In reply to Jonathan Wakely from comment #6) > (In reply to Mikael Pettersson from comment #4) > > (I always build gmp/mpfr/mpc with --disable-shared exactly to avoid such > > issues.) > > Why not just build them in tree and avoid all problems? Because 1. building those libraries with --disable-shared and pointing gcc's configure to them (--with-gmp= etc) is trivial and also avoids the problems, 2. I build gcc a lot (several branches x several architectures), I really don't want to waste time and electricity rebuilding those libraries again and again, 3. I want precise control over which versions of those libraries I'm testing, 4. as a matter of principle I think pre-requisites should be strictly external to the gcc build process, otherwise were do we stop? should we download and build make, bash, coreutils, gdb, expect, glibc, ... just because the build needs them? special-casing gmp/mpfr/mpc is completely unnecessary
