From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by krisdoz.my.domain (8.14.5/8.14.5) with ESMTP id s79H9WXF003233 for ; Sat, 9 Aug 2014 13:09:32 -0400 (EDT) Received: by mail-wg0-f46.google.com with SMTP id m15so6905573wgh.5 for ; Sat, 09 Aug 2014 10:09:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=sRqTaJpwGTv+Wfq6JyZbL+VmcmyqatBsNvukA9pTpII=; b=cWStdz1KhxtHabhoc1YHBN8LZiRF4hk73kg9Ub+4ugCQfTGdXFPC0bHUfu7+rJBCzT 6ojy0LK2qS31DmvJufq3GswKUWShGsWGkpdNqirYPEj+F9/VmTl4THMBuR1z8WYOMiJ7 zfmkaMwhfT8B8y6+m8Ur/WkmEy/nEFqNO37i8dDATVxwrD5iWqTmTmOLtOR0uddxP5cD Mu5PP34RmM+gx/uYvwi/C6o9shBTNA3LszPaFkcadSDnagTcq1+eG47VznIRNfswseta dA71yByOrEiTh3Bypp/ICox7zh3t4wpx73c4LODN5svSYta8M4dQFpQgN2Ho8XldP3Qt l8HA== X-Received: by 10.180.108.1 with SMTP id hg1mr7467478wib.25.1407604166378; Sat, 09 Aug 2014 10:09:26 -0700 (PDT) Received: from sigil.Belkin ([109.231.16.247]) by mx.google.com with ESMTPSA id fc7sm25840779wjc.37.2014.08.09.10.09.24 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Aug 2014 10:09:25 -0700 (PDT) Date: Sat, 9 Aug 2014 19:09:23 +0200 From: Paul Onyschuk To: Ingo Schwarze Cc: discuss@mdocml.bsd.lv Subject: Re: Portability of fts() functions Message-Id: <20140809190923.aa172f22b838ade5621fe601@gmail.com> In-Reply-To: <20140809154928.GD30999@iris.usta.de> References: <20140809123827.6df5072f894ac5795f4228d3@gmail.com> <20140809154928.GD30999@iris.usta.de> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.23; x86_64-alpine-linux-musl) X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 #include 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