netfilter-devel.vger.kernel.org archive mirror
 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: Re: [nft PATCH] libnftables: Split code into frontend and library
Date: Thu, 16 Nov 2017 15:11:22 +0100	[thread overview]
Message-ID: <20171116141122.GL32305@orbyte.nwl.cc> (raw)
In-Reply-To: <20171116135630.GA13559@salvia>

On Thu, Nov 16, 2017 at 02:56:30PM +0100, Pablo Neira Ayuso wrote:
> On Thu, Nov 16, 2017 at 02:34:48PM +0100, Pablo Neira Ayuso wrote:
> > On Tue, Nov 14, 2017 at 09:17:10PM +0100, Phil Sutter wrote:
> > > This finally creates the libnftables shared object.
> > > 
> > > For some reason, this causes two compiler warnings to appear:
> > > 
> > > | parser_bison.y: In function 'nft_parse':
> > > | parser_bison.y:131:3: warning: implicit declaration of function 'nft_set_debug' [-Wimplicit-function-declaration]
> > > |    nft_set_debug(1, scanner);
> > > |    ^~~~~~~~~~~~~
> > > | parser_bison.c:64:25: warning: implicit declaration of function 'nft_lex' [-Wimplicit-function-declaration]
> > > |  #define yylex           nft_lex
> > > |                          ^
> > > | parser_bison.c:4745:16: note: in expansion of macro 'yylex'
> > > |        yychar = yylex (&yylval, &yylloc, scanner);
> > > 
> > > So this patch contains a workaround, namely declaring both functions
> > > in src/parser_bison.y. During linking the objects are found, so this is
> > > rather a matter of cosmetics.
> > 
> > Also applied, thanks Phil.
> 
> This message is popping up here:
> 
>   CCLD     libnftables.la
> ar: `u' modifier ignored since `D' is the default (see `U')

Looks like an automake bug on your system? (Googling turned this up:
https://bugzilla.redhat.com/show_bug.cgi?id=1155273). I don't see the
warning on my machine at least.

Cheers, Phil
> 

      reply	other threads:[~2017-11-16 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 20:17 [nft PATCH] libnftables: Split code into frontend and library Phil Sutter
2017-11-16 13:34 ` Pablo Neira Ayuso
2017-11-16 13:56   ` Pablo Neira Ayuso
2017-11-16 14:11     ` 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=20171116141122.GL32305@orbyte.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 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).