From: Vincent Stemen <zsh@hightek.org>
To: zsh-users@sunsite.dk
Subject: Re: pcre module help
Date: Sun, 20 Jun 2004 16:20:37 -0500 [thread overview]
Message-ID: <20040620212037.GA39276@quark.hightek.org> (raw)
In-Reply-To: <20040620193711.GA15629@scowler.net>
On Sun, Jun 20, 2004 at 03:37:11PM -0400, Clint Adams wrote:
> > I tried this under zsh-4.2.0 on FreeBSD with the pcre module statically
> > linked in.
>
> Is the zsh binary actually linked against libpcre?
> Does configure detect the existence of pcre_compile() and pcre_exec()?
> You shouldn't get the "not available on this system" message unless it
> didn't find one of them.
Looks like you are right. I thought it would automatically use it if
it was available on the system and I enabled it in config.modules.
Especially since it still went through pcre detection, because I saw
output from configure that said,
checking pcre.h usability... yes
checking pcre.h presence... yes
checking for pcre.h... yes
However, further down I disovered it said,
checking for pcre_compile... no
checking for pcre_study... no
checking for pcre_exec... no
because it did not use -lpcre.
Enabling it with the configure option, --enable-pcre, seems to have
corrected that, although I have not recompiled and tested it yet.
> > pcre_compile: not available on this system
> >
> > pcre_match: not available on this system
>
> >
> > # if [[ $PATH -pcre-match '^/.*local' ]]; then echo "matched"; fi
> >
> > zsh: unrecognized condition: `$PATH'
> >
> > # pcre_compile "^/.*local"
> >
> > pcre_compile: not available on this system
> >
> > # if [[ $PATH -pcre-match '^/.*local' ]]; then echo "matched"; fi
> >
> > -- shell crashes leaving a core file --
> >
> > The shell crashing is consistent when I try to use -pcre-match after
> > attempting to run pcre_compile. Also, the -pcre-match method is not
> > mentioned in the zshmodules manual.
>
> Could you send a gdb backtrace to zsh-workers?
I would still think it should not crash because of a missing feature.
If you still would like a backtrace to find that problem, I will try
to get around to recompiling it with debugging turned on and generate
one for you. Just let me know.
Vincent
--
Vincent Stemen
Avoid the VeriSign/Network Solutions domain registration trap!
Read how Network Solutions (NSI) was involved in stealing our domain name.
http://www.InetAddresses.net
prev parent reply other threads:[~2004-06-20 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 11:49 lists
2004-06-20 14:48 ` Clint Adams
2004-06-20 17:36 ` Vincent Stemen
2004-06-20 17:39 ` Vincent Stemen
2004-06-20 19:37 ` Clint Adams
2004-06-20 21:20 ` Vincent Stemen [this message]
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=20040620212037.GA39276@quark.hightek.org \
--to=zsh@hightek.org \
--cc=zsh-users@sunsite.dk \
/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).