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 09:53:25 +0700 [thread overview]
Message-ID: <1700598.0ICZtn5EgB@note> (raw)
In-Reply-To: <CAH+w=7Y6E5r4W9VdermWM8pEVtR45POLbGvNCMq-JfAsb2OyZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
> Why is pcre linking to this? If pcre is actually starting threads,
> there may be unexpected side-effects.
I don't know :(
But I know that dynamic version of libpcre links to pthread as well:
> $ ldd /lib64/libpcre.so.1
> linux-vdso.so.1 (0x00007ffd63be6000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7e8015e000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f7e7fd9a000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f7e805f0000)
// And even libpcre2 links to it.
And I don't see any kind of `--enable-threads` or `--enable-pthread` in their
ebuilds (package manager build scripts), so, I guess, they links to pthread on
their own, and not on maintainers decision.
[-- 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 2:53 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 [this message]
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=1700598.0ICZtn5EgB@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).