From mboxrd@z Thu Jan  1 00:00:00 1970
From: jcn_deja@my-deja.com
To: help-gcc@gnu.org
Subject: Building on hpux.10.20 getting signal 11
Date: Fri, 01 Oct 1999 00:00:00 -0000
Message-ID: <7sg2n0$58u$1@nnrp1.deja.com>
X-SW-Source: 1999-q3/msg00787.html
Message-ID: <19991001000000.gA1qGTTlsbAvxXzBcgFHFZcbs_6dU1qqKvei5O2vAvM@z>

Hello,
     I've been trying to build the gcc-2.95.1 package on my HPux 10.20
system and having no luck at all.  I've tried the following:

1) Using the bunded cc compiler. This fails really bad.  It is a K&R
compiler, but all the system includes are ANSI-C.  I don't have HP's
ANSI-C compiler product.

2) Downloaded a pre-compiled binary from hpux.cs.utah.edu and have tried
it.  I got both gcc-2.8.1 and binutils-2.9.1.  When using those to build
gcc-2.95.1 I consistently receive a signal 11 error from cc1obj.

3) I've combined mixes of using the precompiled 2.8.1 compiler to build
a "c only gcc-2.95.1" package, used that to build and install a fresh
copy of binutils, and then use the new binutils and the c only compiler
to build the full gcc-2.95.1 package.  Get strange results.  If I enable
stabs and enable shared, the stage1/stage2 comparison fails just with
the sbitmap.o file.  If I do not enable stabs or shared I get the
familar signal 11 from cc1obj.

It seems like the there is something wrong with the precompiled 2.8.1
compiler I got.  The README files indicate that they've modified some
header and include files while building it.  So does that mean that I
must *buy* an ANSI-C compiler just to build gcc?  Or does anyone have a
better strategy for building?

               Thanks in advance.


Sent via Deja.com http://www.deja.com/
Before you buy.