public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nbryant@allegientsystems.com To: gcc-gnats@gcc.gnu.org Subject: middle-end/7617: shared libgcc binary incompatibility on sparc-sun-solaris2.8 Date: Fri, 16 Aug 2002 14:56:00 -0000 [thread overview] Message-ID: <20020816214606.28153.qmail@sources.redhat.com> (raw) >Number: 7617 >Category: middle-end >Synopsis: shared libgcc binary incompatibility on sparc-sun-solaris2.8 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Aug 16 14:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: nbryant@allegientsystems.com >Release: gcc-3.2 >Organization: >Environment: sparc solaris-2.8 >Description: Recently I upgraded a sparc-sun-solaris2.8 box to gcc 3.2 and binutils 2.13 and now my binaries compiled with gcc 3.0.4 seem to have stopped working. as best as i can remember, my upgrade path went something like this: * original installation of GNU toolchain with gcc 3.0.4 from sunfreeware * installed binutils, probably 2.11.something * at this point i think i recompiled gcc 3.0.4 with itself to get a working java version using binutils. most of my binaries and libraries in /usr/local were then compiled with this toolchain. * upgraded to binutils 2.12.1 and gcc 3.1, both built from source. I didn't build too many binaries with this toolchain, but I believe all my old binaries still worked at this point. * built and installed binutils 2.13 from source. no special configure options. * built and installed gcc-3.2 from source, configured as follows: nbryant@sundev:~/src$ gcc -v Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.2/specs Configured with: /export/home/nbryant/src/gcc-3.2/configure --with-gnu-as --with-gnu-ld --enable-threads --with-as=/usr/local/bin/as --with-ld=/usr/local/bin/ld --enable-libgcj --with-system-zlib --with-cpu=ultrasparc Thread model: posix gcc version 3.2 At this point, I noticed that any of my old binaries linked with libgcc_s no longer work; they dump core immediately on startup. This means that anything linked with a C shared library built with the older gcc can't work. I believe my gcc 3.0.4 was configured identically, but without --with-cpu=ultrasparc and without --with-system-zlib, probably. in all cases, binutils was built without options. Can somebody please tell me what version of these tools I should be using to ensure C ABI compatibility going forward? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-16 21:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-16 14:56 nbryant [this message] 2002-08-16 16:46 Nathan Bryant 2002-09-26 3:40 davem 2002-10-11 19:16 morey 2002-10-11 21:06 Daniel Jacobowitz 2002-12-11 9:39 ehrhardt
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=20020816214606.28153.qmail@sources.redhat.com \ --to=nbryant@allegientsystems.com \ --cc=gcc-gnats@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: linkBe 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).