All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH v2 0/2] parser_bison: Get rid of (most) bison compiler warnings
Date: Tue, 30 Jul 2019 16:18:45 +0200	[thread overview]
Message-ID: <20190730141845.exhy3tshlbdjnknj@salvia> (raw)
In-Reply-To: <20190730140354.GO14469@orbyte.nwl.cc>

On Tue, Jul 30, 2019 at 04:03:54PM +0200, Phil Sutter wrote:
> Hi Pablo,
> 
> On Tue, Jul 30, 2019 at 02:41:06PM +0200, Pablo Neira Ayuso wrote:
> > On Tue, Jul 23, 2019 at 03:23:11PM +0200, Phil Sutter wrote:
> > > Eliminate as many bison warnings emitted since bison-3.3 as possible.
> > > Sadly getting bison, flex and automake right is full of pitfalls so on
> > > one hand this series does not fix for deprecated %name-prefix statement
> > > and on the other passes -Wno-yacc to bison to not complain about POSIX
> > > incompatibilities although automake causes to run bison in POSIX compat
> > > mode in the first place. Fixing either of those turned out to be
> > > non-trivial.
> > 
> > Indeed, lots of warnings and things to be updated.
> > 
> > Do you think it's worth fixing those in the midterm?
> > 
> > We can just place these two small ones in the tree, I'm just concerned
> > about tech debt in the midterm, these deprecated stuff might just go
> > away.
> 
> We should avoid calling bison with -y since the parser simply isn't
> POSIX yacc compatible. I found a trick somewhere in WWW to do that (one
> has to substitute AC_PROG_YACC) but lost the reference again. But after
> doing so, there was a problem with file names I failed to resolve.
> Hence why I resorted to just passing -Wno-yacc.

Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>

If parser does not break with this and tests pass fine, I'm ok with
this temporary solution. I also need all most warnings go away here by
now.

Please, if you find that reference again share it with me.

Thanks.

  reply	other threads:[~2019-07-30 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 13:23 [nft PATCH v2 0/2] parser_bison: Get rid of (most) bison compiler warnings Phil Sutter
2019-07-23 13:23 ` [nft PATCH v2 1/2] parser_bison: Fix for deprecated statements Phil Sutter
2019-07-23 13:23 ` [nft PATCH v2 2/2] src: Call bison with -Wno-yacc to silence warnings Phil Sutter
2019-07-30 12:41 ` [nft PATCH v2 0/2] parser_bison: Get rid of (most) bison compiler warnings Pablo Neira Ayuso
2019-07-30 14:03   ` Phil Sutter
2019-07-30 14:18     ` Pablo Neira Ayuso [this message]
2019-09-26 10:40       ` Phil Sutter

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=20190730141845.exhy3tshlbdjnknj@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=phil@nwl.cc \
    /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.