public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jakub@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: target/6429: libgcc_s problem on dual 32/64-bit arches
Date: Tue, 23 Apr 2002 09:16:00 -0000 [thread overview]
Message-ID: <20020423161205.11470.qmail@sources.redhat.com> (raw)
>Number: 6429
>Category: target
>Synopsis: libgcc_s problem on dual 32/64-bit arches
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Apr 23 09:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: jakub@redhat.com
>Release: gcc 3.1 20020423 (prerelease)
>Organization:
>Environment:
sparc*-*-solaris*, sparc*-*-linux*, s390*-*-*, x86_64-*-*, ...
>Description:
When configuring a compiler for 64/32bit bi-arch target
with 64-bit the default, 64-bit libgcc_s will be
libgcc_s.so.1 and 32-bit libgcc_s e.g. libgcc_s_32.so.1,
when configuring a compiler for 32/64bit bi-arch target
with 32-bit the default, 32-bit libgcc_s will be
libgcc_s.so.1 and 64-bit libgcc_s e.g. libgcc_s_64.so.1.
Which means those 2 compilers are binary incompatible
for C++/Java and everything else requiring shared libgcc.
>How-To-Repeat:
>Fix:
Some mklibgcc.in/Makefile hackery.
The "interesting" part will be taking care of LD_LIBRARY_PATH
for testing purposes.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-23 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 9:16 jakub [this message]
2002-05-05 15:05 davem
2002-10-10 12:18 jakub
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=20020423161205.11470.qmail@sources.redhat.com \
--to=jakub@redhat.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: 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).