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: Final versions of ncurses libs detection patches
Date: Thu, 07 Mar 2013 10:47:15 +0100 [thread overview]
Message-ID: <51386223.3020901@gentoo.org> (raw)
In-Reply-To: <201303062223.24541.yann.morin.1998@free.fr>
[-- Attachment #1: Type: text/plain, Size: 2323 bytes --]
On 06/03/13 22:23, Yann E. MORIN wrote:
> On Ubuntu Quantal, ncurses is indeed compiled with tinfo as a separate
> lib, but these two patches are not needed, because libncurses has proper
> (NEEDED) on libtinfo:
>
> $ readelf -d /lib/x86_64-linux-gnu/libncurses.so.5.9 |grep tinfo
> 0x0000000000000001 (NEEDED) Shared library: [libtinfo.so.5]
Hi Yann,
Same here
$ scanelf -n /lib//libncurses.so.5.9
TYPE NEEDED FILE
ET_DYN libc.so.6,libdl.so.2,libtinfo.so.5 /lib//libncurses.so.5.9
But why it works on ubuntu and debian is that
/lib/lib/x86_64-linux-gnu/libncurses.so.5.9
is a ld script with following content
INPUT(libncurses.so.9 -ltinfo)
It instructs the linker at link time to add additionally -ltinfo.
On Gentoo, the base-system maintainers refuse to do this (I would agree
if you call it a bug on our side), but I am not allowed to touch those
packages.
Luckily ncurses provides the config scripts and the pkg-config modules
to do sane linking. This should be done if possible regardless the
situation on a single distributions.
>
> If I just configure ncurses with:
> $ ./configure --with-termlib --with-shared --without-normal && make
> $ readelf -d lib/libncurses.so.5.9 |grep tinfo
> 0x0000000000000001 (NEEDED) Shared library: [libtinfo.so.5]
>
> I wonder how you configured your ncurses.
./configure --prefix=/usr --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --libdir=/usr/lib64
--with-terminfo-dirs=/etc/terminfo:/usr/share/terminfo --with-shared
--without-hashed-db --without-ada --with-cxx --with-cxx-binding
--without-debug --without-profile --with-gpm --disable-termcap
--enable-symlinks --with-rcs-ids --with-manpage-format=normal
--enable-const --enable-colorfgbg --enable-echo --enable-pc-files
--enable-warnings --without-assertions --disable-leaks
--without-expanded --with-macros --without-trace --with-termlib
--with-chtype=long --with-mmask-t=long --disable-ext-colors
--disable-ext-mouse --without-pthread --without-reentrant
>
> Thanks for staying around during the iterations.
No problem, this is how it works. Thanks for your suggestions,
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-03-07 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Use config scripts to detect ncurses libs for, menuconfig/nconfig dialogs>
2013-03-06 13:02 ` Final versions of ncurses libs detection patches jlec
2013-03-06 13:02 ` [PATCH 1/2] menuconfig: optionally use pkg-config to detect ncurses libs jlec
2013-03-06 13:02 ` [PATCH 2/2] kconfig: " jlec
2013-03-06 20:47 ` Yann E. MORIN
2013-03-06 21:23 ` Final versions of ncurses libs detection patches Yann E. MORIN
2013-03-07 9:47 ` justin [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=51386223.3020901@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