netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robby Workman <robby@rlworkman.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] nftables 0.3 release
Date: Fri, 27 Jun 2014 12:42:36 -0500	[thread overview]
Message-ID: <20140627124236.793bc975.robby@rlworkman.net> (raw)
In-Reply-To: <20140625155210.GA31550@localhost>

On Wed, 25 Jun 2014 17:52:10 +0200
Pablo Neira Ayuso <pablo@netfilter.org> wrote:

> The Netfilter project presents:
> 
>         nftables 0.3
> 
> This release contains bug fixes, syntax cleanups, new features,
> support for all new features contained in the recent 3.15 kernel
> release.


Hi Pablo,

I get this error after configure:

  checking for readline in -lreadline... no
  configure: error: No suitable version of libreadline found

It appears that you're depending on distro-specific enhancements to
readline, specifically that Fedora explicitly links libtinfo, Arch
explicitly links ncurses, etcetera, while according to upstream
readline, this should not occur -- from INSTALL file in readline:

The readline `configure' recognizes a single `--with-PACKAGE' option:

`--with-curses'
    This tells readline that it can find the termcap library functions
    (tgetent, et al.) in the curses library, rather than a separate
    termcap library.  Readline uses the termcap functions, but does not
    link with the termcap or curses library itself, allowing applications
    which link with readline the to choose an appropriate library.
    This option tells readline to link the example programs with the
    curses library rather than libtermcap.

I think this will be useful:
https://www.gnu.org/software/autoconf-archive/ax_lib_readline.html

-RW

      reply	other threads:[~2014-06-27 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 15:52 [ANNOUNCE] nftables 0.3 release Pablo Neira Ayuso
2014-06-27 17:42 ` Robby Workman [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=20140627124236.793bc975.robby@rlworkman.net \
    --to=robby@rlworkman.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;
as well as URLs for NNTP newsgroup(s).