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] Use config scripts to detect ncurses libs for, menuconfig/nconfig dialogs
Date: Tue, 26 Feb 2013 07:59:57 +0100 [thread overview]
Message-ID: <512C5D6D.1040509@gentoo.org> (raw)
In-Reply-To: <201302252153.39465.yann.morin.1998@free.fr>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On 25/02/13 21:53, Yann E. MORIN wrote:
> Justin, All,
>
> On Monday 25 February 2013 Justin wrote:
>> On 25.02.2013 19:30, Yann E. MORIN wrote:
>>> On Sunday 24 February 2013 Justin wrote:
>>>> when ncurses is build with --with-termlib several symbols are moved to a
>>>> seperate terminfo library (libtinfo.so). Current Kernel buildsystem
>>>> results in a build error with menuconfig and nconfig dialogs.
>>>
>>> Do you know of a distribution where this is the case, so I can test?
>>
>> This is using Gentoo Linux testing with ld.gold. But I assume you will
>> get the same result using any distro with gold.
>
> No, I meant a distro where ncurses is built with --with-termlib.
> On my Debian stable (squeeze), libtinfo does not exist at all,
> so I can not test linking against it:
>
> $ apt-file search libtinfo
> (zilch)
>
> But I'll see at installing a Gentoo (if that's not too complex) in a
> VM to do the checks (can you confirm that Gentoo by default configures
> ncurses with --with-termlib ?).
>
> Regards,
> Yann E. MORIN.
>
I can be build optionally (mostly for binary package compatibility
reasons) with --with-termlib. I will send a step-by-step instruction how
to test this with our live cd later today.
Thanks,
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-02-26 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 15:50 [PATCH] Use config scripts to detect ncurses libs for, menuconfig/nconfig dialogs Justin
2013-02-25 18:30 ` Yann E. MORIN
2013-02-25 20:32 ` Justin
2013-02-25 20:53 ` Yann E. MORIN
2013-02-26 6:59 ` justin [this message]
2013-02-27 14:30 ` justin
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=512C5D6D.1040509@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