mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: symlinks of glibc shared libs to musl libc.so
Date: Tue, 11 Jul 2017 12:20:30 -0400	[thread overview]
Message-ID: <20170711162030.GP1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170711104321.GA546@freedom>

On Tue, Jul 11, 2017 at 10:43:21AM +0000, sylvain.bertrand@gmail.com wrote:
> On Mon, Jul 10, 2017 at 10:06:44AM +0000, sylvain.bertrand@gmail.com wrote:
> > On Sun, Jul 09, 2017 at 10:02:21PM -0400, Rich Felker wrote:
> > > On Mon, Jul 10, 2017 at 01:36:40AM +0000, sylvain.bertrand@gmail.com wrote:
> > > > Hi,
> > > > 
> > > > I have some binaries which are dependent on glibc shared libs (except libgcc_s) and the glibc dynamic loader.
> > > > For instance: libdl, libpthreads... 
> > > > 
> > > > Do symlinks on libc.so based on glibc sonames give me a chance to make them work? (in
> > > > theory yes, since the symbols are there).
> > > 
> > > Are you asking about trying to run glibc-linked binaries with musl
> > > libc.so?
> > 
> > Exactly!
> > 
> > From you experience and feedbacks, do you think I have a chance with the proper
> > glibc symlinks?
> 
> No answer, does it mean there are too many glibc specific symbols?

You're going to need to clarify exactly what you mean by "proper glibc
symlinks". As I understood it, and as I told you in the part of my
reply you didn't quote, what you were talking about doing with
symlinks makes no sense, but maybe I misunderstood. Please describe in
detail what you want to achieve and what setup you're proposing/asking
if it will work.

Rich


  reply	other threads:[~2017-07-11 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  1:36 sylvain.bertrand
2017-07-10  2:02 ` Rich Felker
2017-07-10 10:06   ` sylvain.bertrand
2017-07-11 10:43     ` sylvain.bertrand
2017-07-11 16:20       ` Rich Felker [this message]
2017-07-11 17:53   ` sylvain.bertrand
2017-07-12  7:03     ` William Pitcock
2017-07-12 10:57       ` sylvain.bertrand

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=20170711162030.GP1627@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).