From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Termcap saga again
Date: Tue, 8 May 2001 14:35:43 +0000 [thread overview]
Message-ID: <1010508143543.ZM29748@candle.brasslantern.com> (raw)
In-Reply-To: <Tc0a88d01536464c3f9@mailsweeper01.cambridgesiliconradio.com>
On May 8, 10:36am, Peter Stephenson wrote:
} Subject: Termcap saga again
}
} It seems HAVE_CURSES_H isn't getting defined --- it's generating warnings
} about redefined macros, is this enough to stop configure recognising it?
Is it HAVE_CURSES_H that's not defined, or is it TERM_H_NEEDS_CURSES_H ?
It's that dang GCC overoptimization again, I'll wager.
Index: configure.in
===================================================================
RCS file: /extra/cvsroot/zsh/zsh-4.0/configure.in,v
retrieving revision 1.7
diff -c -r1.7 configure.in
--- configure.in 2001/05/02 16:59:00 1.7
+++ configure.in 2001/05/08 14:33:52
@@ -566,11 +566,11 @@
if test x$ac_cv_header_term_h = xyes; then
AC_MSG_CHECKING(if term.h needs curses.h)
-AC_TRY_COMPILE([#include <term.h>], [char **test = boolcodes;], boolcodes_with_only_term_h=yes,
-boolcodes_with_only_term_h=no)
+AC_TRY_COMPILE([#include <term.h>], [char **test = boolcodes; printf(*test);],
+boolcodes_with_only_term_h=yes, boolcodes_with_only_term_h=no)
AC_TRY_COMPILE([#include <curses.h>
-#include <term.h>], [char **test = boolcodes;], boolcodes_with_curses_h_and_term_h=yes,
-boolcodes_with_curses_h_and_term_h=no)
+#include <term.h>], [char **test = boolcodes; printf(*test);],
+boolcodes_with_curses_h_and_term_h=yes, boolcodes_with_curses_h_and_term_h=no)
if test "x$boolcodes_with_curses_h_and_term_h" = xyes && test "x$boolcodes_with_only_term_h" = xno;
then
AC_DEFINE(TERM_H_NEEDS_CURSES_H)
--
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-05-08 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 9:36 Peter Stephenson
2001-05-08 13:34 ` Clint Adams
2001-05-08 14:35 ` Bart Schaefer [this message]
2001-05-08 14:56 ` Peter Stephenson
2001-05-08 15:14 ` Bart Schaefer
2001-05-08 16:23 ` Peter Stephenson
2001-05-08 18:01 ` Andrej Borsenkow
2001-05-08 18:07 ` Bart Schaefer
2001-05-08 18:25 ` Peter Stephenson
2001-05-09 5:03 ` Bart Schaefer
2001-05-09 5:19 ` Andrej Borsenkow
2001-05-09 5:32 ` PATCH: " Andrej Borsenkow
2001-05-09 5:42 ` Bart Schaefer
2001-05-09 5:37 ` PATCH (the last?) " Bart Schaefer
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=1010508143543.ZM29748@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=pws@csr.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).