tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Thomas Klausner <wiz@NetBSD.org>
To: tech@mdocml.bsd.lv
Cc: Joerg Sonnenberger <joerg@britannica.bec.de>
Subject: Re: call for testing: mandoc-1.13.4 release candidate
Date: Sat, 9 Jul 2016 15:18:28 +0200	[thread overview]
Message-ID: <20160709131828.GB5161@danbala.tuwien.ac.at> (raw)
In-Reply-To: <20160709131158.GA6629@athene.usta.de>

[-- Attachment #1: Type: text/plain, Size: 301 bytes --]

I've tested 1.13.4rc1 on NetBSD-7.99.33 and it built fine, thank you.

There are a couple of patches in pkgsrc by joerg that, it seems, have
not been sent upstream. They remove the inclusion of getopt.h. At
least on NetBSD, the getopt(3) man page mentions that getopt is in
unistd.h.

Cheers,
 Thomas

[-- Attachment #2: patch-demandoc.c --]
[-- Type: text/plain, Size: 280 bytes --]

$NetBSD: patch-demandoc.c,v 1.1 2015/12/10 02:50:19 joerg Exp $

--- demandoc.c.orig	2015-12-07 15:20:07.413956576 +0000
+++ demandoc.c
@@ -20,7 +20,6 @@
 
 #include <assert.h>
 #include <ctype.h>
-#include <getopt.h>
 #include <stdio.h>
 #include <stdlib.h>
 #include <string.h>

[-- Attachment #3: patch-mandocdb.c --]
[-- Type: text/plain, Size: 277 bytes --]

$NetBSD: patch-mandocdb.c,v 1.7 2015/12/10 02:50:19 joerg Exp $

--- mandocdb.c.orig	2015-12-07 15:20:09.513956486 +0000
+++ mandocdb.c
@@ -30,7 +30,6 @@
 #else
 #include "compat_fts.h"
 #endif
-#include <getopt.h>
 #include <limits.h>
 #include <stddef.h>
 #include <stdio.h>

[-- Attachment #4: patch-manpage.c --]
[-- Type: text/plain, Size: 281 bytes --]

$NetBSD: patch-manpage.c,v 1.1 2015/12/10 02:50:19 joerg Exp $

--- manpage.c.orig	2015-12-07 15:20:30.565955584 +0000
+++ manpage.c
@@ -20,7 +20,6 @@
 #include <sys/types.h>
 
 #include <assert.h>
-#include <getopt.h>
 #include <limits.h>
 #include <stdint.h>
 #include <stdio.h>

[-- Attachment #5: patch-mansearch.c --]
[-- Type: text/plain, Size: 286 bytes --]

$NetBSD: patch-mansearch.c,v 1.1 2015/12/10 02:50:19 joerg Exp $

--- mansearch.c.orig	2016-07-09 11:15:54.000000000 +0000
+++ mansearch.c
@@ -26,7 +26,6 @@
 #endif
 #include <errno.h>
 #include <fcntl.h>
-#include <getopt.h>
 #include <glob.h>
 #include <limits.h>
 #include <regex.h>

       reply	other threads:[~2016-07-09 13:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sfid-H20160709-151232-+015.17-1@spamfilter.osbf.lua>
     [not found] ` <20160709131158.GA6629@athene.usta.de>
2016-07-09 13:18   ` Thomas Klausner [this message]
2016-07-09 15:30     ` Ingo Schwarze
2016-07-09 13:39   ` Baptiste Daroussin FreeBSD
2016-07-09 14:31     ` Anthony J. Bentley
2016-07-09 15:29       ` New db format (was Re: call for testing: mandoc-1.13.4 release candidate) Baptiste Daroussin
2016-07-09 16:12         ` New db format Ingo Schwarze
2016-08-05 20:26           ` Baptiste Daroussin
2016-07-09 14:28   ` call for testing: mandoc-1.13.4 release candidate Svyatoslav Mishyn Crux
2016-07-10 14:08     ` Ingo Schwarze
2016-07-09 18:21   ` Svyatoslav Mishyn
2016-07-09 21:13     ` Ingo Schwarze
2016-07-09 18:55   ` Svyatoslav Mishyn Crux
2016-07-10 10:46     ` Svyatoslav Mishyn
2016-07-10 13:39       ` Ingo Schwarze
2016-07-10 14:27   ` Christian Neukirchen
2016-07-10 16:36     ` Ingo Schwarze
2016-07-10 16:48       ` Christian Neukirchen
2016-07-10 18:34         ` Ingo Schwarze

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=20160709131828.GB5161@danbala.tuwien.ac.at \
    --to=wiz@netbsd.org \
    --cc=joerg@britannica.bec.de \
    --cc=tech@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).