From: "piranna@gmail.com" <piranna@gmail.com>
To: musl@lists.openwall.com
Subject: Re: static build and dlopen
Date: Wed, 27 Aug 2014 19:10:35 +0200 [thread overview]
Message-ID: <CAKfGGh2gzV67kXVCJirNE92yH-TP2dDTSK4dcXpK=pXBzwUapw@mail.gmail.com> (raw)
In-Reply-To: <20140827164309.GO12888@brightrain.aerifal.cx>
> As for a possible workaround, you can link your program dynamically
> (possibly including most of the libraries that your modules _won't_
> need to reference as static-linked in the main program binary) and
> include a wrapper script, or wrapper static-linked-binary, to exec
> your program explicitly via the dynamic linker, as in:
>
> /path/to/ld-musl-i386.so.1 -- /path/to/your/node "$@"
>
> or similar. This avoids the need to have musl "installed" on the
> target system; everything can be in a self-contained directory. I know
> some users are already doing something like this for deployments;
> maybe at some point we'll think about making some official tools to
> make it easier.
Yes, I though about this option before, has a dumb statically linked
executable to work as PID 1 that just only exec Node.js and wait until
it finishes, so I can use a standard dynamically linked one and do
whatever I want, but it's more like an ugly hack and since I was
already thinking to use a statically linked Node.js to make simpler
the filesystem layout, then I followed that path. It's not what I
wanted, but seems it would be the easiest path. At least I've learn a
lot the last week while fighting with this things... :-)
--
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
Unix."
– Linus Tordvals, creador del sistema operativo Linux
next prev parent reply other threads:[~2014-08-27 17:10 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
2014-08-27 20:07 ` piranna
2014-08-27 16:43 ` Rich Felker
2014-08-27 17:10 ` piranna [this message]
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='CAKfGGh2gzV67kXVCJirNE92yH-TP2dDTSK4dcXpK=pXBzwUapw@mail.gmail.com' \
--to=piranna@gmail.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).