From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: make check problem
Date: Thu, 22 Jan 2015 08:00:46 -0800 [thread overview]
Message-ID: <54C11EAE.6000904@eastlink.ca> (raw)
In-Reply-To: <CAECNH1QOKDv+BrYhYqgTTNHAG0APGtRiWHE-MrUwwOunxVWCZA@mail.gmail.com>
On 01/22/2015 12:49 AM, Peter Stephenson wrote:
> The check needs to be able to perform a compilation, so it has to find
> the headers as well as the libraries.
You mean besides /usr/include/pcre.h which is already found?
'libpcre3-dev' is installed. Maybe it will take another Debian user to
know what to do. Or is this important at all? One doesn't like to see
any defect in 'make check', but I know that some of the checks are not
vital.
> Those are typically in some additional package. You'll probably find
> you have a package "pcre" installed and need another one called
> "pcre-devel" or something similar. pws
next prev parent reply other threads:[~2015-01-22 16:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 0:19 completion Ray Andrews
2015-01-17 2:57 ` Command substitution parsing issues (not really Re: completion) Bart Schaefer
2015-01-17 3:29 ` Ray Andrews
2015-01-17 13:25 ` Vin Shelton
2015-01-19 10:29 ` Peter Stephenson
2015-01-19 10:39 ` Peter Stephenson
2015-01-22 0:34 ` make check problem Ray Andrews
2015-01-22 8:49 ` Peter Stephenson
2015-01-22 16:00 ` Ray Andrews [this message]
2015-01-22 16:40 ` Jun T.
2015-01-22 17:38 ` Ray Andrews
2015-01-22 17:56 ` Bart Schaefer
2015-01-22 18:24 ` Ray Andrews
2015-01-23 4:02 ` Bart Schaefer
2015-01-23 4:48 ` Ray Andrews
2015-01-22 19:04 ` --enable-pcre and regex comparison (Was: make check problem) Lawrence Velázquez
2015-01-23 4:04 ` Bart Schaefer
2015-01-18 16:36 ` Command substitution parsing issues (not really Re: completion) Peter Stephenson
2015-01-18 17:31 ` Peter Stephenson
2015-01-18 22:34 ` 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=54C11EAE.6000904@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-workers@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).