From: Dan Nicolaescu <dann@ics.uci.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: alinsoar@voila.fr, mathias.dahl@gmail.com,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Cannot open termcap database
Date: Sat, 5 Dec 2009 03:05:03 -0800 (PST) [thread overview]
Message-ID: <200912051105.nB5B53wL016307@godzilla.ics.uci.edu> (raw)
In-Reply-To: <83iqclkana.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 05 Dec 2009 11:55:37 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Cc: Dan Nicolaescu <dann@ics.uci.edu>, alinsoar@voila.fr, emacs-devel@gnu.org, mathias.dahl@gmail.com
> > Date: Fri, 04 Dec 2009 14:46:23 -0500
> >
> > > MSDOS needs it. I could move all the code it needs to msdos.c, if
> > > that's what people want, but it sounds easier to leave termcap.c in
> > > place and just move termcap.o to MSDOS_OBJ in src/Makefile.in. Then
> > > no other platform will link it in.
> >
> > Moving the code is not a good idea. If it's still in use, then we may
> > as well keep it as is. So we should simply change the configure script
> > so that it never uses it except under MSDOS, or upon some other
> > explicit request.
>
> The MSDOS build does not use the configure script, it uses its own
> config.bat, and relies on src/Makefile.in to mention DOS-specific
> files in MSDOS_OBJ. So if the configure script is modified to never
> use termcap.c and termcap.o is added to MSDOS_OBJ, I think the effect
> is what you suggest above.
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
next prev parent reply other threads:[~2009-12-05 11:05 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 [this message]
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=200912051105.nB5B53wL016307@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=alinsoar@voila.fr \
--cc=eliz@gnu.org \
--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 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).