From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10605 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: 32 bit musl? Date: Sun, 9 Oct 2016 12:08:51 -0400 Message-ID: <20161009160851.GC19318@brightrain.aerifal.cx> References: <20161009144443.GA28065@port70.net> <20161009151036.GA25506@dora.lan> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1476029359 10121 195.159.176.226 (9 Oct 2016 16:09:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 9 Oct 2016 16:09:19 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) Cc: musl@lists.openwall.com, John Mudd To: Bobby Bingham Original-X-From: musl-return-10618-gllmg-musl=m.gmane.org@lists.openwall.com Sun Oct 09 18:09:16 2016 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 1btGev-0000tR-0X for gllmg-musl@m.gmane.org; Sun, 09 Oct 2016 18:09:05 +0200 Original-Received: (qmail 13621 invoked by uid 550); 9 Oct 2016 16:09:05 -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 13601 invoked from network); 9 Oct 2016 16:09:05 -0000 Content-Disposition: inline In-Reply-To: <20161009151036.GA25506@dora.lan> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:10605 Archived-At: On Sun, Oct 09, 2016 at 10:10:36AM -0500, Bobby Bingham wrote: > On Sun, Oct 09, 2016 at 04:44:44PM +0200, Szabolcs Nagy wrote: > > * John Mudd [2016-10-09 10:29:02 -0400]: > > > On Sat, Oct 8, 2016 at 9:55 PM, John Mudd wrote: > > > > > > > Rich's musl-cross-make builds 32-bit executables that use musl libs. It > > > > kills two birds with one stone. That's great. > > > > > > > > But it appears to expect musl libc to be installed in /lib for dynamically > > > > linked executables. That's not an option for me. Is there a way I can > > > > override this? > > > > > > > > > > > Thanks Laurent, I used symbolic link in /lib for testing on my development > > > machine. That works well. But I don't have reasonable access to root user > > > when I deploy for production. > > > > deploy static linked binary or use explicit -Wl,-dynamic-linker > > Using -Wl,-dynamic-linker will result in binaries that will not run on > normal musl systems. It will also result in binaries that require the end user to have them (or at least the dynamic linker part) installed in exactly the same absolute path that you came up with when building them. > If you can deploy the musl libc alongside your program, you can invoke it > as `/path/to/libc.so /path/to/your/program`. This can be done by a shell > script you also deploy. Indeed, this is the recommended approach for shipping dynamic-linked binaries to be run on non-musl-based systems. Rich