From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python: re-enable hashlib
Date: Mon, 3 Feb 2020 12:31:12 +0100 [thread overview]
Message-ID: <20200203123112.41c6247b@windsurf> (raw)
In-Reply-To: <20200203111837.13376-1-titouan.christophe@railnova.eu>
On Mon, 3 Feb 2020 12:18:37 +0100
titouan.christophe at railnova.eu wrote:
> From: Titouan Christophe <titouan.christophe@railnova.eu>
>
> In commit e5cfb319f9493d677f059ca72b80f7fa22fc9f0f,
> the committer did add the flag `--disable-hashlib` to python,
> even though this was not part of the original patch
> (https://patchwork.ozlabs.org/patch/1231905/).
>
> This unexpected modification break the builds of waf-based
> packages, such as jack2, mpv or aubio. This commit therefore
>
> Fixes: http://autobuild.buildroot.net/results/2b3/2b377bcfda6e7ae4d6bb894664e3a4cb13a70b6d/
> Fixes: http://autobuild.buildroot.net/results/cd5/cd5da8cb3da8479ebee60d011ce0c5dc0e59aab7/
>
> Signed-off-by: Titouan Christophe <titouan.christophe@railnova.eu>
Note to self: "git commit -a --amend" can be dangerous. Sorry for the mess.
However, this particular change is related to a discussion I had on the
mailing list about this hashlib module which was causing build issues
on some machines in host Python. This module needs OpenSSL on the host,
which we don't have installed on some autobuilders. So how come we
hadn't seen these failures before ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-02-03 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 11:18 [Buildroot] [PATCH 1/1] package/python: re-enable hashlib titouan.christophe at railnova.eu
2020-02-03 11:31 ` 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=20200203123112.41c6247b@windsurf \
--to=thomas.petazzoni@bootlin.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