From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Robby Workman <robby@rlworkman.net>
Cc: netfilter-devel@vger.kernel.org
Subject: libreadline not found by configure [was Re: [ANNOUNCE] nftables 0.3
Date: Mon, 30 Jun 2014 13:22:19 +0200 [thread overview]
Message-ID: <20140630112219.GA8205@localhost> (raw)
release]
Reply-To:
In-Reply-To: <20140627124236.793bc975.robby@rlworkman.net>
Hi Robby,
On Fri, Jun 27, 2014 at 12:42:36PM -0500, Robby Workman wrote:
> 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
Thanks for the detailed report.
Would you send us a patch that you can test in your fedora setup? I
would appreciate it. Thanks.
next reply other threads:[~2014-06-30 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 11:22 Pablo Neira Ayuso [this message]
2014-07-01 1:40 ` libreadline not found by configure [was Re: [ANNOUNCE] nftables 0.3 Robby Workman
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=20140630112219.GA8205@localhost \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=robby@rlworkman.net \
/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.