From: Justin <jlec@gentoo.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] menuconfig: use config scripts to detect ncurses libs
Date: Sun, 03 Mar 2013 22:20:44 +0100 [thread overview]
Message-ID: <5133BEAC.8040304@gentoo.org> (raw)
In-Reply-To: <201303032136.27096.yann.morin.1998@free.fr>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On 03.03.2013 21:36, Yann E. MORIN wrote:
Hello,
>
> In the light of the different mails on the subject, it appears that the
> ncurses*-config script are unreliable: at least one major distribution
> (Debian) is broken and, for various reasons, is not gonna fix it, and
> all its derivatives (eg. Ubuntu) do suffer from the same deficiency.
Indeed the config scripts come without the necessary build time deps.
But it ends in the same situation as current version of the Makefile.
The user will be asked to install the devel package.
So I don't see any problem here.
>
> I think we should stick to:
> - try with pkg-config;
> - fallback to the legacy heuristic.
>
> Does using pkg-config fix your use-case?
It does, nevertheless I would prefer to include the ncurses*-config
script as well to cover most situation we will find on users system.
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-03-03 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 15:50 ncurses detection for nconfig/menuconfig patches revised jlec
2013-03-01 15:50 ` [PATCH 1/2] menuconfig: use config scripts to detect ncurses libs jlec
2013-03-03 20:36 ` Yann E. MORIN
2013-03-03 21:20 ` Justin [this message]
2013-03-01 15:50 ` [PATCH 2/2] kconfig: " jlec
2013-03-03 20:38 ` Yann E. MORIN
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=5133BEAC.8040304@gentoo.org \
--to=jlec@gentoo.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/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