public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Bob Harris <rmharrisva@netscape.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8350: segmentation fault when using -shared-libgcc on Solaris2.9
Date: Tue, 29 Apr 2003 17:36:00 -0000 [thread overview]
Message-ID: <20030429173601.2138.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/8350; it has been noted by GNATS.
From: Bob Harris <rmharrisva@netscape.net>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
gcc-prs@gcc.gnu.org, boulier@lifl.fr
Cc:
Subject: Re: c/8350: segmentation fault when using -shared-libgcc on Solaris2.9
Date: Tue, 29 Apr 2003 13:28:38 -0400
I would like to add that I am seeing this exact same problem with GCC
3.1 on
Solaris 8 (64bit mode) on a Sun Blade 100.
ksh [gadalka] - / -> uname -a && gcc -v
SunOS gadalka 5.8 Generic_108528-20 sun4u sparc SUNW,Sun-Blade-100
Reading specs from /opt/gcc/lib/gcc-lib/sparcv9-sun-solaris2.8/3.1/specs
Configured with: ./configure --prefix=/opt/gcc
-host=sparcv9-sun-solaris2.8 --enable-threads=solaris --disable-nls
Thread model: solaris
gcc version 3.1
ksh [gadalka] - / ->
Static libs are okay. But every shared lib I have tried to build always
seg faults.
This includes shared libs (.so) that GCC 3.1 builds as part of an
appplication.
Is there going to be a fix any time soon? This is a most annoying problem.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8350
=============================================================================
Bob Harris Email: rharris@sprint.net
Systems Programmer III Fax: (703) 478-5471
Sprint / IP Services
DNS and News (USENET) Team
//QUOTE EXEC PGM=IEBGENER
//SYSIN DD *
The power of accurate observation is commonly called cynicism
by those who have not got it.
- Sir George Bernard Shaw
/*
//
next reply other threads:[~2003-04-29 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 17:36 Bob Harris [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 7:07 davem
2002-10-25 6:46 boulier
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=20030429173601.2138.qmail@sources.redhat.com \
--to=rmharrisva@netscape.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).