zsh-users
 help / color / mirror / code / Atom feed
From: Josh Wasserstein <ribonucleico@gmail.com>
To: Philippe Troin <phil@fifi.org>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Building Zsh: No terminal handling library found - But I installed ncourses
Date: Mon, 7 Apr 2014 16:25:04 -0400	[thread overview]
Message-ID: <CAD4ivxWJo9fddYZAmpYJM+eA6PgyizFSnZFhvvGw=mw8AapqFw@mail.gmail.com> (raw)
In-Reply-To: <1396897619.1172.14.camel@air.home.fifi.org>

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

Thanks Philippe. I fixed that so that CFLAGS points to the include folder
(I tried both the parent folder and the folder with the headers). Still no
luck ...

Josh


On Mon, Apr 7, 2014 at 3:06 PM, Philippe Troin <phil@fifi.org> wrote:

> On Mon, 2014-04-07 at 14:43 -0400, Josh Wasserstein wrote:
> > Since I am not root on this system, I downloaded ncurses and installed it
> > manually (also using ./configure --prefix=<my_installation_path>), which
> > seems to have gone well.
> >
> > I then updated the following paths:
> >
> > INSTALLATION_PATH='/path/to/installation'
> > export PATH=$INSTALLATION_PATH/bin/:$PATH
> > export LD_LIBRARY_PATH=$INSTALLATION_PATH/lib:$LD_LIBRARY_PATH
> > export CFLAGS=-I$INSTALLATION_PATH/lib
>                 ^^^^^^^^^^^^^^^^^^^^^^^
> Shouldn't that be:
> export CFLAGS=-I$INSTALLATION_PATH/include
>
> > and tried installing Zsh again, but got the same ncurses error. As far
> as I
> > can tell, the path variables above point to the right locations, and I
> can
> > check this on the shell.
>
> You may need to re-run the configure step after changing the environment
> variables, otherwise the changes may not be picked up.
>
> Phil.
>
>

  reply	other threads:[~2014-04-07 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 18:43 Josh Wasserstein
2014-04-07 19:06 ` Philippe Troin
2014-04-07 20:25   ` Josh Wasserstein [this message]
2014-04-08  8:53     ` Peter Stephenson

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='CAD4ivxWJo9fddYZAmpYJM+eA6PgyizFSnZFhvvGw=mw8AapqFw@mail.gmail.com' \
    --to=ribonucleico@gmail.com \
    --cc=phil@fifi.org \
    --cc=zsh-users@zsh.org \
    /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).