Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] RTLD_DEEPBIND and uClibc
Date: Thu, 17 Jan 2013 20:48:38 +0200	[thread overview]
Message-ID: <50F84786.7030900@petroprogram.com> (raw)
In-Reply-To: <CA+wH295dD1eRwkfBXorP78zxcjy4jKPuLOK87bjqoR79R9OY=w@mail.gmail.com>

17.1.2013 19:09, Alex Bradbury kirjoitti:
> On 17 January 2013 16:51, Stefan Fr?berg
> <stefan.froberg@petroprogram.com> wrote:
>> Is it true that musl supports (at least most) of the glibc ABI ?
>> (my biggest worry so far when using uClibc is that I encounter an
>> application that is provided as glibc-only
>> binary and no source code provided.)
> Yes, this is one of the goals. There was a big discussion on the musl
> mailing list <http://dir.gmane.org/gmane.linux.lib.musl.general> in
> December. One of the aims is glibc ABI compatibility, with
> applications like Opera being discussed on the list. Development is
> *very* active and Rich Felker (lead dev) seems to respond very quickly
> to issues or bug reports.
>
> In fact, I've fallen behind following the musl mailing list the last
> couple of months but see a recent posts that indicate there has been
> good glibc ABI progress
> <http://article.gmane.org/gmane.linux.lib.musl.general/2549>. Of
> course many of the proprietary apps are likely to use C++, and the C++
> ABI is...fiddly.
>
>> What about it's configuration ? Does it have nice kconf style  "make
>> menuconfig" like uClibc or what ?
> I don't *think* so, but could be wrong. Still, it aims to be
> substantially lighterweight than glibc, while hopefully providing more
> performant implementations of functions than either glibc or uclibc.
>
> Alex

Thanks Alex!
I will keep watching that list.

Stefan

  reply	other threads:[~2013-01-17 18:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 12:51 [Buildroot] RTLD_DEEPBIND and uClibc Stefan Fröberg
2013-01-16 23:00 ` Thomas Petazzoni
2013-01-17  0:36   ` Stefan Fröberg
2013-01-17  8:31     ` Thomas Petazzoni
2013-01-17 13:50       ` Stefan Fröberg
2013-01-17 16:18         ` Alex Bradbury
2013-01-17 16:51           ` Stefan Fröberg
2013-01-17 17:09             ` Alex Bradbury
2013-01-17 18:48               ` Stefan Fröberg [this message]
2013-01-17 22:03           ` Peter Korsgaard
2013-01-17 17:44         ` Yann E. MORIN
2013-01-17 18:47           ` Stefan Fröberg
2013-01-17 20:38             ` Yann E. MORIN
2013-01-17 20:41               ` Yann E. MORIN
2013-01-17 20:51               ` Stefan Fröberg
2013-01-17 21:17                 ` Yann E. MORIN
2013-01-17 21:23                   ` Stefan Fröberg

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=50F84786.7030900@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox