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 10:27:33 +0200 [thread overview]
Message-ID: <20170720102733.2d606f02@windsurf> (raw)
In-Reply-To: <CAO6UsjBm0q9_g8_dpuA=7kPcFuzhouvM_8GV1J=+76PDfVykSw@mail.gmail.com>
Hello,
On Thu, 20 Jul 2017 16:21:51 +0800, Diankun Zhang wrote:
> According to HOST_PYTHON_CONF_OPTS defined in python.mk, --disable-hashlib
> is not specified.
> That means _hashlib should be enabled by default, right?
Well, no, not necessarily. We simply forgot to add --disable-hashlib.
Again: why do you need this? If you could answer this question it would
make the discussion a lot more productive :-)
It is very possible that there are legitimate use cases for having
the hashlib module built in the host Python interpreter. If we
understand those use cases, then we can come up with a solution. But if
you keep being silent about the *why* you need this, we won't move very
far.
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 8:27 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
2017-07-20 8:21 ` Diankun Zhang
2017-07-20 8:27 ` Thomas Petazzoni [this message]
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=20170720102733.2d606f02@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