Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx> writes: > steffen@host:/usr/local/build/gcc # find gcc-4.6.0 -type l -maxdepth > 1|xargs ls -l > lrwxrwxrwx 1 steffen develop [...] gcc-4.6.0/binutils -> binutils-2.21 > lrwxrwxrwx 1 steffen develop [...] gcc-4.6.0/gmp -> gmp-4.3.2/ > lrwxrwxrwx 1 steffen develop [...] gcc-4.6.0/mpc -> mpc-0.8.1/ > lrwxrwxrwx 1 steffen develop [...] gcc-4.6.0/mpfr -> mpfr-2.4.2/ You have to put all the top-level binutils directories in the gcc source tree. That is, you shouldn't see just a binutils directory there; you should see bfd, opcodes, gas, ld, binutils, etc. This does not work reliably when mixing releases, because directories like include and libiberty are shared between gcc and binutils. It only works reliably when working with the development sources. Ian
