From: Duncan Roe <duncan_roe@optusnet.com.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: Can someone please update libnetfilter_queue online documentation
Date: Mon, 7 Sep 2020 11:22:55 +1000 [thread overview]
Message-ID: <20200907012255.GC6585@dimstar.local.net> (raw)
In-Reply-To: <20200906214904.GA7550@salvia>
On Sun, Sep 06, 2020 at 11:49:04PM +0200, Pablo Neira Ayuso wrote:
> On Sun, Sep 06, 2020 at 10:18:17AM +1000, Duncan Roe wrote:
> > Hi everyone,
> >
> > The online doc for libnetfilter_queue at
> > https://netfilter.org/projects/libnetfilter_queue/doxygen/html/ is still at
> > release 1.0.3.
>
> Refreshed.
Thanks, Pablo.
It looks like you don't have the 'graphviz' package installed, so there are
lines like
> Collaboration diagram for User-space network packet buffer:
with no diagram.
(e.g. in
https://netfilter.org/projects/libnetfilter_queue/doxygen/html/group__pktbuff.html).
'graphviz' supplies the 'dot' program which you may have seen doxygen
complaining about. I didn't see the problem originally because I have graphviz
but it didn't come with Slackware so the lack of it may be common.
The fix would be to have config.ac create HAVE_DOT and use that in
doxygen.cfg.in to put YES or NO on the HAVE_DOT and maybe some other lines.
I may tackle that sometime as I gain more confidence with aoutotools.
Cheers ... Duncan.
next prev parent reply other threads:[~2020-09-07 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 0:18 Can someone please update libnetfilter_queue online documentation Duncan Roe
2020-09-06 21:49 ` Pablo Neira Ayuso
2020-09-07 1:22 ` Duncan Roe [this message]
2020-09-07 10:39 ` [PATCH libnetfilter_queue] build: check whether dot is available when configuring doxygen Jeremy Sowden
2020-09-08 9:52 ` Duncan Roe
2020-09-08 10:49 ` Pablo Neira Ayuso
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=20200907012255.GC6585@dimstar.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.