From: Albert Chin <zsh-workers@lists.thewrittenword.com>
To: zsh-workers@sunsite.dk
Subject: Re: Compile errors for zsh 4.0.4 on Aix 4.3.3
Date: Fri, 10 May 2002 18:01:38 -0500 [thread overview]
Message-ID: <20020510180138.A61520@oolong.il.thewrittenword.com> (raw)
In-Reply-To: <1020509150823.ZM8499@candle.brasslantern.com>; from schaefer@brasslantern.com on Thu, May 09, 2002 at 03:08:23PM +0000
On Thu, May 09, 2002 at 03:08:23PM +0000, Bart Schaefer wrote:
> On May 9, 9:08am, travis@jedi.net wrote:
> } "termcap.c", line 71.13: 1506-334 (S) Identifier boolcodes has already been defined on line 1342 of "/usr/include/term.h".
>
> is happening *because* "Zsh now defaults to termcap on AIX;" the problem
> about which we want more information is "variables boolcodes and some other
> are declared in term.h but missing is libcurses.a."
>
> It's a bit confusing that your build actually included term.h even though
> it was supposedly defaulting to termcap, so that might still be worth
> looking into, but it's not the problem Etc/MACHINES is talking about.
The patch below worked for us with 4.0.4 and AIX 4.3.2.
--
albert chin (china@thewrittenword.com)
-- snip snip
--- Src/Modules/termcap.c.orig Sat Nov 10 13:26:59 2001
+++ Src/Modules/termcap.c Sat Nov 10 13:27:53 2001
@@ -67,20 +67,20 @@
static Param termcap_pm;
-#ifndef HAVE_BOOLCODES
-static char *boolcodes[] = {
- "bw", "am", "ut", "cc", "xs", "YA", "YF", "YB", "xt", "xn", "eo",
- "gn", "hc", "HC", "km", "YC", "hs", "hl", "in", "YG", "da", "db",
- "mi", "ms", "nx", "xb", "NP", "ND", "NR", "os", "5i", "YD", "YE",
- "es", "hz", "ul", "xo", NULL};
-#endif
-
/**/
static int
ztgetflag(char *s)
{
char **b;
+#ifndef HAVE_BOOLCODES
+ static char *boolcodes[] = {
+ "bw", "am", "ut", "cc", "xs", "YA", "YF", "YB", "xt", "xn", "eo",
+ "gn", "hc", "HC", "km", "YC", "hs", "hl", "in", "YG", "da", "db",
+ "mi", "ms", "nx", "xb", "NP", "ND", "NR", "os", "5i", "YD", "YE",
+ "es", "hz", "ul", "xo", NULL};
+#endif
+
/* ncurses can tell if an existing boolean capability is *
* off, but other curses variants can't, so we fudge it. *
* This feature of ncurses appears to have gone away as *
@@ -295,6 +295,14 @@
"NC", "Nl", "pb", "vt", "ws", "Yo", "Yp", "Ya", "BT", "Yc", "Yb",
"Yd", "Ye", "Yf", "Yg", "Yh", "Yi", "Yk", "Yj", "Yl", "Ym", "Yn",
NULL};
+#endif
+
+#ifndef HAVE_BOOLCODES
+ static char *boolcodes[] = {
+ "bw", "am", "ut", "cc", "xs", "YA", "YF", "YB", "xt", "xn", "eo",
+ "gn", "hc", "HC", "km", "YC", "hs", "hl", "in", "YG", "da", "db",
+ "mi", "ms", "nx", "xb", "NP", "ND", "NR", "os", "5i", "YD", "YE",
+ "es", "hz", "ul", "xo", NULL};
#endif
#ifndef HAVE_STRCODES
prev parent reply other threads:[~2002-05-10 23:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 14:08 travis
2002-05-09 15:03 ` Bart Schaefer
2002-05-09 15:05 ` Borsenkow Andrej
2002-05-09 15:31 ` Borsenkow Andrej
2002-05-09 15:45 ` Borsenkow Andrej
2002-05-09 15:56 ` Bart Schaefer
2002-05-09 15:08 ` Bart Schaefer
2002-05-09 15:17 ` Borsenkow Andrej
2002-05-10 23:01 ` Albert Chin [this message]
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=20020510180138.A61520@oolong.il.thewrittenword.com \
--to=zsh-workers@lists.thewrittenword.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).