This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gas/gld installation during bootstrap -- how to unpack?
- To: wheeler at ipl dot rpi dot edu (Frederick W. Wheeler)
- Subject: Re: gas/gld installation during bootstrap -- how to unpack?
- From: Joe Buck <jbuck at synopsys dot com>
- Date: Wed, 28 Oct 98 8:30:11 PST
- Cc: egcs at cygnus dot com
> I'd like to have "make bootstrap" build and use gas and gld, but I
> don't understand exactly what is meant by "if they have been properly
> unpacked into the egcs source tree" in the installation instructions I
> have quoted below.
WARNING WARNING: read the last paragraph before trying this.
Let's say that you have a binutils distribution and an egcs distribution
or snapshot.
If you untar them both, you will find that the top-level directories of
both have many files in common: COPYING, COPYING.LIB, configure, etc.
In fact, the top levels of both are substantially identical. The reason
is that both can be thought of as subsets of one big source tree from
which all tools can be built.
So, you could move the directories
bfd binutils gas gprof ld opcodes
from the binutils tree into the egcs tree and they would all build with
the one configure, make bootstrap, make install series of commands.
HOWEVER: you're taking a risk if you do that, since the "official"
versions were built in a tree that contains an older libiberty and other
minor differences. Please don't confuse others by giving them the
resulting binaries and telling them you've given them, say, gas 2.9.1,
since you've given them something that may be slightly different. Also,
since gas and gld don't change every week like snapshots do, you might not
want to keep rebuilding them.