Hi, thanks for your quick reply. On Wed, Apr 27, 2011 at 1:58 AM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > 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. ohh, I see... The documentation does not mentiones this so clearly. > This does not work reliably when mixing releases, because > directories like include and libiberty are shared between gcc > and binutils. Yes, their contents differs; in my case, binutils/include seem to have more files, so I'm afraid my build attempt will break (in a few hours when reaching the point)... Which include / intl / libiberty I should use, from gcc or bintuils? Isn't there some documentation anywhere? Is my assumption, that a "combined build" is most easy, a wrong one and should I try a non-combined build? Are there some docs about? For the documentation, especially extraction of bintuils, would it be a good idea to submit a bug report about the too brief installation instructions? > It only works reliably when working with the development > sources. But there is a way to build a recent released gcc toolchain, isn't there? Sorry for my silly questions, but I tried to follow avaialable documentation and information from the web... Anyone is building gcc-4.6.0, why am I unable, what do I wrong... oki, Steffen
