From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo@netfilter.org>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: [ANNOUNCE] nftables 1.0.2 release
Date: Tue, 22 Feb 2022 16:49:35 +0100 [thread overview]
Message-ID: <YhUGD5J1fMJ6FSN6@salvia> (raw)
In-Reply-To: <YhUE38mgAKGV1WZn@salvia>
On Tue, Feb 22, 2022 at 04:44:31PM +0100, Pablo Neira Ayuso wrote:
> On Tue, Feb 22, 2022 at 04:28:39PM +0100, Arturo Borrero Gonzalez wrote:
> >
> >
> > On 2/21/22 17:09, Pablo Neira Ayuso wrote:
> > > Hi!
> > >
> > > The Netfilter project proudly presents:
> > >
> > > nftables 1.0.2
> > >
> >
> >
> > Hi there,
> >
> > this release doesn't build out of the box:
> >
> > [..]
> > Making all in examples
> > make[3]: Entering directory '/<<PKGBUILDDIR>>/examples'
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -c -o nft-buffer.o nft-buffer.c
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -c -o nft-json-file.o nft-json-file.c
> > nft-json-file.c:3:10: fatal error: nftables/libnftables.h: No such file or
> > directory
> > 3 | #include <nftables/libnftables.h>
> > | ^~~~~~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
> > nft-buffer.c:3:10: fatal error: nftables/libnftables.h: No such file or
> > directory
> > 3 | #include <nftables/libnftables.h>
> > | ^~~~~~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
> > [..]
> >
> >
> > Some options:
> > * make the missing header file properly available to the example files
> > * don't build the examples unless explicitly requested, not as part of the
> > main program build
> >
> > What do you suggest?
>
> It is fixed here, both things you mentioned:
>
> http://git.netfilter.org/nftables/commit/?id=18a08fb7f0443f8bde83393bd6f69e23a04246b3
Unfortunately, make distcheck did not catch this error since it uses
on libnftables local headers (my system already had previous version
headers).
next prev parent reply other threads:[~2022-02-22 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 16:09 [ANNOUNCE] nftables 1.0.2 release Pablo Neira Ayuso
2022-02-22 15:28 ` Arturo Borrero Gonzalez
2022-02-22 15:44 ` Pablo Neira Ayuso
2022-02-22 15:49 ` Pablo Neira Ayuso [this message]
2022-02-23 13:21 ` Arturo Borrero Gonzalez
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=YhUGD5J1fMJ6FSN6@salvia \
--to=pablo@netfilter.org \
--cc=arturo@netfilter.org \
--cc=netfilter-devel@vger.kernel.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 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).