From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python: fix building _hashlib of host-python
Date: Thu, 20 Jul 2017 09:56:36 +0200 [thread overview]
Message-ID: <20170720095636.72423497@windsurf> (raw)
In-Reply-To: <CAO6UsjCZQUKvmA-a0votPq5AFZ6ESkwpNbLvfEymU5uy_SdggA@mail.gmail.com>
Hello,
On Thu, 20 Jul 2017 15:33:17 +0800, Diankun Zhang wrote:
> The python buildin module _hashlib has dependency on library
> libcrypto.so to provide the SHA-224, SHA-256, SHA-384, SHA-512
> hash algorithms in addition to platform optimized versions
> of MD5 and SHA1. Adding host package dependency on host-openssl
> to support the building of _hashlib module for host-python.
>
> Signed-off-by: Diankun Zhang <kundy.zhang@gmail.com>
Why do you need the _hashlib module in the host-python ?
Indeed, we try to avoid adding too many dependencies, and adding a new
dependency to host-python is going to increase the build time to a
large number of people who don't necessarily need the _hashlib module
in the host Python interpreter.
So could you explain why this is needed ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-20 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 7:33 [Buildroot] [PATCH 1/1] package/python: fix building _hashlib of host-python Diankun Zhang
2017-07-20 7:56 ` Thomas Petazzoni [this message]
2017-07-20 8:21 ` Diankun Zhang
2017-07-20 8:27 ` Thomas Petazzoni
2017-07-20 9:09 ` Diankun Zhang
2017-07-20 9:19 ` Thomas Petazzoni
2017-07-20 10:59 ` Diankun Zhang
2017-07-20 11:09 ` Thomas Petazzoni
2017-07-20 11:20 ` Diankun Zhang
2017-07-20 11:24 ` Thomas Petazzoni
2017-07-20 11:39 ` Diankun Zhang
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=20170720095636.72423497@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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