FW: gcc-3.2

[John David Anglin]

> > > > Since you have shown an interest I am notifying you directly in
> > > > addition to posting to the group.  Just to inform you that I solved
> > > > my problem by making use of the GNU assembler in stead of the HPUX
> > > > standard one. (I fetched the binary version of GNU as from the pages
> > > > of HPUX porting center.)  Configuration options: --with-gnu-as
> > > > --with-as=/opt/binutils/bin/as The doc says it makes a difference to
> > > > make use of GNU as, but in the first place I did not interpret that
> > > > as strictly necesarry.  Lorentz

The GNU assembler is not a requirement but you lose features when
you don't use it (e.g., debugging).

There are basically two approaches to building binutils and gcc from
scratch.  You can build binutils first with the HP bundled compiler
and then build gcc using the --with-gnu-as and --with-as options.
The second approach is to build GCC (probably just the C language)
with the HP bundled compiler, then you can use GCC to build binutils,
then rebuild GCC with binutils.

As noted in the installation documentation, building binutils and/or
GCC with the HP bundled compiler is tested infrequently and problems
often arise when non K&R compatible code is introduced into the compiler.
GCC 3.3 will probably be the last version that will build with a
traditional compiler.

It shouldn't be necessary to obtain a binary distributions to bootstrap
GCC.  When the documented installation procedure doesn't work, we would
very much like to receive reports on the failure.  We don't get very
many as once someone has gcc installed they tend to use it instead of
the HP tools.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)