I doubt the following configure options were optimal, as I'd simuply cut/hasted from another machine. However, what I find odd is that the configure script determined says "

checking how to compare bootstrapped objects... cmp $$f1 $$f2 16 16
checking for correct version of gmp.h... yes
checking for correct version of mpfr.h... buggy but acceptable


Given the configure script has determined that mpfr.h is buggy, it should at least 

1) Exit, with an error
2) Print a message such as "This will not be used, mpfr.h from gcc will be used instead'

Simply to report something is buggy and unaccesptable, then continue as nothing had happened seems unwise. 

 ../gcc-4.4.0/configure --without-gnu-as --with-as=/usr/ccs/bin/as --without-gnu-ld --with-ld=/usr/ccs/bin/ld --with-gmp=/home/kirkby/dependencies/ --with-mpfr=/home/kirkby/dependencies/ --enable-languages=c,c++,fortran --prefix=/home/kirkby/gcc-4.4.0-Sun-Tools/ --with-pkgversion=Built-un-kestrel


The veriosn of gcc used to build attempt to build gcc 4.4.0 was an earlier one. The configur options to that are:

Target: sparc-sun-solaris2.10
Configured with: ../gcc-4.3.2/configure --prefix=/home/mabshoff/sparc-solaris-toolchain/ --enable-languages=c,c++,fortran --with-gnu-ld --with-ld=/home/mabshoff/sparc-solaris-toolchain/bin/ld --with-gnu-as --with-as=/home/mabshoff/sparc-solaris-toolchain/bin/as --with-gmp=/usr/local/gmp-4.2.3/sparc-SunOS-gcc-4.3.1-abi32/ --with-mpfr=/usr/local/mpfr-2.3.2/sparc-SunOS-gmp-4.2.3-gcc-4.3.1-abi32/
Thread model: posix
gcc version 4.3.2 (GCC)


But basically, it seems irrelavant what options are compiler are used. If gcc determines something is unacceptable, it should not continue, and produce a makefile that at least starts compiling. I did not see if it actually ever built gcc - that would have been a bit stupid given the error message.