Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Erik Leunissen <e.leunissen@hccnet.nl>
To: Steve Eaton <seaton@novell.com>
Cc: gdb@sourceware.org
Subject: Re: gdb configure error: no termcap library found
Date: Sun, 05 Nov 2006 19:33:00 -0000	[thread overview]
Message-ID: <454E3C8D.6040707@hccnet.nl> (raw)
In-Reply-To: <454DC089.742A.00E2.0@novell.com>

Steve Eaton wrote:
> 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.
> 

That did the trick indeed.

Thanks.


For the maintainers in this mailing list: would it be wise to change the 
error message ("configure: error: no termcap library found")?

To me, the message was misleading, because:
- a termcap library actually was present
- the configure script appeared to be needing other files besides the 
library (header files, ... ).


Cheers,

Erik Leunissen


      reply	other threads:[~2006-11-05 19:33 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
2006-11-05 19:33   ` Erik Leunissen [this message]

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=454E3C8D.6040707@hccnet.nl \
    --to=e.leunissen@hccnet.nl \
    --cc=gdb@sourceware.org \
    --cc=seaton@novell.com \
    /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