From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
To: zsh-users@zsh.org
Subject: Re: zsh/pcre module breakage when static build enabled
Date: Tue, 20 Mar 2018 12:16:10 +0700 [thread overview]
Message-ID: <3473799.7LEjvMZMrB@note> (raw)
In-Reply-To: <20180319234236.GA43407@tower.spodhuis.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Well, I just tried to repeat your steps:
---------
mkdir /tmp/zsh
cd /tmp/zsh
git pull git://git.code.sf.net/p/zsh/code
./.preconfig
CPPFLAGS=-I/usr/include LDFLAGS='-L/usr/lib64 -static' \
./configure --prefix=/tmp/zsh/uzsh --enable-etcdir=/etc --with-tcsetpgrp \
--enable-function-subdirs --enable-maildir-support --enable-multibyte \
--enable-zsh-mem --enable-zsh-secure-free --sysconfdir=/usr \
--disable-dynamic --with-term-lib="tinfow tinfo" --enable-pcre \
--disable-dynamic
# yeah, even with double `disable-dynamic like in yours)
sed -i -e '/name=zsh\/(pcre|regex)/s/link=no/link=static/' config.modules
make
----------
Then I called ./Src/zsh -f, and...
note% setopt rematchpcre
note% [[ 'foo→bar' =~ .([^[:ascii:]]). ]]; print $MATCH
zsh: module `zsh/pcre' has no such feature: `C:pcre-match'
zsh: -pcre-match not available for regex
So, it seems, it is either somehow related to linux only, or to libpcre
version, maybe...
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-03-20 5:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 17:33 Vadim A. Misbakh-Soloviov
2018-03-19 23:42 ` Phil Pennock
2018-03-20 5:02 ` Vadim A. Misbakh-Soloviov
2018-03-20 5:16 ` Vadim A. Misbakh-Soloviov [this message]
2018-03-21 2:15 ` Phil Pennock
2018-03-25 6:04 ` Vadim A. Misbakh-Soloviov
2018-03-25 6:25 ` Vadim A. Misbakh-Soloviov
2018-03-25 19:50 ` Bart Schaefer
2018-03-26 2:53 ` Vadim A. Misbakh-Soloviov
2018-03-26 5:37 ` Phil Pennock
2018-03-26 8:16 ` Vadim A. Misbakh-Soloviov
2018-03-26 9:41 ` Vadim A. Misbakh-Soloviov
2018-03-19 18:13 Vadim A. Misbakh-Soloviov
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=3473799.7LEjvMZMrB@note \
--to=mva@mva.name \
--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).