discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Paul Onyschuk <ptmelville@gmail.com>
Cc: discuss@mdocml.bsd.lv
Subject: Re: Portability of fts() functions
Date: Mon, 11 Aug 2014 05:28:50 +0200	[thread overview]
Message-ID: <20140811032849.GJ325@iris.usta.de> (raw)
In-Reply-To: <20140810125340.6c5c29fcb9288000b093074b@gmail.com>

Hi Paul,

Paul Onyschuk wrote on Sun, Aug 10, 2014 at 12:53:40PM +0200:
> On Sat, 9 Aug 2014 17:49:28 +0200 Ingo Schwarze wrote:

>> I guess what is needed is a compat_fts.h/compat_fts.c just like
>> for ohash(3).  I fear that won't be something that can be done
>> in a hurry, though.

> This may be helpful in future.  Libnbcompat from pkgsrc is providing
> portable fts(3) implementation under reasonable conditions (3-clause
> BSD license).
> 
> http://cvsweb.netbsd.org/bsdweb.cgi/ \
> pkgsrc/pkgtools/libnbcompat/files/nbcompat/

Thanks for the pointer!

While i didn't use the NetBSD implementation itself - it seems to
lack some bugfixes that the OpenBSD implementation has - the
libnbcompat file was quite helpful for inspiration how to work around
the lack of d_namlen and ALIGN/ALIGNBYTES on Linux.

Anyway, the mdocml.bsd.lv repo now contains a fallback for fts(3)
that works for me on OpenBSD and Linux.  It will be contained in
the future mandoc 1.13.2 release.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2014-08-11  3:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 10:38 Paul Onyschuk
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 [this message]
  -- 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=20140811032849.GJ325@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    --cc=ptmelville@gmail.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. 
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).