* -static-libgcc and static libstdc++.a,
@ 2011-01-16 14:21 Bob Rossi
2011-01-18 6:38 ` Ian Lance Taylor
0 siblings, 1 reply; 2+ messages in thread
From: Bob Rossi @ 2011-01-16 14:21 UTC (permalink / raw)
To: gcc-help
Hi,
I separated this question out, to keep things simple.
Does it make sense to link in libstdc++.a and leave libgcc
shared? The goal is maximum portability between different linux
environments.
I'm hoping this will keep the c++ shared library symbols private,
but allow the exception handling to work on the system the software
is run on.
Thanks,
Bob
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: -static-libgcc and static libstdc++.a,
2011-01-16 14:21 -static-libgcc and static libstdc++.a, Bob Rossi
@ 2011-01-18 6:38 ` Ian Lance Taylor
0 siblings, 0 replies; 2+ messages in thread
From: Ian Lance Taylor @ 2011-01-18 6:38 UTC (permalink / raw)
To: Bob Rossi; +Cc: gcc-help
Bob Rossi <bob@brasko.net> writes:
> Does it make sense to link in libstdc++.a and leave libgcc
> shared? The goal is maximum portability between different linux
> environments.
It makes sense if you do not plan to dlopen any shared libraries which
themselves depend on libstdc++.so.
> I'm hoping this will keep the c++ shared library symbols private,
> but allow the exception handling to work on the system the software
> is run on.
That by itself won't necessarily keep the C++ shared library symbols
private. To ensure that they are private you would need to use a
version script a link time.
Ian
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-01-18 6:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-16 14:21 -static-libgcc and static libstdc++.a, Bob Rossi
2011-01-18 6:38 ` Ian Lance Taylor
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).