From: "Steve Eaton" <seaton@novell.com>
To: "Erik Leunissen" <e.leunissen@hccnet.nl>,<gdb@sourceware.org>
Subject: Re: gdb configure error: no termcap library found
Date: Sun, 05 Nov 2006 17:44:00 -0000 [thread overview]
Message-ID: <454DC089.742A.00E2.0@novell.com> (raw)
In-Reply-To: <454E1C58.6020406@hccnet.nl>
I had something similar a while back. I actually had termcap available and still got errors. Seems to me I did something simple like adding the ncurses-devel.
Steve
>>> Erik Leunissen <e.leunissen@hccnet.nl> 11/05/06 10:16 AM >>>
When compiling the gdb-6.4 source package, the build comes to a halt
when the ./configure script in the gdb directory is run:
configure: error: no termcap library found
I have trouble to make this error message correspond with the actual
output of the following command:
> locate *libncurses.so*
/lib/libncurses.so.5
/lib/libncurses.so.5.3
/usr/lib/libncurses.so.1.9.7a
/usr/lib/libncurses.so.2.1
/usr/lib/libncurses.so.4
/usr/lib/libncurses.so.4.2
Can somebody please help me find out what's wrong?
Thanks in advance,
Erik Leunissen
next prev parent reply other threads:[~2006-11-05 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 17:16 Erik Leunissen
2006-11-05 17:44 ` Steve Eaton [this message]
2006-11-05 19:33 ` Erik Leunissen
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=454DC089.742A.00E2.0@novell.com \
--to=seaton@novell.com \
--cc=e.leunissen@hccnet.nl \
--cc=gdb@sourceware.org \
/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