* Statically Linked Shared Objects
@ 2004-08-05 18:44 Kevin Lindsay
0 siblings, 0 replies; only message in thread
From: Kevin Lindsay @ 2004-08-05 18:44 UTC (permalink / raw)
To: gcc-help
Hi,
I am creating a statically linked shared object which I want to link to
on different systems. The problem here is that this library is binary
incompatible with the application that will be loading it, thus friendly
segfaults appear. Specifically, glibc 2.3.2 symbols exist in this static
library. I want an application compiled with glibc 2.2.5 to load it
without symbol conflicts.
This is what I have done so far:
libA.so - Statically linked shared object using glibc 2.3.2.
Module.so - Perl C module built with glibc-2.2.5 which links to libA.so.
Perl, which is also using glibc-2.2.5 dynamically loads Module.so, a few
system calls after dlopen() a segfault occurs.
Any help is appreciated, thanks.
Kevin-
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-08-05 18:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-05 18:44 Statically Linked Shared Objects Kevin Lindsay
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).