I'm trying to build gcc/g++ 4.5.0 with the Graphite optimizations for i686-pc-solaris2.10. I'd like to see whether I'm building all this in the way it should be built, at least at a high level. http://gcc.gnu.org/install/prerequisites.html says I need PPL and CLooG-PPL to get Graphite. http://www.cs.unipr.it/ppl/Download/ftp/releases/LATEST/README.configure says, "Let us take the occasion to stress, once again, the fact that you must use exactly the same C++ compiler to compile the C++ interface of GMP, the PPL and your application, if it uses the C++ interface of the PPL." Since "my application" is gcc-4.5.0 and the three stage bootstrap build of gcc-4.5.0 uses gcc-4.5.0, I'm interpreting this to mean that GMP, PPL and CLooG must also be built with gcc-4.5.0. Here are the high level steps I'm using. 1. Build GCC/G++ 4.5.0 incorporating binutils-20.2, gmp-4.3.2, mpfr-2.4.2 and mpc-0.8.2. Do not include ppl-0.10.2 or CLooG-PPL-0.15.9 yet. 2. Run the test suite. I haven't posted the results, but the summaries are === gcc Summary === # of expected passes 70567 # of unexpected failures 19 # of expected failures 169 # of unsupported tests 687 /tool/gcc/4.5.0/build/gcc/xgcc version 4.5.0 (GCC) === g++ Summary === # of expected passes 22661 # of unexpected failures 1 # of unexpected successes 1 # of expected failures 152 # of unsupported tests 162 /tool/gcc/4.5.0/build/gcc/testsuite/g++/../../g++ version 4.5.0 (GCC) 3. Use gcc/g++ 4.5.0 to compile GMP again. This is necessary to set CPPFLAGS=-fexceptions, to configure it with --enable-cxx and to make sure the GMP libraries are exported where PPL can see them. 4. Use gcc/g++ 4.5.0 and the new "external" version of GMP (i.e. not the one that was included in the original gcc build) to build PPL. 5. Use gcc/g++ 4.5.0 and the new GMP and the new PPL to build CLooG 6. Use gcc/g++ 4.5.0, the new GMP, the new PPL and the new CLooG to rebuild gcc/g++ 4.5.0. This time, remove the symbolic link to gmp since we're supplying an pre-built version of gmp. I'm getting "make check" failures in step 3 and fatal compiler errors in step 4, so I must not be building this in the same way it was built for test purposes. Before I go over the details again, is the general procedure correct? Thanks very much for any help, Dan