> Hello,
>
> On Debian there is no libtermcap.so, on Redhat-4.2 there is one. As far
> as I remember libtermcap is obsolete and should be replaced by
> libncurses.
libncurses is really another way of doing buisness altogether. The
replacement for libtermcap is libte
Will Lowe <[EMAIL PROTECTED]> writes:
> I'm trying to recompile the clisp package, which installs and
> compiles it's own gnu readline library. The display routines are
> having problems locating functions such as "tputs", which the
> comments in the source code indicate should come from the loca
I'm trying to recompile the clisp package, which installs and compiles
it's own gnu readline library. The display routines are having problems
locating functions such as "tputs", which the comments in the source code
indicate should come from the locate termcap library. I'm using the most
curre
On Sep 12, Peter Weiss wrote
>On Debian there is no libtermcap.so, on Redhat-4.2 there is one. As far
>as I remember libtermcap is obsolete and should be replaced by
>libncurses.
>Am I wrong?
No.
>Has any body more Information?
Yes.
>The problem occurred when installing som
Hello,
On Debian there is no libtermcap.so, on Redhat-4.2 there is one. As far
as I remember libtermcap is obsolete and should be replaced by
libncurses.
Am I wrong? Has any body more Information?
The problem occurred when installing some foreign binaries build on a
On Tue, 31 Dec 1996, Carnage wrote:
> Hello Mailing List!,
>
> I seem to be having a problem linking with the Termcap library
> when specifying "-ltermcap" on the gcc command line.
I would recommend that you change to ncurses ("-lncurses") which will move
you into a maintained library. (te
library
> when specifying "-ltermcap" on the gcc command line.
>
> Explicitly specifying libtermcap works fine (i.e. "gcc -o program
> program.o module1.o /lib/libtermcap.so.2.0.8"). But doing a "-ltermcap"
> results in ld saying that it can't op
Hello Mailing List!,
I seem to be having a problem linking with the Termcap library
when specifying "-ltermcap" on the gcc command line.
Explicitly specifying libtermcap works fine (i.e. "gcc -o program
program.o module1.o /lib/libtermcap.so.2.0.8"). Bu
> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> > Would there be in simple reason, why the binary works in RedHat, but not
> > in Debian?
>
> If you have upgraded libc to 5.4.7, try this:
>
> LD_PRELOAD=/usr/lib/libgnumalloc.so.5
> export LD_PRELOAD
>
> or if you use csh or tcsh:
>
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Would there be in simple reason, why the binary works in RedHat, but not
> in Debian?
If you have upgraded libc to 5.4.7, try this:
LD_PRELOAD=/usr/lib/libgnumalloc.so.5
export LD_PRELOAD
or if you use csh or tcsh:
setenv L
close(9)= 0
write(2, "Got unusable memory address 0x40"..., 39Got unusable memory address
0x400cd008
) = 39
_exit(1)
End of strace.
I would guess, this has something to do with different ELF-binaries, but
anyone really knowing or guessing ?
An other thing, the lib
I recompiled emacs 19.30 on my debian 1.1 system so it would be elf.
It complained that it needed libtermcap, so I did the trick of linking
libtermcap to libncurses (libtermcap.so -> libncurses.so.3.0 in /lib).
It linked and runs OK under X, but in the console (with TERM=vt100 and
TERM=li
Hi,
after I installed 1.1 I noticed that /etc/termcap and the termcap libs are
missing. Is this on purpose or an oversight?
Should all programs now use ncurses/terminfo?
--
Cheerio, Jan
Jan Wender - [EMAIL PROTECTED] - Universitaet Trier, Germany
The man who letterspaces lowercase letters also stea
On Sat, 18 May 1996, Jan Wender wrote:
> after I installed 1.1 I noticed that /etc/termcap and the termcap libs are
> missing. Is this on purpose or an oversight?
On purpose.
> Should all programs now use ncurses/terminfo?
Yes.
In case you have nondebian binaries, termcap compatibility lib wil
14 matches
Mail list logo
