This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Unclear documentation on building GCC together with binutils
- From: "Ulf Magnusson" <ulfalizer at gmail dot com>
- To: gcc-help at gcc dot gnu dot org
- Date: Wed, 29 Nov 2006 07:10:47 +0100
- Subject: Unclear documentation on building GCC together with binutils
The following paragraph in the GCC installation guide
(http://gcc.gnu.org/install/) seems a bit unclear to me:
"If you also intend to build binutils (either to upgrade an existing
installation or for use in place of the corresponding tools of your
OS), unpack the binutils distribution either in the same directory or
a separate one. In the latter case, add symbolic links to any
components of the binutils you intend to build alongside the compiler
(bfd, binutils, gas, gprof, ld, opcodes, ...) to the directory
containing the GCC sources."
What exactly is meant by "the same directory"? Say the GCC tarball is
unpacked in the directory foo, yielding foo/gcc-3.x.x. Should binutils
be unpacked in the same directory, so that you get
foo/gcc-3.x.x
foo/binutils-x.x
, or in the gcc-3.x.x directory, so that you get
foo/gcc-3.x.x/binutils-x.x
, or into the gcc-3.x.x directory with one directory level stripped
(e.g. with --strip-components 1 passed to tar), essentially "merging"
the two packages in foo/gcc-3.x.x? Whatever turns out to be The Right
Way, the doc really needs to be updated for clarity.
Why would you want to build gcc and binutils together in this way by
the way? Isn't it possible to install them separately?
/Ulf Magnusson