From: Nir Tzachar <nir.tzachar@gmail.com>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: new kbuild maintainer
Date: Thu, 10 Dec 2009 14:04:23 +0200 [thread overview]
Message-ID: <9b2db90b0912100404s5e97d9ddk181aed1990e36208@mail.gmail.com> (raw)
In-Reply-To: <200912090728.10135.a.miskiewicz@gmail.com>
>
> On my disto it works but it won't on a distro where /usr/include/ncurses
> contains wide version of headers.
ncurses does not support a proper pkg-config scheme, hence the
difficulty with finding the correct flags. Regarding the wideness of
the library, I would presume that any distro which mismatches
/usr/include/ncurses.h and libncurses.so is in itself broken. Taking
this into consideration, I think that including /usr/include/ncurses.h
and linking against -lncurses should work. We should entirely ignore
the wide version of the library, and use the default installation
provided.
>
>>
>> Moreover, currently nconfig does not use this check.
>
> I was testing on linus git and this flags from this check were used in nconfig
> build, too (that's why there were ncurses and ncursesw at the same time in
> linking command).
Well, I do not know why, by the check changed the flags for _all_
targets in the scripts/kconfig dir, such that even qconfig got copiled
with -lncursesw. Strange. The change I made in the Makefile in the
previous mail fixes that.
Cheers,
Nir.
prev parent reply other threads:[~2009-12-10 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 12:52 Michal Marek
2009-12-08 13:18 ` Sam Ravnborg
2009-12-08 15:11 ` Arkadiusz Miskiewicz
2009-12-08 19:56 ` Michal Marek
2009-12-08 20:07 ` Arkadiusz Miskiewicz
2009-12-08 20:24 ` Michal Marek
2009-12-08 20:31 ` Arkadiusz Miskiewicz
2009-12-09 6:22 ` Nir Tzachar
2009-12-09 6:28 ` Arkadiusz Miskiewicz
2009-12-10 12:04 ` Nir Tzachar [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=9b2db90b0912100404s5e97d9ddk181aed1990e36208@mail.gmail.com \
--to=nir.tzachar@gmail.com \
--cc=a.miskiewicz@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®