Date: Sun, 09 Dec 2012 14:09:23 -0600 From: Rob Landley <rob@...dley.net> To: musl@...ts.openwall.com Cc: musl@...ts.openwall.com Subject: Re: static linking and dlopen On 12/08/2012 04:52:37 PM, Rich Felker wrote: > The source of all these problems is basically the same as the benefit > of static linking: the fact that the linker resolves, statically at > link time, which object files are needed to satisfy the needs of the > program. With dlopen, however, there is no static answer; *any* object > is potentially-needed, not directly by the main program, but possibly > by loaded modules. Is there some way you could put a dlopen() symbol in libc.a that forces a build break? Perhaps a redirect to dlopen_is_not_compatible_with_static_linking_go_read_posix? Rob
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.