From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-23280-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 18919 invoked by alias); 26 Mar 2018 02:53:36 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
List-Unsubscribe: <mailto:zsh-users-unsubscribe@zsh.org>
X-Seq: 23280
Received: (qmail 9724 invoked by uid 1010); 26 Mar 2018 02:53:36 -0000
X-Qmail-Scanner-Diagnostics: from forward105p.mail.yandex.net by f.primenet.com.au (envelope-from <mva@mva.name>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(77.88.28.108):SA:0(-2.6/5.0):. 
 Processed in 1.754898 secs); 26 Mar 2018 02:53:36 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
	SPF_PASS autolearn=ham autolearn_force=no version=3.4.1
X-Envelope-From: mva@mva.name
X-Qmail-Scanner-Mime-Attachments: |signature.asc|
X-Qmail-Scanner-Zip-Files: |
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
Message-ID: <1700598.0ICZtn5EgB@note>
In-Reply-To: <CAH+w=7Y6E5r4W9VdermWM8pEVtR45POLbGvNCMq-JfAsb2OyZQ@mail.gmail.com>
References: <3073701.qdQlh9y6XZ@note> <29268448.1ttGRCcLCz@note> <CAH+w=7Y6E5r4W9VdermWM8pEVtR45POLbGvNCMq-JfAsb2OyZQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1844891.hT0eWj2S6j"; micalg="pgp-sha256"; protocol="application/pgp-signature"

--nextPart1844891.hT0eWj2S6j
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="UTF-8"

> 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.

--nextPart1844891.hT0eWj2S6j
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQTxiw6i5QzSBiZgM/FnZfRvKOlgfgUCWrhgpQAKCRBnZfRvKOlg
fsnyAQC+FbUKOpvOszosqlNEYZr8INWXibJbX3Ty45sDySBmmAEAp9RTLOz12bq6
Bsb8CRcqFOIkaXwz60kxCj5MJbTsyQc=
=1ZP5
-----END PGP SIGNATURE-----

--nextPart1844891.hT0eWj2S6j--