mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: How to use MUSL without installing it?
Date: Tue, 4 Sep 2018 10:30:25 -0400	[thread overview]
Message-ID: <20180904143025.GA1878@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180904153910.522997076cd761d32db94028@asm32.info>

On Tue, Sep 04, 2018 at 03:39:10PM +0300, John Found wrote:
> On Tue, 4 Sep 2018 08:27:20 -0400
> Rich Felker <dalias@libc.org> wrote:
> 
> > This won't work -- a relative path is relative to the current working
> > directory, not the location of the executable. If you want users to be
> > able to invoke your program normally, you need to just provide a
> > wrapper script that does something like
> > 
> > 	exec $(basedir)/ld-musl-i386.so --library-path ... -- $(basedir)/your_program.bin "$@"
> > 
> > I'm actually working on a design to allow direct invocation of
> > dynamic-linked programs without absolute dynamic linker paths, but it
> > will be a while before it's done and included in musl.
> 
> It works like a charm. :) It is a back-end web application and it always
> is started in it's own directory, as a service or from the web server.
> 
> I use this way, because when installing web applications on shared hosting,
> the user can't install libraries to the system directories of the server.
> He is limited only to the his document root.

OK, it works for your usage case but not in general. :)

Rich


  reply	other threads:[~2018-09-04 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 20:24 John Found
2018-09-04  9:40 ` Szabolcs Nagy
2018-09-04 11:34   ` John Found
2018-09-04 11:58     ` Szabolcs Nagy
2018-09-04 12:20       ` John Found
2018-09-04 12:27         ` Rich Felker
2018-09-04 12:39           ` John Found
2018-09-04 14:30             ` Rich Felker [this message]
2018-09-04 13:00           ` Jon Chesterfield
2018-09-04 14:38             ` Rich Felker
2018-09-04 13:27       ` John Found

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=20180904143025.GA1878@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).