From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/21002] Incompatible with MUSL libc
Date: Sat, 31 Dec 2016 15:20:00 -0000 [thread overview]
Message-ID: <bug-21002-10460-dychjZC9E1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21002-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21002
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjw at redhat dot com
--- Comment #6 from Mark Wielaard <mjw at redhat dot com> ---
(In reply to Luiz Angelo Daros de Luca from comment #5)
> It is not part of my use case but besides the problems already mentioned,
> elfutils/src will still miss from glibc:
>
> - obstack
> - fts (I already use a patch to remove its dependency on lib*)
We could probably add these using gnulib if it is useful for alternative glibc
implementations that are missing them. But we haven't used gnulib modules
before so we would need tweak the infrastructure a little to accommodate them.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-31 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21002-10460@http.sourceware.org/bugzilla/>
2016-12-29 23:38 ` mark at klomp dot org
2016-12-30 21:29 ` luizluca at gmail dot com
2016-12-30 23:56 ` luizluca at gmail dot com
2016-12-31 15:20 ` mjw at redhat dot com [this message]
2018-03-09 23:20 ` mark at klomp dot org
2018-03-10 2:23 ` luizluca at gmail dot com
2018-03-11 14:22 ` mark at klomp dot org
2021-02-05 14:49 ` mark at klomp dot org
2021-08-27 17:13 ` mark at klomp dot org
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=bug-21002-10460-dychjZC9E1@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).