Re: make check problem

[Ray Andrews <rayandrews@eastlink.ca>]

On 01/22/2015 08:40 AM, Jun T. wrote:
> 2015/01/22 09:34, Ray Andrews <rayandrews@eastlink.ca> wrote:
>>   checking for pcre_compile... no
>>   checking for pcre_study... no
>>   checking for pcre_exec... no
> Did you use --enable-pcre with configure?
>
> $ ./configure --enable-pcre ...other options...
>
Nope.  I wonder why 'make check' indicates a fault when the test can't 
possibly succeed from the getgo without that option? Are there other 
modules that require that sort of special handling?  Why is it special? 
Do I need it anyway?

Anyway, I added that option, and now:


----------------------------------------------------
./V07pcre.ztst: starting.
Testing PCRE multibyte with locale en_US.UTF-8
*** /tmp/zsh.ztst.out.27929    2015-01-22 08:55:33.172945830 -0800
--- /tmp/zsh.ztst.tout.27929    2015-01-22 08:55:33.184945978 -0800
***************
*** 1,12 ****
! 0 o→b →b
! 1
! 1
! 0 o→† →†
! 0 o→b →b
! 1
! 0 o→b →b
! 0 o→b →b
! 0 xo→t →t
! 1
! 0 xo→t →t
! 0 Xo→t →t
--- 1,12 ----
! 127 bar 0 :pcre_compile interface testing: basic, anchored & 
case-insensitive
! 127
! 127
! 127
! 127
! 127
! 127
! 127
! 127
! 127
! 127
! 127
Test ./V07pcre.ztst failed: output differs from expected as shown above for:
   pcre_compile '.(→.)'
   pcre_match foo→bar
   print $? $MATCH $match ; unset MATCH match
   pcre_match foo.bar
   print $? $MATCH $match ; unset MATCH match
   pcre_match foo†bar
   print $? $MATCH $match ; unset MATCH match
   pcre_match foo→†ar
   print $? $MATCH $match ; unset MATCH match
   pcre_study
   pcre_match foo→bar
   print $? $MATCH $match ; unset MATCH match
   pcre_compile -a '.(→.)'
   pcre_match foo→bar
   print $? $MATCH $match ; unset MATCH match
   pcre_match o→bar
   print $? $MATCH $match ; unset MATCH match
   pcre_match o→b
   print $? $MATCH $match ; unset MATCH match
   pcre_compile 'x.(→.)'
   pcre_match xo→t
   print $? $MATCH $match ; unset MATCH match
   pcre_match Xo→t
   print $? $MATCH $match ; unset MATCH match
   pcre_compile -i 'x.(→.)'
   pcre_match xo→t
   print $? $MATCH $match ; unset MATCH match
   pcre_match Xo→t
   print $? $MATCH $match ; unset MATCH match
Error output:
(eval):1: command not found: pcre_compile
(eval):2: command not found: pcre_match
(eval):4: command not found: pcre_match
(eval):6: command not found: pcre_match
(eval):8: command not found: pcre_match
(eval):10: command not found: pcre_study
(eval):11: command not found: pcre_match
(eval):13: command not found: pcre_compile
(eval):14: command not found: pcre_match
(eval):16: command not found: pcre_match
(eval):18: command not found: pcre_match
(eval):20: command not found: pcre_compile
(eval):21: command not found: pcre_match
(eval):23: command not found: pcre_match
(eval):25: command not found: pcre_compile
(eval):26: command not found: pcre_match
(eval):28: command not found: pcre_match
Was testing: pcre_compile interface testing: basic, anchored & 
case-insensitive
./V07pcre.ztst: test failed.
-------------------------------------------------------------

... However, in config.log:

-----------------------------------------------------------
configure:8329: checking for pcre_compile
configure:8329: gcc -o conftest  -Wall -Wmissing-prototypes -O2 
conftest.c -lpcre -ldl -ltinfo -lrt -lm  -lc >&5
configure:8329: $? = 0
configure:8329: result: yes
configure:8329: checking for pcre_study
configure:8329: gcc -o conftest  -Wall -Wmissing-prototypes -O2 
conftest.c -lpcre -ldl -ltinfo -lrt -lm  -lc >&5
configure:8329: $? = 0
configure:8329: result: yes
configure:8329: checking for pcre_exec
configure:8329: gcc -o conftest  -Wall -Wmissing-prototypes -O2 
conftest.c -lpcre -ldl -ltinfo -lrt -lm  -lc >&5
configure:8329: $? = 0
configure:8329: result: yes
--------------------------------------------------------------------

... there are no failures shown anywhere.  It seems the functions are 
there but there's no matching commands available (if there are any such 
things).  However, I do have /usr/bin/pcre-config and perhaps that is 
not doing it's job? It is referred to in config.log.