From: Jens Schleusener <Jens.Schleusener@debis-sfr.de>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: zsh-4.0.1-pre-[45] compile problems under AIX
Date: Fri, 1 Jun 2001 14:38:48 +0200 (DFT) [thread overview]
Message-ID: <Pine.A41.3.96.1010601142940.205016A-100000@n05.sp.go.dlr.de> (raw)
In-Reply-To: <Tc0a88d0153dffb991f@mailsweeper01.cambridgesiliconradio.com>
On Fri, 1 Jun 2001, Peter Stephenson wrote:
> Jens Schleusener wrote:
> > 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).
>
> OK, I'll assume this isn't a general problem and get on with releasing it.
>
> I don't think altering PATH would make it point at
> /usr/local/contrib/include, so I can't see why it picked that up.
Sorry, that I bother you zsh-gurus, but just for completeness: I found
that the "configure"-wrapper-script I use set also
export CFLAGS="$CFLAGS -I/usr/local/contrib/include"
export LDFLAGS="$LDFLAGS -L/usr/local/contrib/lib"
so that seems to force the use of /usr/local/contrib/include/curses.h
instead of /usr/include/curses.h (I had til now the wrong (?) idea that
that line would only force an addrtional search for header files in the
given directory that aren't found in the "standard" include-directories).
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
prev parent reply other threads:[~2001-06-01 12:38 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
2001-06-01 9:33 ` Peter Stephenson
2001-06-01 12:38 ` Jens Schleusener [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=Pine.A41.3.96.1010601142940.205016A-100000@n05.sp.go.dlr.de \
--to=jens.schleusener@debis-sfr.de \
--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).