All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [nft PATCH v2 0/2] parser_bison: Get rid of (most) bison compiler warnings
Date: Tue, 23 Jul 2019 15:23:11 +0200	[thread overview]
Message-ID: <20190723132313.13238-1-phil@nwl.cc> (raw)

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.

Changes since v1:
- Drop nfnl_osf patch, Fernando took care of that already.
- Split remaining patch in two.
- Document which warnings are being silenced.

Phil Sutter (2):
  parser_bison: Fix for deprecated statements
  src: Call bison with -Wno-yacc to silence warnings

 src/Makefile.am    | 2 +-
 src/parser_bison.y | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.22.0


             reply	other threads:[~2019-07-23 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 13:23 Phil Sutter [this message]
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
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=20190723132313.13238-1-phil@nwl.cc \
    --to=phil@nwl.cc \
    --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.