From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30511 invoked by alias); 16 Aug 2002 23:26:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 30497 invoked by uid 71); 16 Aug 2002 23:26:01 -0000 Date: Fri, 16 Aug 2002 16:46:00 -0000 Message-ID: <20020816232601.30492.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Nathan Bryant Subject: Re: middle-end/7617: shared libgcc binary incompatibility on sparc-sun-solaris2.8 Reply-To: Nathan Bryant X-SW-Source: 2002-08/txt/msg00345.txt.bz2 List-Id: The following reply was made to PR middle-end/7617; it has been noted by GNATS. From: Nathan Bryant To: nbryant@allegientsystems.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Cc: Subject: Re: middle-end/7617: shared libgcc binary incompatibility on sparc-sun-solaris2.8 Date: Fri, 16 Aug 2002 19:16:44 -0400 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7617 I have some more info on this PR; it's not just a binary incompatibility with libgcc_s.so; shared libgcc seems to be broken entirely, since I am unable to build very simple C shared libraries that don't segfault, with gcc 3.2+binutils 2.13 with gcc 3.2 configured as described in the PR. Sorry for the misleading PR. It seems that the only thing needed to reproduce the problem is gcc3.2 itself (and perhaps this specific binutils.) At the moment, unfortunately, I am unable to get anything useful out of gdb since gdb is one of my binaries that got broken; the gdb binary i've moved from another system has problems and seems unable to connect to the child process.