From: Paul Onyschuk <ptmelville@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mdocml.bsd.lv
Subject: Re: Portability of fts() functions
Date: Sat, 9 Aug 2014 19:09:23 +0200 [thread overview]
Message-ID: <20140809190923.aa172f22b838ade5621fe601@gmail.com> (raw)
In-Reply-To: <20140809154928.GD30999@iris.usta.de>
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.
>
> So it looks like for the 1.13.1 release, it's probably to late
> to fix the fts(3) issue, and systems not having it will have the
> choice of either running 1.13.1 with "BUILD_TARGETS += db-build"
> disabled (that is, without apropos/makewhatis)
> or stay with 1.12.4 until 1.13.2 comes out.
>
> Do you think that would be tolerable?
For systems missing fts(3) I would say yes. I would worry more about
glibc scenario, especially if mdocml is packaged e.g. clean build on
x86_64 system used by packager, where it could break otherwise, wasting
someone's time.
Using occasion:
In file included from mansearch_const.c:20:0:
manpath.h:36:1: error: unknown type name '__END_DECLS'
mansearch_const.c is not including config.h before manpath.h, patch:
XXX
--- mansearch_const.c.orig
+++ mansearch_const.c
@@ -14,6 +14,10 @@
* ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
* OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*/
+#ifdef HAVE_CONFIG_H
+#include "config.h"
+#endif
+
#include <sys/types.h>
#include <stdint.h>
XXX
I think configure script should be guarded against standalone
execution. Right now you can do "./configure && make" expecting usual
behavior (if you forget about looking at INSTALL). Since in this case
${CC} won't be defined, script will try running commands starting with
"-Wno-unused -Werror". All tests will fail, enabling all compat
functions.
I also have additional question. Are there any plans for providing
man(1) command also? This would make mdocml a possible, standalone
replacement for groff and man-db combination (typical in Linux
distributions).
--
Paul Onyschuk
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-08-09 17:09 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 [this message]
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=20140809190923.aa172f22b838ade5621fe601@gmail.com \
--to=ptmelville@gmail.com \
--cc=discuss@mdocml.bsd.lv \
--cc=schwarze@usta.de \
/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).