[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cannot open termcap database

From: Dan Nicolaescu
Subject: Re: Cannot open termcap database
Date: Sat, 5 Dec 2009 03:05:03 -0800 (PST)

Eli Zaretskii <address@hidden> writes:

  > > From: Stefan Monnier <address@hidden>
  > > Cc: Dan Nicolaescu <address@hidden>,  address@hidden,  address@hidden,  
  > > 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 

/* 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>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]