mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Hello
Date: Thu, 5 Jul 2012 19:34:57 -0400	[thread overview]
Message-ID: <20120705233457.GR544@brightrain.aerifal.cx> (raw)
In-Reply-To: <20120706012417.5ae680f0@sibserver.ru>

On Fri, Jul 06, 2012 at 01:24:17AM +0800, orc wrote:
> On Thu, 7 Jun 2012 23:31:41 -0400
> Rich Felker <dalias@aerifal.cx> wrote:
> 
> > > So there is a question: will musl support this configs? Or I will
> > > need patchelf and 'libc6-legacy' for them?
> > 
> > It's intended to work, but I don't know whether it does yet.
> 
> Did some research there last days: for, example, one that proprietary
> drivers that nvidia ships it was required about 30 missing symbols,
> half of them are one-liners system calls, 5 were glibc-specific
> functions that were easy to add (one of them is gnu_get_libc_version()
> that is designed to return a plain string), 4 were missing math
> functions that already defined as a macros in math.h, rest is a forest
> of weak aliases around already existed functions (plus two aliases to
> objects). That allowed me to run plain unmodified X11 applications (not
> even gtk2 ones) and accelerated glxgears without errors (The gtk2 or
> qt or other such libraries compiled against glibc is not my target,
> just to prove that userspace nvidia could be run with musl).
> If you interested, I can put a patch that adds such forest of
> weak_alias'es to improve (partly) glibc compatibility. And separate
> patch for missing syscall wrappers.

I'm very interested in this. I'm surprised it was that easy to make it
work, and just curious about all the aliases that were involved and
whether they make since or whether they're hacks. Post patches or a
report in whatever form you prefer; I'll review it and hopefully it
can be committed without much additional fuss.

Rich


  reply	other threads:[~2012-07-05 23:34 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 12:01 Hello orc
2012-06-07 13:13 ` Hello John Spencer
2012-06-07 15:18   ` Hello orc
2012-06-07 16:29     ` Hello John Spencer
2012-06-07 16:19       ` Hello Rich Felker
2012-06-07 17:15         ` Hello orc
2012-06-08  3:31           ` Hello Rich Felker
2012-06-08  5:49             ` Hello Isaac Dunham
2012-06-08 12:28             ` Hello aep
2012-06-08 14:14               ` Hello Rich Felker
2012-06-08 16:17                 ` Hello aep
2012-06-08 16:11                   ` Hello Rich Felker
2012-06-09  2:05                   ` Hello Isaac Dunham
2012-07-05 17:24             ` Hello orc
2012-07-05 23:34               ` Rich Felker [this message]
2012-07-06  6:06                 ` Hello orc
2012-07-06  6:26                   ` Hello Rich Felker
2012-07-06  8:22                     ` Hello orc
2012-07-06 23:14                       ` Hello idunham
2012-07-07  0:57                         ` Hello Rich Felker
2012-07-07  8:07                         ` Hello orc
2012-07-07 15:54                           ` Hello idunham
2012-07-08  9:09                             ` Hello orc
2012-06-07 17:45         ` Hello Christian Neukirchen
2012-06-07 18:03       ` Hello Jens Staal
2012-06-07 19:10         ` Hello John Spencer
2012-06-07 17:33     ` Hello Jens Staal
2012-06-07 17:59       ` Hello orc
2012-06-20  7:29     ` Hello orc
2012-06-23  1:43       ` Hello idunham
2012-06-23  1:51         ` Hello Rich Felker
2012-06-25 12:09           ` Hello orc
2012-06-25 11:59         ` Hello orc
2012-06-25 13:53           ` Hello idunham
2012-07-22 23:09 Hello idunham
2012-07-23  2:01 ` Hello Rich Felker
2012-07-23  3:49   ` Hello idunham
2012-07-23 21:01     ` Hello 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=20120705233457.GR544@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).