From: Shawn Starr <shawn.starr@datawire.net>
To: GCC Help <gcc-help@gcc.gnu.org>
Subject: Re: SCO OpenServer 5 (3.2v5.0.4) G++ 2.95.3 borks
Date: Tue, 18 Jun 2002 12:58:00 -0000 [thread overview]
Message-ID: <1024430357.31646.23.camel@unaropia> (raw)
In-Reply-To: <1024430324.31638.21.camel@unaropia>
We're not using gcc 3.1.0 just yet and still need 2.95.3 for legacy.
On Tue, 2002-06-18 at 15:58, Shawn Starr wrote:
> gcc 2.95.3 (g++ build) fails on SCO. Any solutions on how to fix this?
>
>
> Fault below:
>
> -O2 -g -O2 -I./include -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
> -g -O2 -I. -I../../gcc-2.95.3/gcc -I../../gcc-2.95.3/gcc/config
> -I../../gcc-2.95.3/gcc/../include \
> -c -fexceptions ../../gcc-2.95.3/gcc/cp/exception.cc
> xgcc: Internal compiler error: program as got fatal signal 11
> make[5]: *** [exception.o] Error 1
> make[5]: Leaving directory `/root/gcc-build/gcc'
>
> --
> Shawn Starr
> Development Support Engineer, Operations
> Datawire Communication Networks Inc.
> 10 Carlson Court, Suite 300
> Toronto, ON, M9W 6L2
> T: 416-213-2001 ext 179 F: 416-213-2008
--
Shawn Starr
Development Support Engineer, Operations
Datawire Communication Networks Inc.
10 Carlson Court, Suite 300
Toronto, ON, M9W 6L2
T: 416-213-2001 ext 179 F: 416-213-2008
prev parent reply other threads:[~2002-06-18 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 12:57 Shawn Starr
2002-06-18 12:58 ` Shawn Starr [this message]
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=1024430357.31646.23.camel@unaropia \
--to=shawn.starr@datawire.net \
--cc=gcc-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).