From: enh <enh@google.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com, Aditya Kumar <appujee@google.com>
Subject: Re: [musl] fts.h
Date: Mon, 27 Jan 2025 10:34:45 -0500 [thread overview]
Message-ID: <CAJgzZor=FpJTqembh4JtwXx+WbY33ab0uY=7eFH-Ro=PCdYBmw@mail.gmail.com> (raw)
In-Reply-To: <20250127152534.GR10433@brightrain.aerifal.cx>
On Mon, Jan 27, 2025 at 10:25 AM Rich Felker <dalias@libc.org> wrote:
>
> On Thu, Jan 23, 2025 at 01:54:41PM -0500, enh wrote:
> > https://wiki.musl-libc.org/faq says "If glibc bug 15838 is fixed by
> > adding an fts64 interface in glibc, we could consider supporting it
> > with a matching ABI in musl, but it seems more likely that glibc will
> > just deprecate this interface", but that bug _was_ fixed in 2015 for
> > glibc 2.23...
>
> I wonder when that text was written. While we could certainly consider
> it, lack of any apparent need so far suggests that it wouldn't meet
> the modern criteria for inclusion in musl.
well, the reason i'm mentioning this is because Android's mixing in
the bionic (lightly modified openbsd) fts to its host musl to be able
to build various things.
one of them is the bionic fts test (we build the bionic tests against
the host libc too, for comparison), so we can ignore that.
bionic/tests/fts_test.cpp:32:10: fatal error: 'fts.h' file not found
the other two seem legit though:
external/vboot_reference/futility/updater_archive.c:13:10: fatal
error: 'fts.h' file not found
external/selinux/libselinux/utils/selabel_get_digests_all_partial_matches.c:7:10:
fatal error: 'fts.h' file not found
> The main motivation I could potentially see flipping this is if there
> are a significant number of programs shipping their own (e.g. gnulib?)
> versions of fts, that would save significant code-duplication disk
> space (or get better behavior of some sort) if using a shared copy in
> libc.
iirc there's a way to grep the source of all debian packages, though
it would be hard to know how many of them have an alternative like
ftw(3) they can use instead.
> Rich
next prev parent reply other threads:[~2025-01-27 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 18:54 enh
2025-01-24 23:20 ` [musl] fts.h appujee
2025-01-27 15:25 ` [musl] fts.h Rich Felker
2025-01-27 15:34 ` enh [this message]
2025-01-27 19:17 ` Khem Raj
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='CAJgzZor=FpJTqembh4JtwXx+WbY33ab0uY=7eFH-Ro=PCdYBmw@mail.gmail.com' \
--to=enh@google.com \
--cc=appujee@google.com \
--cc=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).