From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13181 Path: news.gmane.org!.POSTED!not-for-mail From: John Found Newsgroups: gmane.linux.lib.musl.general Subject: Re: How to use MUSL without installing it? Date: Tue, 4 Sep 2018 15:39:10 +0300 Message-ID: <20180904153910.522997076cd761d32db94028@asm32.info> References: <20180903232441.0c0e1e868bac54e3b9b31226@asm32.info> <20180904094020.GM4418@port70.net> <20180904143439.121b6867f3e7fb99d4f1b527@asm32.info> <20180904115828.GN4418@port70.net> <20180904152012.ba537d4bb4d775753bfe8f72@asm32.info> <20180904122720.GZ1878@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1536064714 16211 195.159.176.226 (4 Sep 2018 12:38:34 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 4 Sep 2018 12:38:34 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-13197-gllmg-musl=m.gmane.org@lists.openwall.com Tue Sep 04 14:38:30 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1fxAbD-00044M-Qs for gllmg-musl@m.gmane.org; Tue, 04 Sep 2018 14:38:27 +0200 Original-Received: (qmail 13789 invoked by uid 550); 4 Sep 2018 12:40:31 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 13771 invoked from network); 4 Sep 2018 12:40:31 -0000 In-Reply-To: <20180904122720.GZ1878@brightrain.aerifal.cx> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-unknown-linux-gnu) Xref: news.gmane.org gmane.linux.lib.musl.general:13181 Archived-At: On Tue, 4 Sep 2018 08:27:20 -0400 Rich Felker 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. > > Rich 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. -- John Found