Re: gas/gld installation during bootstrap -- how to unpack?

Re: gas/gld installation during bootstrap -- how to unpack?

[Frederick W. Wheeler]

EGCS list,

I think my last question was too brief.  Here is a bit more
explanation of what I mean: 

To have "make bootstrap" build and use gas and gld, should the
binutils-2.9.1 top-level source directory be in the egcs-1.1a
directory or should certain sub-directories and files from
binutils-2.9.1 be placed in egcs-1.1a?

Thanks again for your time,
Fred Wheeler
wheeler@ipl.rpi.edu

I wrote:
> EGCS list,
> 
> 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.
> 
> Thank you,
> Fred Wheeler
> 
> From: http://egcs.cygnus.com/install/build.html
> > For a native build issue the command "make bootstrap". This will build
> > the entire egcs compiler system, which includes the following steps:
> > 
> >     Build host tools necessary to build the compiler such as texinfo,
> >     bison, gperf.
> > 
> >     Build target tools for use by the compiler such as gas, gld, and
> >     binutils if they have been properly unpacked into the egcs source
> >     tree.
> > 
> >     Perform a 3-stage bootstrap of the compiler.
> > 
> >     Perform a comparison test of the stage2 and stage3 compilers.
> > 
> >     Build runtime libraries using the stage3 compiler from the
> >     previous step.

Re: gas/gld installation during bootstrap -- how to unpack?

[Alexandre Oliva]

Frederick W Wheeler <wheeler@ipl.rpi.edu> writes:

> To have "make bootstrap" build and use gas and gld, should the
> binutils-2.9.1 top-level source directory be in the egcs-1.1a
> directory or should certain sub-directories and files from
> binutils-2.9.1 be placed in egcs-1.1a?

From a quick look at the top-level Makefile, it seems to me that
binutils-2.9.1 should be moved into egcs/binutils (no version number)

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:oliva@gnu.org mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil

Re: gas/gld installation during bootstrap -- how to unpack?

[Joe Buck]

> 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.

gas/gld installation during bootstrap -- how to unpack?

[Frederick W. Wheeler]

EGCS list,

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.

Thank you,
Fred Wheeler
wheeler@ipl.rpi.edu

From: http://egcs.cygnus.com/install/build.html
> For a native build issue the command "make bootstrap". This will build
> the entire egcs compiler system, which includes the following steps:
> 
>     Build host tools necessary to build the compiler such as texinfo,
>     bison, gperf.
> 
>     Build target tools for use by the compiler such as gas, gld, and
>     binutils if they have been properly unpacked into the egcs source
>     tree.
> 
>     Perform a 3-stage bootstrap of the compiler.
> 
>     Perform a comparison test of the stage2 and stage3 compilers.
> 
>     Build runtime libraries using the stage3 compiler from the
>     previous step.