From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Stéphane Veyret" <sveyret@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nftables v4 1/1] add ct expectations support
Date: Fri, 5 Jul 2019 20:07:49 +0200 [thread overview]
Message-ID: <20190705180749.fku5r3tnt4jzskpp@salvia> (raw)
In-Reply-To: <CAFs+hh6TcVM1HbK=iZF5vfSnnGYdtpSTTy=DR3LizSgkuYQghA@mail.gmail.com>
Hi Stéphane,
On Thu, Jul 04, 2019 at 08:48:50PM +0200, Stéphane Veyret wrote:
> Le mer. 3 juil. 2019 à 01:12, Pablo Neira Ayuso <pablo@netfilter.org> a écrit :
> > Please, make sure you run ./configure with --with-json.
>
> I'm sorry, but I don't manage to compile it anymore.
>
> I took latest versions of kernel/lib/nft and merged my modifications
> to nft. But when I try to compile nft, even if the configure goes
> well, the make fails. The message is that it needs libnftnl > 1.1.3
> whereas configure only requires version 1.1.1, and the lib creates a
> package with version 1.1.2.
Make sure you install a fresh libnftnl from git.netfilter.org.
> If I cheat (and update the libnftnl.pc
> file by hand), then make fails later, when compiling libnftables.c
> with the following messages :
> libnftables.c:112:14: warning: data definition has no type or storage class
> EXPORT_SYMBOL(nft_ctx_add_include_path);
> ^
> libnftables.c:112:15: warning: type defaults to ‘int’ in declaration
> of « nft_ctx_add_include_path » [-Wimplicit-int]
> EXPORT_SYMBOL(nft_ctx_add_include_path);
> ^~~~~~~~~~~~~~~~~~~~~~~~
> libnftables.c:112:15: error: « nft_ctx_add_include_path » redeclared
> as different kind of symbol
> In file included from libnftables.c:9:
> ../include/nftables/libnftables.h:76:5: note: previous definition of «
> nft_ctx_add_include_path » was here
> int nft_ctx_add_include_path(struct nft_ctx *ctx, const char *path);
> ^~~~~~~~~~~~~~~~~~~~~~~~
> libnftables.c:113:5: warning: no previous prototype for function «
> nft_ctx_add_include_path » [-Wmissing-prototypes]
> int nft_ctx_add_include_path(struct nft_ctx *ctx, const char *path)
> ^~~~~~~~~~~~~~~~~~~~~~~~
>
> Does someone have a clue ?
From the nftables tree, after pulling latest changes from
git.netfilter.org, run:
autoreconf -fi
before ./configure.
next prev parent reply other threads:[~2019-07-05 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 9:28 [PATCH nftables v4 0/1] add ct expectation support Stéphane Veyret
2019-06-05 9:28 ` [PATCH nftables v4 1/1] add ct expectations support Stéphane Veyret
2019-07-02 23:12 ` Pablo Neira Ayuso
2019-07-03 14:32 ` Stéphane Veyret
2019-07-04 18:48 ` Stéphane Veyret
2019-07-05 18:07 ` Pablo Neira Ayuso [this message]
2019-06-15 13:10 ` [PATCH nftables v4 0/1] add ct expectation support Stéphane Veyret
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=20190705180749.fku5r3tnt4jzskpp@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sveyret@gmail.com \
/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).