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: Sun, 26 Apr 2015 23:19:08 +0200 [thread overview]
Message-ID: <1430083148.2411.15.camel@x220> (raw)
In-Reply-To: <20150425160546.GA4002@freedom>
On Sat, 2015-04-25 at 16:05 +0000, sylvain.bertrand@gmail.com wrote:
> HOSTLD scripts/kconfig/mconf
> /bin/ld: scripts/kconfig/lxdialog/checklist.o: undefined reference to symbol 'acs_map'
>
> Add tinfo library to lxdiablog linking flags, if it exists.
>
> Signed-off-by: Sylvain BERTRAND <sylvain.bertrand@gmail.com>
> ---
> --- a/scripts/kconfig/lxdialog/check-lxdialog.sh
> +++ b/scripts/kconfig/lxdialog/check-lxdialog.sh
> @@ -4,6 +4,9 @@
> # What library to link
> ldflags()
> {
> + # Some ncurses symbols are in tinfo library, if it exists
> + pkg-config --libs tinfow 2>/dev/null
> + pkg-config --libs tinfo 2>/dev/null
> pkg-config --libs ncursesw 2>/dev/null && exit
> pkg-config --libs ncurses 2>/dev/null && exit
> for ext in so a dll.a dylib ; do
It looks like commit fc9c6e000f62 ("menuconfig: optionally use
pkg-config to detect ncurses libs") claims to already fix this. And your
patch is obviously done on top of that commit.
So I did some further, well, research. That is: I skimmed man pkg-config
and stared a bit at the pkg-config related files shipped with
ncurses-devel (for Fedora 20). And to me it seems
pkg-config --libs ncursesw
or
pkg-config --libs ncurses
should already add -ltinfow or -ltinfo if those flags would be needed,
just like that commit implies.
Is that how pkg-config should work? If so, I wonder why it fails for
you.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-04-26 21: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 [this message]
2015-04-27 12:00 ` sylvain.bertrand
2015-04-28 8:19 ` Paul Bolle
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=1430083148.2411.15.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