public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: jcn_deja@my-deja.com
To: help-gcc@gnu.org
Subject: Building on hpux.10.20 getting signal 11
Date: Fri, 24 Sep 1999 07:55:00 -0000	[thread overview]
Message-ID: <7sg2n0$58u$1@nnrp1.deja.com> (raw)

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.

WARNING: multiple messages have this Message-ID
From: jcn_deja@my-deja.com
To: help-gcc@gnu.org
Subject: Building on hpux.10.20 getting signal 11
Date: Thu, 30 Sep 1999 23:56:00 -0000	[thread overview]
Message-ID: <7sg2n0$58u$1@nnrp1.deja.com> (raw)
Message-ID: <19990930235600.pxkwXH6T3TWc0O9d5Z8mI2NrpjIqjS98zv4n0fQsTh8@z> (raw)

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.

WARNING: multiple messages have this Message-ID
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	[thread overview]
Message-ID: <7sg2n0$58u$1@nnrp1.deja.com> (raw)
Message-ID: <19991001000000.gA1qGTTlsbAvxXzBcgFHFZcbs_6dU1qqKvei5O2vAvM@z> (raw)

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.

             reply	other threads:[~1999-09-24  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-24  7:55 jcn_deja [this message]
1999-09-30 23:56 ` jcn_deja
1999-10-01  0:00 ` jcn_deja

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='7sg2n0$58u$1@nnrp1.deja.com' \
    --to=jcn_deja@my-deja.com \
    --cc=help-gcc@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).