From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: make check problem
Date: Wed, 21 Jan 2015 16:34:48 -0800 [thread overview]
Message-ID: <54C045A8.10102@eastlink.ca> (raw)
In-Reply-To: <20150119102910.18102a0b@pwslap01u.europe.root.pri>
I'm getting this 'make check' problem:
./V07pcre.ztst: skipped (the zsh/pcre module is not available)
Studying the output of './configure':
...
checking pcre.h usability... no
checking pcre.h presence... no
checking for pcre.h... no
checking for pcre_compile... no
checking for pcre_study... no
checking for pcre_study... no
...
After installing 'libpcre3-dev' :
checking pcre.h usability... yes
checking pcre.h presence... yes
checking for pcre.h... yes
checking for pcre_compile... no
checking for pcre_study... no
checking for pcre_exec... no
All three 'pcre_*' functions exist in both:
/usr/lib/i386-linux-gnu/libpcre.a
/usr/lib/i386-linux-gnu/libpcre.so
... so I'm wondering why they are not linked.
This is under Debian testing.
next prev parent reply other threads:[~2015-01-22 0:34 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 ` Ray Andrews [this message]
2015-01-22 8:49 ` make check problem Peter Stephenson
2015-01-22 16:00 ` Ray Andrews
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=54C045A8.10102@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).