this is on host i installed binary xterm package:
# epm -q xterm
xterm: error while loading shared libraries: libtermcap.so.2: cannot open shared object file: No such file or directory
and this is on host where i actually built the xterm package:
# epm -qa|grep termcap
i don't know how this termcap-compat got into my system. and as the xterm will compile *fine* without termcap-compat package, there could be perhaps use flag to enable/disable linking with libtermcap.
Steps to Reproduce:
1. emerge libtermcap-compat
2. FEATURES=buildpkg emerge xterm
3. emerge -C libtermcap-compat
4. emerge -k xterm
Try running revdep-rebuild (or alternatively, emerge xterm without the -k
option) and see if you still have problems running xterm.
i can not compile there. and i don't want to compile there :)
the problem i was able to resolve by uninstalling the libtermcap on compile host, then it produced xterm without libtermcap linkage.
would it be advisable to distribute our xterm without --enable-tcap-query and linking against termcap and instead to ncurses?
The only advantage of linking with libtermcap is if one had
some old application that uses termcap and needed to have its
screen size specified in the $TERMCAP file. (Also the backspace
setting, but I'm not aware of anything that uses that feature).
The tcap-query feature would work with ncurses (and I have been
told that vim uses this feature).
Thomas, in that case, I don't suppose a request for a configure flag switch for termcap vs. ncurses would be out of order, would it?
That might be easiest rather than patching it out?
I suppose so (no one's asked for it, but adding it would not be
hard, and patching it would be ugly ;-)
punting to Donnie and the gang, while I'm on LOA for 45-90 days.
Any dev interested in picking up maintenance for xterm and related sundry (utempter)?
I'm adding a --disable-full-tgetent option in xterm patch #198
to address the choice between ncurses and termcap libraries.
Added xterm-199, which fixes this. Thanks Thomas.