From: Eli Zaretskii <eliz@gnu.org>
To: monnier@iro.umontreal.ca
Cc: alinsoar@voila.fr, dann@ics.uci.edu, emacs-devel@gnu.org,
mathias.dahl@gmail.com
Subject: Re: Cannot open termcap database
Date: Sat, 12 Dec 2009 12:00:09 +0200 [thread overview]
Message-ID: <83y6l87brq.fsf@gnu.org> (raw)
In-Reply-To: <83fx7pk2jj.fsf@gnu.org>
> Date: Sat, 05 Dec 2009 14:50:40 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: alinsoar@voila.fr, mathias.dahl@gmail.com, monnier@iro.umontreal.ca,
> emacs-devel@gnu.org
>
> > termcap.o would also need to be removed from the setting of termcapobj
> > in src/Makefile.in
> >
> > > Btw, maybe I'm blind, but configure checks only for termcap.h, it
> > > never references -ltermcap or anything else that has "termcap" as a
> > > substring. Would removing termcap.h from the script be all that is
> > > needed for Unix platforms to not use termcap.c?
> >
> > No, see above.
> > And it gets even better: termcap.h is not even used, see src/term.c and src/cm.c:
> >
> > /* For now, don't try to include termcap.h. On some systems,
> > configure finds a non-standard termcap.h that the main build
> > won't find. */
> >
> > #if defined HAVE_TERMCAP_H && 0
> > #include <termcap.h>
> > #else
>
> Right. So, taking into consideration what Andreas points out, we will
> need to:
>
> . Move termcap.o from termcapobj to MSDOS_OBJ in src/Makefile.in
>
> . Simplify src/Makefile.in under #ifndef LIBS_TERMCAP" in the
> !TERMINFO case (because both branches will become identical now)
>
> . Remove termcap.h from AC_CHECK_HEADERS in configure.in
>
> . Remove the above "#if 0" snippet from src/term.c and src/cm.c
>
> Anything else I missed?
No one commented. Should I do this now, or should I wait for the
release branch to be cut?
next prev parent reply other threads:[~2009-12-12 10:00 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y6l87brq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=alinsoar@voila.fr \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=mathias.dahl@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.