unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Mathias Dahl <mathias.dahl@gmail.com>
Cc: A Soare <alinsoar@voila.fr>, emacs-devel@gnu.org
Subject: Re: Cannot open termcap database
Date: Thu, 3 Dec 2009 13:20:03 -0800 (PST)	[thread overview]
Message-ID: <200912032120.nB3LK3MN028567@godzilla.ics.uci.edu> (raw)
In-Reply-To: <7dbe73ed0912031141h781e61d1l18776fb696cc4916@mail.gmail.com> (Mathias Dahl's message of "Thu, 3 Dec 2009 20:41:22 +0100")

Mathias Dahl <mathias.dahl@gmail.com> writes:

  > On Thu, Nov 26, 2009 at 3:11 PM, A Soare <alinsoar@voila.fr> wrote:
  > > I tried to compile emacs for console, and I got the error
  > >
  > > Cannot open termcap database
  > >
  > >
  > > I solved the problem by installing ncurses-dev.
  > >
  > > One can introduce a check in ./configure.ac for the existence of terminfo data
  > > base when compiling for console and giving a suggestive error message?
  > 
  > I get bitten by this each time I compile and install Emacs on a new
  > Ubuntu GNU/Linux machine. Each time I have to surf around to
  > understand what to do about it. If it is possible for "us" to fix it
  > it would be nice.

configure could try to detect either the termcap or terminfo headers and
if none are present should error out.  All the systems we support
nowadays that use ttys have either termcap or terminfo, so we don't lose
anything.




  reply	other threads:[~2009-12-03 21:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 14:11 Cannot open termcap database A Soare
2009-12-03 19:41 ` Mathias Dahl
2009-12-03 21:20   ` Dan Nicolaescu [this message]
2009-12-04  1:47     ` Stefan Monnier
2009-12-04  4:53       ` Dan Nicolaescu
2009-12-04 14:16         ` Stefan Monnier
2009-12-04 14:21           ` Miles Bader
2009-12-04 17:17           ` Dan Nicolaescu
2009-12-04 19:08             ` Eli Zaretskii
2009-12-04 19:24               ` Dan Nicolaescu
2009-12-04 19:33                 ` Eli Zaretskii
2009-12-04 19:46               ` Stefan Monnier
2009-12-05  9:55                 ` Eli Zaretskii
2009-12-05 10:51                   ` Andreas Schwab
2009-12-05 12:52                     ` Eli Zaretskii
2009-12-05 11:05                   ` Dan Nicolaescu
2009-12-05 12:50                     ` Eli Zaretskii
2009-12-12 10:00                       ` Eli Zaretskii
2009-12-12 15:55                         ` Chong Yidong
2009-12-12 16:30                           ` Eli Zaretskii
2010-01-28  5:22                             ` Ken Hori
2010-01-28  5:44                               ` Eli Zaretskii
2010-01-28 19:23                                 ` Stefan Monnier
2010-03-12 16:37                             ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2009-12-08  8:23 A. Soare

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200912032120.nB3LK3MN028567@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=alinsoar@voila.fr \
    --cc=emacs-devel@gnu.org \
    --cc=mathias.dahl@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).