From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: Re: static build and dlopen
Date: Wed, 27 Aug 2014 18:20:24 +0100 [thread overview]
Message-ID: <CAK4o1WxSLAnGtOv+eVAMP107E0_wxEJ1A82MkDx5soQRvgeN2w@mail.gmail.com> (raw)
In-Reply-To: <CAKfGGh0W2U+d4Ew1YFe=3H8TzR08Wdp=+YsmPzoec2OkXCEhhg@mail.gmail.com>
On Wed, Aug 27, 2014 at 6:01 PM, piranna@gmail.com <piranna@gmail.com> wrote:
> The de-facto standard in Node.js is that all the compiled modules are
> static ones (.a files) with no external dependencies at all, just to
> make it simpler to move to another environments. This contrast to how
> Python works, where compiled modules are dynamic ones (.so). I'm
> honestly not sure what are the low-level details of Node.js compiled
> modules, but the general idea of Node.js modules is make them as
> independent as possible and left to Node.js require() function to
> manage the dependencies, so probably this would also apply to compiled
> ones... Only point left here is if in fact .node files are in fact .a
> files with a different extension or if they are wrapped someway, so in
> that case dlopen() is efectively loading .a files (that would be a
> surprise to me, but would left open the door to solve this problem...)
If this is really true, and they are static, then you should be able
to write a loader that has a function called dlopen etc but which is
not actually the full dynamic linker, just pretends to be, and will
work from a static binary. It could link in the modules at compile
time and just return static pointers (I have done this with Lua code,
pretending to be in a dynamic environment when actually in a static
one, just return pointers from dlsym calls that are fixed at compile
time).
Justin
next prev parent reply other threads:[~2014-08-27 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 14:14 piranna
2014-08-27 15:27 ` Szabolcs Nagy
2014-08-27 17:01 ` piranna
2014-08-27 17:20 ` Justin Cormack [this message]
2014-08-27 20:07 ` piranna
2014-08-27 16:43 ` Rich Felker
2014-08-27 17:10 ` piranna
2014-08-27 18:48 ` Laurent Bercot
2014-08-27 20:19 ` piranna
2014-08-27 20:51 ` Rich Felker
2014-08-27 20:59 ` Laurent Bercot
2014-08-27 21:04 ` Rich Felker
2014-08-27 22:54 ` Kurt H Maier
2014-08-27 23:24 ` Laurent Bercot
2014-08-27 23:36 ` Brent Cook
2014-09-01 23:38 ` piranna
2014-09-02 0:38 ` Rich Felker
2014-09-02 0:49 ` piranna
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=CAK4o1WxSLAnGtOv+eVAMP107E0_wxEJ1A82MkDx5soQRvgeN2w@mail.gmail.com \
--to=justin@specialbusservice.com \
--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).