On Wednesday, August 19, 2015 12:14:46 AM Jeremi Piotrowski wrote: > On Tue, 18 Aug 2015, Dale wrote: > > Grant Edwards wrote: > > > On 2015-08-18, Dale <rdalek1...@gmail.com> wrote: > > > I don't have any libtinfo.<whatever> on any of my systems either. By > > > default, I don't think a separate libtinfo is built. One suggestion I > > > saw for this problem (on a different distro) is to symlink libtinfo to > > > libncurses. > > Ncurses can be compiled as a single library or as two (ncurses + tinfo), > in either case all the symbols are present on the system it's just a > question of where they are located. > > Many packages are not prepared to handle the seperate tinfo library, we > have many bugs in the bugzilla that deal with tracking down such build > failures and correcting them. But this is the first I hear of anyone > having a problem with the reverse.
It could happen if the tinfo flag is removed (perhaps as an attempt to build one of the many broken packages). If the tinfo library is not preserved everything that linked against it stops working. That's one of the many problems with the current approach to this use flag (patching the multitude of broken packages). I patched my ncurses ebuild to build and install both a full ncurses along with a tinfo library, that causes the most packages to link against curses only so no rebuild is necessary after removing the use flag, everything builds ok and only binary packages use libtinfo. I posted the patch on the tinfo tracker but no one seems interested. > Symlinking libtinfo to libncurses *should* work, or atleast seems like a > valid rescue attempt. It's worth a shot, but it doesn't work for all packages. I think it depends on the linking order. PS: There's a post by wraeth on this thread, is anybody having problems opening it? kmail crashes everytime I try. -- Fernando Rodriguez
