All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Bart Trojanowski <bart@jukie.net>,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: nftables: build issues
Date: Tue, 24 Mar 2009 20:02:03 +0100	[thread overview]
Message-ID: <49C92E2B.3030906@trash.net> (raw)
In-Reply-To: <20090324185711.GB2551@jukie.net>

I've CCed netfilter-devel since I assume more people will hit this.

Bart Trojanowski wrote:
> the project sounds very interesting.  I wanted to give it a try -- at
> least look at the user space for now -- but I ran into some build
> issues.
> 
> Here is what I ran:
> 
> ...
> Up to here everything works nicely, but then...
> 
>         % cd ../nftables
>         % LIBS=-L${HOME}/usr/lib CFLAGS=-I${HOME}/usr/include ./configure --prefix=${HOME}/usr
>         % make install
> 
>           SUBDIR    src/
>           LEX       src/scanner.l
>           DEP       src/scanner.c
>           YACC      src/parser.y
>         src/parser.y: fatal error: invalid @ in skeleton: @output 

I assume you're using a recent version of Debian unstable?

The nftables tree includes a copy of the bison template for debugging
purposes because there's no other way to increase the amount of expected
tokens reported during an syntax error. The current bison version used
in Debian unstable is incompatible with the old templates. I've tried
updating the template, but the bison version appears to be broken
itself and incorrectly jumps into the lexer after an EOF again, causing
a crash. For now I'd recommend to get an older version of bison to
compile nftables. 1.2.3.dfsg-4 from etch works fine for me.


       reply	other threads:[~2009-03-24 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090324185711.GB2551@jukie.net>
2009-03-24 19:02 ` Patrick McHardy [this message]
2009-03-24 19:31   ` nftables: build issues Bart Trojanowski
2009-03-24 19:35   ` Bart Trojanowski

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=49C92E2B.3030906@trash.net \
    --to=kaber@trash.net \
    --cc=bart@jukie.net \
    --cc=netfilter-devel@vger.kernel.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.