From: Paul Onyschuk <ptmelville@gmail.com>
To: discuss@mdocml.bsd.lv
Subject: Portability of fts() functions
Date: Sat, 9 Aug 2014 12:38:27 +0200 [thread overview]
Message-ID: <20140809123827.6df5072f894ac5795f4228d3@gmail.com> (raw)
mandocdb.c in v1.13.x introduced dependency on fts() family of
functions. This will bite on non-BSD systems.
Musl libc doesn't provide it at all, neither does systems of Solaris
origin I guess, but then glibc does something even worse [1], relevant
fts.h header [2]. AFAIK uClibc replicated behavior of glibc.
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=15838
[2] https://sourceware.org/git/?p=glibc.git;a=blob;f=io/fts.h
--
Paul Onyschuk
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2014-08-09 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 10:38 Paul Onyschuk [this message]
2014-08-09 15:49 ` Ingo Schwarze
2014-08-09 17:09 ` Paul Onyschuk
2014-08-09 21:59 ` Ingo Schwarze
2014-08-09 23:26 ` Paul Onyschuk
2014-08-10 2:46 ` Ingo Schwarze
2014-08-10 1:23 ` man(1) replacement Ingo Schwarze
2014-08-10 10:53 ` Portability of fts() functions Paul Onyschuk
2014-08-11 3:28 ` Ingo Schwarze
-- strict thread matches above, loose matches on Subject: below --
2014-08-09 9:54 Paul Onyschuk
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=20140809123827.6df5072f894ac5795f4228d3@gmail.com \
--to=ptmelville@gmail.com \
--cc=discuss@mdocml.bsd.lv \
/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 NNTP newsgroup(s).