From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Fernando Fernandez Mancera <ffmancera@riseup.net>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft v3 1/2] jump: Introduce chain_expr in jump and goto statements
Date: Fri, 24 May 2019 12:29:50 +0200 [thread overview]
Message-ID: <20190524102950.GH17768@orbyte.nwl.cc> (raw)
In-Reply-To: <20190524092148.wagryvqpj3l64hge@salvia>
Hi,
On Fri, May 24, 2019 at 11:21:48AM +0200, Pablo Neira Ayuso wrote:
> On Fri, May 24, 2019 at 09:29:34AM +0200, Fernando Fernandez Mancera wrote:
> > On 5/24/19 9:17 AM, Fernando Fernandez Mancera wrote:
> > > Hi Pablo,
> > >
> > > On 5/21/19 9:38 PM, Fernando Fernandez Mancera wrote:
> > >> Hi Pablo,
> > >>
> > >> On 5/21/19 11:28 AM, Pablo Neira Ayuso wrote:
> > >>> On Thu, May 16, 2019 at 10:45:58PM +0200, Fernando Fernandez Mancera wrote:
> > >>>> Now we can introduce expressions as a chain in jump and goto statements. This
> > >>>> is going to be used to support variables as a chain in the following patches.
> > >>>
> > >>> Something is wrong with json:
> > >>>
> > >>> json.c: In function ‘verdict_expr_json’:
> > >>> json.c:683:11: warning: assignment from incompatible pointer type
> > >>> [-Wincompatible-pointer-types]
> > >>> chain = expr->chain;
> > >>> ^
> > >>> parser_json.c: In function ‘json_parse_verdict_expr’:
> > >>> parser_json.c:1086:8: warning: passing argument 3 of
> > >>> ‘verdict_expr_alloc’ from incompatible pointer type
> > >>> [-Wincompatible-pointer-types]
> > >>> chain ? xstrdup(chain) : NULL);
> > >>> ^~~~~
> > >>>
> > >>> Most likely --enable-json missing there.
> > >>>
> > >>
> > >> Sorry, I am going to fix that.
> > >> [...]
> > >
> > > I am compiling nftables with:
> > >
> > > $ ./configure --enable-json
> > > $ make
> > >
> > > And I am not getting any error, am I missing something? Thanks! :-)
> > >
> >
> > Fixed, the option is --with-json. Why isn't it "--enable-json" as other
> > features?
It is actually not that uniform. While we have:
--enable-debug
--enable-man-doc
--enable-python
we also have:
--with-mini-gmp
--with-cli
--with-xtables
--with-json
and all of them just enable/disable something, unlike --with-python-bin.
> We can just update this to accept both, either --with-json or
> --enable-json.
For consistency, we should turn all of the above --with flags into
--enable ones, but there's of course the compatibility problem.
What do you think, is it feasible to change all the above and introduce
--with aliases for them?
Cheers, Phil
prev parent reply other threads:[~2019-05-24 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 20:45 [PATCH nft v3 1/2] jump: Introduce chain_expr in jump and goto statements Fernando Fernandez Mancera
2019-05-16 20:45 ` [PATCH nft v3 2/2] jump: Allow goto and jump to a variable using nft input files Fernando Fernandez Mancera
2019-05-21 9:28 ` [PATCH nft v3 1/2] jump: Introduce chain_expr in jump and goto statements Pablo Neira Ayuso
2019-05-21 19:38 ` Fernando Fernandez Mancera
2019-05-21 19:42 ` Pablo Neira Ayuso
2019-05-24 7:17 ` Fernando Fernandez Mancera
2019-05-24 7:29 ` Fernando Fernandez Mancera
2019-05-24 9:21 ` Pablo Neira Ayuso
2019-05-24 10:29 ` Phil Sutter [this message]
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=20190524102950.GH17768@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=ffmancera@riseup.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox