* multilibs produce incompatible libgcc_s
@ 2002-04-18 2:20 Andreas Jaeger
2002-04-18 2:50 ` Jakub Jelinek
0 siblings, 1 reply; 2+ messages in thread
From: Andreas Jaeger @ 2002-04-18 2:20 UTC (permalink / raw)
To: gcc
If I use multilibs on sparc or x86-64, the shared 32-bit libgcc_s will
be called libgcc_s_32.so instead of libgcc_s.so when multilibs aren't
used or when a native 32-bit build is done.
This looks broken since it causes an incompatibility to a non-multilib
install.
What's the right way to fix this?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: multilibs produce incompatible libgcc_s
2002-04-18 2:20 multilibs produce incompatible libgcc_s Andreas Jaeger
@ 2002-04-18 2:50 ` Jakub Jelinek
0 siblings, 0 replies; 2+ messages in thread
From: Jakub Jelinek @ 2002-04-18 2:50 UTC (permalink / raw)
To: Andreas Jaeger; +Cc: gcc
On Thu, Apr 18, 2002 at 11:19:05AM +0200, Andreas Jaeger wrote:
>
> If I use multilibs on sparc or x86-64, the shared 32-bit libgcc_s will
> be called libgcc_s_32.so instead of libgcc_s.so when multilibs aren't
> used or when a native 32-bit build is done.
>
> This looks broken since it causes an incompatibility to a non-multilib
> install.
>
> What's the right way to fix this?
Its on my TODO list. Some Makefile/mklibgcc/etc. magic is needed.
Jakub
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-04-18 9:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-18 2:20 multilibs produce incompatible libgcc_s Andreas Jaeger
2002-04-18 2:50 ` Jakub Jelinek
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).