currently our binutils/gcc cross-compilers install their binaries into /usr/CTARGET/binutils-bin and /usr/CTARGET/gcc-bin ... this is a bit confusing now that we have switched fully to a sysroot system where /usr/CTARGET is our sysroot the more standard method would be to install into /usr/CHOST/CTARGET/binutils-bin and /usr/CHOST/CTARGET/gcc-bin ... this would also keep /usr/CTARGET completely clean of any CHOST files
Jocke pointed out: packages install into /usr/CTARGET/{gcc,binutils}-bin and then the binutils-config script sets up /usr/CTARGET/bin ... all need to move
ok ive updated toolchain-binutils.eclass and released binutils-config-1.9 cross-compiler binutils will no longer touch /usr/CTARGET (and in fact, after reviewing all of this, it was wrong for me to have the stuff install into /usr/CTARGET as the libs from binutils are in *CHOST* format, not *CTARGET*) i'll see about gcc later today
ok gcc was painless because it all filters down :) i'll be releasing binutils-config-1.9-r1 to correct a PATH issue, but otherwise that should be it hopefully ...