Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/python-cryptography: bump version to 2.3.1
Date: Mon, 10 Sep 2018 23:39:24 +0200	[thread overview]
Message-ID: <ct4j6fxcf3.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: CAGm1_ktoBnagq89z6WbQcTCB4Fkc5bY2YqEnpy3PeVZbMST_hA@mail.gmail.com

Am Mon, 20 Aug 2018 10:05:15 +0200 schrieb Yegor Yefremov:

> I've performed a runtime test and I still get:
[...]
> ImportError:
> /usr/lib/python3.6/site-packages/cryptography/hazmat/bindings/
_openssl.abi3.so:
> undefined symbol: pthread_atfork

Hi,

I did not find the time to do a run-time test yet, sorry, but it seems 
you are not the only one hitting the problem:

https://www.mail-archive.com/yocto at yoctoproject.org/msg38512.html

https://forums.gentoo.org/viewtopic-p-8120220.html?
sid=b50fe8a26a38d18882c5f2915a030408

https://lists.yoctoproject.org/pipermail/yocto/2017-December/039398.html

The solution is to add "-pthread":

https://patchwork.openembedded.org/patch/146240/

https://bugs.gentoo.org/630578

https://gitweb.gentoo.org/repo/gentoo.git/commit/?
id=c824d1c44fcf4556de21d2c8b8ae3732b0fc0c5b

Could you please do another runtime test with this fix added?

Regards, Bernd

  parent reply	other threads:[~2018-09-10 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-19 18:42 [Buildroot] [PATCH/next 1/1] package/python-cryptography: bump version to 2.3.1 Bernd Kuhls
2018-08-19 18:53 ` Yegor Yefremov
2018-08-19 19:02   ` Bernd Kuhls
2018-08-20  8:05     ` Yegor Yefremov
2018-08-20 12:05       ` Yegor Yefremov
2018-09-10 21:39       ` Bernd Kuhls [this message]
2018-09-11  6:52         ` Yegor Yefremov
2018-08-29 20:20 ` Thomas Petazzoni

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=ct4j6fxcf3.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --cc=buildroot@busybox.net \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox