From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Vin Shelton <shelton@icd.teradyne.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: Make Failure on SunOS-4.1
Date: Thu, 26 Apr 2001 04:27:51 +0000 [thread overview]
Message-ID: <1010426042751.ZM11961@candle.brasslantern.com> (raw)
In-Reply-To: <545itjsx3ec.fsf@icd.teradyne.com>
On Apr 25, 2:03pm, Vin Shelton wrote:
} Subject: Re: Make Failure on SunOS-4.1
}
} OK. I found a little time to investigate further. This is truly
} ugly.
}
} 'DO' conflicts with the 'DO' token from zsh.h. I guess curses.h
} predates any kind of useful namespace standard.
Ah, distant memory begins to return ... try the following patch (against
current CVS); if this works, the only configure.in issue we need to deal
with is the question of which (if either) of tigetstr or setupterm to pass
to a call to AC_SEARCH_LIBS.
diff -u -x CVS zsh-forge/current/Src/Modules/termcap.c zsh-4.0/Src/Modules/termcap.c
--- zsh-forge/current/Src/Modules/termcap.c Mon Apr 23 23:43:27 2001
+++ zsh-4.0/Src/Modules/termcap.c Wed Apr 25 21:24:42 2001
@@ -27,36 +27,36 @@
*
*/
-#define USES_TERMCAP_H 1
-#define USES_TERM_H 1
+#ifdef HAVE_TGETENT
+# if defined(HAVE_CURSES_H) && defined(HAVE_TERM_H)
+# define USES_TERM_H 1
+# else
+# ifdef HAVE_TERMCAP_H
+# define USES_TERMCAP_H 1
+# endif
+# endif
+
#include "termcap.mdh"
#include "termcap.pro"
static char termcap_nam[] = "termcap";
-/* echotc: output a termcap */
-
#ifdef HAVE_TGETENT
-# if defined(HAVE_CURSES_H) && defined(HAVE_TERM_H)
+# ifdef USES_TERM_H
# ifdef HAVE_TERMIO_H
# include <termio.h>
# endif
# include <curses.h>
# include <term.h>
# else
-# ifdef HAVE_TERMCAP_H
+# ifdef USES_TERMCAP_H
# include <termcap.h>
-# else
-# ifdef HAVE_CURSES_H
-# include <curses.h>
-# endif
-# ifdef HAVE_TERM_H
-# include <term.h>
-# endif
# endif
# endif
static Param termcap_pm;
+
+/* echotc: output a termcap */
/**/
static int
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-04-26 4:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 19:43 Vin Shelton
2001-04-25 4:13 ` Bart Schaefer
2001-04-25 9:55 ` Peter Stephenson
2001-04-25 14:41 ` Bart Schaefer
2001-04-25 14:57 ` Clint Adams
2001-04-25 14:29 ` Vin Shelton
2001-04-25 14:58 ` Bart Schaefer
2001-04-25 18:03 ` Vin Shelton
2001-04-26 4:27 ` Bart Schaefer [this message]
2001-04-26 4:35 ` Make Failure on SunOS-4.1 (correction) Bart Schaefer
2001-04-26 12:50 ` Vin Shelton
2001-04-26 13:06 ` Or on ReliantUNIX ... " Andrej Borsenkow
2001-04-26 13:15 ` Clint Adams
2001-04-26 13:25 ` Andrej Borsenkow
2001-04-26 13:30 ` Clint Adams
2001-04-26 14:02 ` Andrej Borsenkow
2001-04-26 14:20 ` Clint Adams
2001-04-26 14:35 ` Bart Schaefer
2001-04-26 14:52 ` Andrej Borsenkow
2001-04-26 14:58 ` Clint Adams
2001-04-26 15:32 ` Bart Schaefer
2001-04-26 15:52 ` Clint Adams
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=1010426042751.ZM11961@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=shelton@icd.teradyne.com \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).