if you're cross-building (i.e. the build CHOST you're running catalyst on is diff from the CHOST used in the stage files), then the gcc-config/binutils-config will think they're setting up cross-compilers instead of native-compilers this is mostly a limitation in portage (portageq doesnt respect ROOT when gathering envvar's), but it can be workedaround quite easily in catalyst ... just run with CHOST=${clst_CHOST} like ROOT now
Created attachment 75853 [details, diff] catalyst-gcc-binutils-config-CHOST.patch
Added to CVS
Fixed in 2.0_rc13