From: Jens Schleusener <Jens.Schleusener@debis-sfr.de>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: zsh-4.0.1-pre-[45] compile problems under AIX
Date: Thu, 31 May 2001 21:03:08 +0200 (DFT) [thread overview]
Message-ID: <Pine.A41.3.96.1010531201932.83874A-100000@n05.sp.go.dlr.de> (raw)
In-Reply-To: <Tc0a88d0153dad562d3@mailsweeper01.cambridgesiliconradio.com>
On Thu, 31 May 2001, Peter Stephenson wrote:
> Jens Schleusener wrote:
> > Hi,
> >
> > I have problems to compile zsh-4.0.1-pre-4 and zsh-4.0.1-pre-5
> > under AIX 4.1.4 and 4.3.x.
> >
> > I assume the problem is a local one (local gcc installation etc.) and
> > probably I have overseen something.
>
> This could be a problem with the configure changes for termcap, so it might
> be serious. First, however, does this happen with a completely clean
> distribution? It's possible some of the attempts at fixing termcap/curses
Yes, I used a completely clean distribution.
> in the middle have confused configure.
>
> Has anybody compiled successfully under AIX with zsh-4.0.1-pre-4 or
> zsh-4.0.1-pre-5? If not, we need to fix this.
>
> > Under AIX 4.1.4 (gcc 2.95.3) I got the following error:
> >
> > ...
> > gcc -c -I. -DHAVE_CONFIG_H -I/usr/local/contrib/include -o termcap.o
> > termcap.c
> > In file included from termcap.c:61:
> > /usr/include/term.h:1315: parse error before `SGTTY'
>
> That probably means that curses.h hasn't been included. Is
> TERM_H_NEEDS_CURSES_H defined in config.h? If not we need to figure out
That was the point. TERM_H_NEEDS_CURSES_H was undefined. And the reason
seems to be an old curses.h file (63933 Bytes, Feb 14 1996 from a package
named "PDCurses") residing in a directory /usr/local/contrib/include (in
/usr/local/contrib the free software is installed on this machine).
Compiling configure's "checking if term.h needs curses.h"-test-program
with the additional line
#include <curses.h>
failes with the inappropriate curses.h also. Remains the question why the
file /usr/local/contrib/include/curses.h was used instead of the standard
AIX /usr/include/curses.h? The answer may be (I am not familiar with the
configure process) that I forced (special reasons) for the configure run
the PATH to be PATH="/usr/local/contrib/bin:$PATH". Without that or with
renaming the strange /usr/local/contrib/include/curses.h zsh configures
and compiles well!
> why not. In the generated file config.log, look for the message `checking
> if term.h needs curses.h'. You should see some failure messages for an
> attempt to compile a programme which included term.h, but not curses.h
> (just what's happening in the failed compilation above), which triggers the
> symbol being defined. It should be pretty difficult to get the compilation
> to succeed accidentally, though.
>
> Looking at termcap.c, I can't see any other way of getting that particular
> error.
Greetings
Jens
--
Dr. Jens Schleusener T-Systems debis Systemhaus
phone: +49 (551) 709-2493 Solutions for Research
fax: +49 (551) 709-2169 Bunsenstr.10
mail: Jens.Schleusener@debis-sfr.de D-37073 Goettingen
next prev parent reply other threads:[~2001-05-31 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 20:44 Jens Schleusener
2001-05-31 9:34 ` Peter Stephenson
2001-05-31 19:03 ` Jens Schleusener [this message]
2001-06-01 9:33 ` Peter Stephenson
2001-06-01 12:38 ` Jens Schleusener
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=Pine.A41.3.96.1010531201932.83874A-100000@n05.sp.go.dlr.de \
--to=jens.schleusener@debis-sfr.de \
--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).