From: Bobby Bingham <koorogi@koorogi.info>
To: musl@lists.openwall.com, John Mudd <johnbmudd@gmail.com>
Subject: Re: Re: 32 bit musl?
Date: Sun, 9 Oct 2016 10:10:36 -0500 [thread overview]
Message-ID: <20161009151036.GA25506@dora.lan> (raw)
In-Reply-To: <20161009144443.GA28065@port70.net>
On Sun, Oct 09, 2016 at 04:44:44PM +0200, Szabolcs Nagy wrote:
> * John Mudd <johnbmudd@gmail.com> [2016-10-09 10:29:02 -0400]:
> > On Sat, Oct 8, 2016 at 9:55 PM, John Mudd <johnbmudd@gmail.com> 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.
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.
next prev parent reply other threads:[~2016-10-09 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 22:20 John Mudd
2016-10-05 23:02 ` Rich Felker
2016-10-06 0:24 ` Shiz
2016-10-06 0:33 ` Rich Felker
2016-10-06 7:21 ` Jens Staal
2016-10-06 21:32 ` Rich Felker
2016-10-09 1:55 ` John Mudd
2016-10-09 9:36 ` Laurent Bercot
2016-10-09 14:29 ` John Mudd
2016-10-09 14:44 ` Szabolcs Nagy
2016-10-09 15:10 ` Bobby Bingham [this message]
2016-10-09 16:08 ` Rich Felker
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=20161009151036.GA25506@dora.lan \
--to=koorogi@koorogi.info \
--cc=johnbmudd@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).