From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python: disable _ssl.c build when --disable-ssl
Date: Fri, 10 Mar 2017 21:30:03 +0100 [thread overview]
Message-ID: <20170310213003.5cd63c7f@free-electrons.com> (raw)
In-Reply-To: <CAO1odpzB59BT3cgh3AVznLzcWz+nShYsok1GqEv_SV9N3wXbLA@mail.gmail.com>
Hello,
On Fri, 10 Mar 2017 13:36:45 -0600, Adam Allison wrote:
> Ok, I guess my browser took a dump, and send the message early.
>
> In setup.py, it will pull in hashlib if 'have_any_openssl' and
> 'have_usable_openssl' is true.
>
> The old patch forced those to be false.
> This one (cleaner), but the setup.py will have to change as well.
Could you explain in more details what Buildroot configuration you're
using, the problem you're seeing, and what you're expecting to see
instead?
Notice that there is a different option for hashlib,
BR2_PACKAGE_PYTHON_HASHLIB, and it was very recently fixed to really
disable hashlib when disabled (commit
https://git.buildroot.org/buildroot/commit/?id=bc3e1fb22ef641916938fff76bef10a1347ef0f7).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-03-10 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 21:22 [Buildroot] [PATCH 1/1] python: disable _ssl.c build when --disable-ssl Matt Weber
2017-01-13 9:31 ` Nicolas Cavallari
2017-03-09 23:04 ` Thomas Petazzoni
2017-03-10 18:15 ` Matthew Weber
[not found] ` <CAO1odpw8E=b2eTsVX8vCjhUF_vpg34WJvUxCKGCm+p0OSMsdkw@mail.gmail.com>
[not found] ` <CAO1odpzng87mcYwEFs72B9bRTdLgewtGscH1GsuEAyndOVuntw@mail.gmail.com>
[not found] ` <CAO1odpzB59BT3cgh3AVznLzcWz+nShYsok1GqEv_SV9N3wXbLA@mail.gmail.com>
2017-03-10 20:30 ` Thomas Petazzoni [this message]
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=20170310213003.5cd63c7f@free-electrons.com \
--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