When running configure and the path to a cross-compilation toolset is given in --with-dev-kit, then configure sometimes find the compiler in the local path instead of the correct compiler in the dev kit path.

This has been reported by David Holmes on jdk_build_infra_dev_ww_grp@oracle.com (when building ARM hard-float) and I have also found it when building ppc. Configure finds the wrong compiler if it can't find cc in the toolset directory, but if there is a link cc->gcc in the toolset dir, then it finds the correct compiler (for example ARM soft float works fine to build)

A not so good workaround that only fixes the ppc problem has been submitted:
http://hg.openjdk.java.net/build-infra/jdk8/rev/21b7150f5a7d

A better workaround is to create symlinks in the toolset dirs for the missing cc's.