From: Paul Bolle <pebolle@tiscali.nl>
To: sylvain.bertrand@gmail.com
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: add tinfo library if it exists to lxdialog linking flags
Date: Tue, 28 Apr 2015 10:19:27 +0200 [thread overview]
Message-ID: <1430209167.2411.41.camel@x220> (raw)
In-Reply-To: <20150427120019.GA567@freedom>
On Mon, 2015-04-27 at 12:00 +0000, sylvain.bertrand@gmail.com wrote:
> The pkg-config file I use is straight from the ncurses distribution with the
> lastest "rollup" patch.
>
> Either it's a fedora specific modification, either a genuine ncurses patch
> released after the lastest "rollup" patch.
(If I read ftp://invisible-island.net/ncurses/5.9/README correctly, a
rollup is the patch that should be applied on top of the latest ncurses
release in order to get a development snapshot.)
What version of ncurses are you actually using?
> As far I understand it, from an application point of view, "standard" ncurses
> programming, in the case where tinfo lib is outside of ncurses lib, involves
> linking to libncurses library only. libtinfo linking would be required only in
> some special features are used, which seems to be the case with lxdialog.
On my Fedora 20 box linking to libtinfo is only necessary if you're
linking an application that's using libncurses statically.
> Please correct me if I'm wrong.
I have no idea.
Perhaps - and I'm speculating here - some features got moved from
ncurses(w) to tinfo. Anyhow, over here linking to tinfo is unneeded but
doesn't break mconf as far as I noticed. But, personally, I'd like to
know what triggered the issue you ran into before considering this
patch.
Paul Bolle
next prev parent reply other threads:[~2015-04-28 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 16:05 [PATCH] kconfig: add tinfo library if it exists to lxdialog linking flags sylvain.bertrand
2015-04-26 21:19 ` Paul Bolle
2015-04-27 12:00 ` sylvain.bertrand
2015-04-28 8:19 ` Paul Bolle [this message]
2015-04-29 15:20 ` sylvain.bertrand
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=1430209167.2411.41.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvain.bertrand@gmail.com \
/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).