From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Subject: --enable-pcre doesn't fail when not supported / zsh should switch to PCRE2
Date: Fri, 2 Sep 2022 02:26:36 +0200 [thread overview]
Message-ID: <20220902002636.GC1046913@zira.vinc17.org> (raw)
I've configured zsh with
./configure --enable-pcre --prefix=$HOME/opt/zsh-dev
but I get the following error:
zira:~,2> zmodload zsh/pcre
zsh: failed to load module `zsh/pcre': /home/vinc17/opt/zsh-dev/lib/zsh/5.9.0.1-dev/zsh/pcre.so: cannot open shared object file: No such file or directory
In config.log:
configure:6170: checking for pcre-config
configure:6205: result: no
[...]
configure:6401: checking for pcre.h
configure:6401: gcc -c -Wall -Wmissing-prototypes -O2 conftest.c >&5
conftest.c:95:10: fatal error: pcre.h: No such file or directory
95 | #include <pcre.h>
| ^~~~~~~~
compilation terminated.
[...]
configure:6401: result: no
[...]
configure:9995: checking for pcre_compile
configure:9995: gcc -o conftest -Wall -Wmissing-prototypes -O2 conftest.c -ldl -lncursesw -lrt -lm -lc >&5
/usr/bin/ld: /tmp/cc9sU4eV.o: in function `main':
conftest.c:(.text.startup+0x7): undefined reference to `pcre_compile'
collect2: error: ld returned 1 exit status
configure:9995: $? = 1
[...]
/usr/bin/ld: /tmp/ccuULZbN.o: in function `main':
conftest.c:(.text.startup+0x7): undefined reference to `pcre_study'
collect2: error: ld returned 1 exit status
configure:10001: $? = 1
[...]
etc.
So, first, the configure script should have failed because of
the --enable-pcre option, meaning that one wants PCRE.
Moreover, the current PCRE version is PCRE2, and zsh should switch
to it.
https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions
says:
In 2015 a fork of PCRE was released with a revised programming
interface (API). The original software, now called PCRE1 (the
1.xx–8.xx series), has had bugs mended, but no further development.
As of 2020, it is considered obsolete, and the current 8.45 release
is likely to be the last. The new PCRE2 code (the 10.xx series) has
had a number of extensions and coding improvements and is where
development takes place.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
reply other threads:[~2022-09-02 0:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220902002636.GC1046913@zira.vinc17.org \
--to=vincent@vinc17.net \
--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).