public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/7617: shared libgcc binary incompatibility on sparc-sun-solaris2.8
Date: Fri, 11 Oct 2002 21:06:00 -0000 [thread overview]
Message-ID: <20021012040601.16892.qmail@sources.redhat.com> (raw)
The following reply was made to PR middle-end/7617; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@mvista.com>
To: morey@astech.org
Cc: nbryant@allegientsystems.com, gcc-gnats@gcc.gnu.org,
gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: middle-end/7617: shared libgcc binary incompatibility on sparc-sun-solaris2.8
Date: Sat, 12 Oct 2002 00:02:57 -0400
On Fri, Oct 11, 2002 at 08:10:43PM +0700, morey@astech.org wrote:
> I have been experiencing the same problems. I have been using binutils-2.13. After extensive playing around I have noticed
>
> a few things. If you compile a simple program that is dynamically linked with libgcc_s.so it will crash in __init with a
>
> SIGSEV. However, if it is compiled with -static the program will run fine. I then rebuilt gcc and had it use the solaris ld
>
> and as and how a program the dynamically linked with libgcc_s.so will run fine. It appears to be a problem related to binutils-2.13.
>
> I will try an older version and see if I can track down what exactly is causing the problem.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7617
Get a binutils CVS head snapshot. This is recently fixed and we'll be
releasing a fixed 2.13.1 in a couple of weeks hopefully.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-10-12 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 21:06 Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 9:39 ehrhardt
2002-10-11 19:16 morey
2002-09-26 3:40 davem
2002-08-16 16:46 Nathan Bryant
2002-08-16 14:56 nbryant
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=20021012040601.16892.qmail@sources.redhat.com \
--to=drow@mvista.com \
--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).