From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: static linking and dlopen
Date: Sun, 9 Dec 2012 16:53:14 -0500 [thread overview]
Message-ID: <20121209215314.GG20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <1355083763.9353.2@driftwood>
On Sun, Dec 09, 2012 at 02:09:23PM -0600, Rob Landley wrote:
> 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?
The dlopen in libc.a simply always-fails. For programs where loading
modules is optional, this is probably the ideal behavior.
Rich
prev parent reply other threads:[~2012-12-09 21:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 18:09 Paul Schutte
2012-12-08 20:47 ` Szabolcs Nagy
2012-12-09 20:02 ` Rob Landley
2012-12-08 22:52 ` Rich Felker
2012-12-08 23:17 ` Charlie Kester
2012-12-08 23:23 ` Rich Felker
2012-12-09 0:04 ` Paul Schutte
2012-12-09 0:16 ` Rich Felker
2012-12-09 15:24 ` Paul Schutte
2012-12-09 17:54 ` Rich Felker
2012-12-09 19:07 ` Szabolcs Nagy
2012-12-09 19:24 ` Rich Felker
2012-12-09 2:39 ` Szabolcs Nagy
2012-12-09 6:36 ` croco
2012-12-09 7:25 ` Isaac Dunham
2012-12-09 8:10 ` Charlie Kester
2012-12-09 10:08 ` croco
2012-12-09 11:46 ` Szabolcs Nagy
2012-12-09 15:11 ` Rich Felker
2012-12-09 20:43 ` Rob Landley
2012-12-08 23:29 ` Paul Schutte
2012-12-09 2:55 ` Szabolcs Nagy
2012-12-09 3:10 ` Rich Felker
2012-12-09 7:30 ` Isaac Dunham
2012-12-09 20:09 ` Rob Landley
2012-12-09 21:53 ` Rich Felker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121209215314.GG20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).