From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6837 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: dynamic linking (Re: [musl] musl and android) Date: Thu, 15 Jan 2015 07:15:36 -0500 Message-ID: <20150115121536.GO4574@brightrain.aerifal.cx> References: <20150115161322.4ee903b7@sibserver.ru> <20150115110158.GN4574@brightrain.aerifal.cx> <20150115120004.GY14316@example.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1421324156 24016 80.91.229.3 (15 Jan 2015 12:15:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 15 Jan 2015 12:15:56 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6850-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jan 15 13:15:52 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1YBjL4-0001CO-FD for gllmg-musl@m.gmane.org; Thu, 15 Jan 2015 13:15:50 +0100 Original-Received: (qmail 1468 invoked by uid 550); 15 Jan 2015 12:15:46 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 1460 invoked from network); 15 Jan 2015 12:15:45 -0000 Content-Disposition: inline In-Reply-To: <20150115120004.GY14316@example.net> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:6837 Archived-At: On Thu, Jan 15, 2015 at 01:00:05PM +0100, u-wsnj@aetey.se wrote: > On Thu, Jan 15, 2015 at 06:01:58AM -0500, Rich Felker wrote: > > copy of the dynamic linker (libc.so/ld-musl) in the package > > and executing the program via a wrapper script that manually invokes > > the dynamic linker (so the hard-coded PT_INTERP pathname isn't > > needed). > > > But these are not the approaches I'd like to be > > recommending in the long term... :( > > Actually I believe (and know from long time experience) this to be > the only "sane"/robust/general way to run dynamically linked executables. It depends on your perspective. If you're viewing them as self-contained entities, then yes, but if you're viewing them as something running in an existing library ecosystem, there's no problem. > I don't think that the implications of hardcoding the interpreter > path were well understood when dynamic linking was first deployed, > the hardcoding merely became percepted as the only/natural approach > when the purpose was to cheaply imitate the behaviour of statically > linked programs. (This mimics the #!/... which is similarly > limited/broken. The plain text scripts are though relatively easy > to modify to hack around the limitation, according to local curcumstances) I think this could be fixed easily by having the kernel support $ORIGIN in PT_INTERP. Rich