Merged GCC and Binutils build directories for bootstrap?

Rupert Wood me@rupey.net
Fri Oct 24 11:08:00 GMT 2003


Mario Nigrovic wrote:

> So it seems that, contrary to the howto, the GCC libiberty is not a
> superset of the binutils version, which sort of makes this whole
> merged build kinda a bad idea.  In particular, binutils fails
> because lrealpath is not in gcc's version (even 3.3.2).

It depends on the versions you try and merge. The current libiberty at the
head of GCC's CVS tree is identical to the one at binutil's head of CVS
tree. It's possible that the libiberty was never updated on the
gcc-3_3-branch, i.e. it'd be the same as the libibery in the binutils
version from whenever the gcc-3_3-branch was created.

You could always try and build GCC 3.3.2 with the newer libiberty from the
binutils you're using?

> The point of merging these trees, I thought, was to do a nice clean
> bootstrap.  Otherwise you have to either do the whole compile twice
> (ick!) or build your final gcc with a binutils built with the older
> gcc (or other compiler).

I don't think the combined tree will 'bootstrap' the binutils in the same
way as it does GCC - I think you just get them built once with your current
compiler and it only does the three stages for GCC. I know that cygnus
themselves used to three-stage everything but I don't think this is default
for the combined tree.

Rup.



More information about the Gcc-help mailing list