[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Handling conflicts caused by command-line editing, revisited
- From: "Vadim A. Misbakh-Soloviov" <lua-l@...>
- Date: Thu, 19 Jul 2018 20:39:18 +0300
> Any ideas?
Or you can try to talk with fbsd readline and ncurses maintainers.
For example, ncurses-6 (well, actually, even 5.9) can be built with "tinfo" as
a separate library.
So, and readline can be linked against `tinfo`, and not against whole curses
/usr/bin/lua5.3 (interpreter => /lib64/ld-linux-x86-64.so.2)
libm.so.6 => /lib64/libm.so.6
libdl.so.2 => /lib64/libdl.so.2
libreadline.so.7 => /lib64/libreadline.so.7
libtinfo.so.6 => /lib64/libtinfo.so.6
libc.so.6 => /lib64/libc.so.6
Although, here, on Gentoo, maintainers just patches readline to not use
`-lncurses`, but use `pkg-config ncurses --libs` instead (i.e. it's not native
And also, Gentoo forces '-Wl,--as-needed' in LDFLAGS, so `-lncurses` goes off
from linked library (since it's not used for anything), so it's only `-ltinfo`
stays in place.
So, you can talk with fbsd readline port maintainers to do the same, and also
with ncurses port maintainers to provide "separated tinfo" build option.