From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
To: zsh-users@zsh.org
Subject: Re: zsh/pcre module breakage when static build enabled
Date: Mon, 26 Mar 2018 15:16:53 +0700 [thread overview]
Message-ID: <2320204.0CN0jtCPyd@note> (raw)
In-Reply-To: <20180326053715.GA37203@tower.spodhuis.org>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
В письме от понедельник, 26 марта 2018 г. 12:37:15 +07 пользователь Phil
Pennock написал:
> 40. Static linking against the PCRE library using the pkg-config module was
> failing on missing pthread symbols.
Well, I've looked in commit history, and found that:
https://github.com/svn2github/pcre/commit/
2765d0933715e6b2c78a4e74fa8d5cad27273f29
And my `libpcre.pc` have
> Libs.private: -pthread
at that place.
Although, I'm not sure if it is okay for it to be `-pthread`, and not `-
lpthread`.
> Vadim has `pcre-config --version` reporting 8.42 though. Perhaps a
> regression, perhaps a system mismatch between libraries and tools.
I bet on regression (since I'm using source-based distro and it's pretty
unlikely to have that mismatch here.
>
> Regardless, all the relevant errors from Vadim's post are in compiling
> JIT stuff, which we're not using. So it's bloat for unused
> functionality but shouldn't be affecting our operation.
Well, I'll try to check if manual fixing of libpcre's pkg-config file would
help. Now it really looks like libpcre issue.
By the way,
> $ ldd /usr/lib64/zsh/5.4.2/zsh/pcre.so
> linux-vdso.so.1 (0x00007ffd8469b000)
> libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f368efaa000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f368ebe6000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f368e9c6000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f368f420000)
Here, libpthread is inherited from dynamic libpcre, and (I hope) it doesn't
interfere with any zsh's internal work. So, I guess, it shouldn't interfere in
static too.
But I'm not sure if it should be worked around in zsh at all (in case, if I'll
confirm that is libpcre's pc-file bug).
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-03-26 8:23 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
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 [this message]
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=2320204.0CN0jtCPyd@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).