This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
target/6429: libgcc_s problem on dual 32/64-bit arches
- From: jakub at redhat dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: 23 Apr 2002 16:12:05 -0000
- Subject: target/6429: libgcc_s problem on dual 32/64-bit arches
- Reply-to: jakub at redhat dot com
>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: