Re: dlopen() sees some symbols, but not others
- From: "Gary R. Hook" <noway@xxxxxxxxxxxxxx>
- Date: Thu, 28 Dec 2006 20:35:44 GMT
Rob Y wrote:
Do you know of a way to bypass this symbol garbage collection? If
not, I can just change my dummy 'dllstub.c' module to make calls to all
the functions I want to force to be available, and I guess that'll
force them to be pulled in and exported via -bexpall.
Better to build an explicit export list (which can be used along
with -bexpall).
By the way, is garbage collection only done for modules pulled in by
the linker from a library? If the .o's are explicitly fed to the
linker, are all functions in the .o's kept even if they're not
referenced by the app?
When you use -brtl and .bexpall any named .o files should be fully, retained, as the symbols in all of the .o files should end up
exported.
.
- Follow-Ups:
- Re: dlopen() sees some symbols, but not others
- From: Rob Y
- Re: dlopen() sees some symbols, but not others
- References:
- dlopen() sees some symbols, but not others
- From: Rob Y
- Re: dlopen() sees some symbols, but not others
- From: Paul Pluzhnikov
- Re: dlopen() sees some symbols, but not others
- From: Rob Y
- dlopen() sees some symbols, but not others
- Prev by Date: Re: dlopen() sees some symbols, but not others
- Next by Date: Planning on running ncftpd on AIX
- Previous by thread: Re: dlopen() sees some symbols, but not others
- Next by thread: Re: dlopen() sees some symbols, but not others
- Index(es):
Relevant Pages
|