summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAdrian Bunk <bunk@stusta.de>2019-09-29 23:46:25 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-10-10 16:52:30 +0100
commitcc0605bad6c2bde06136f3af5eeb145a9636c5d2 (patch)
treebf1d285758ddd6a347525303635aa4dc1412c012
parentb15ffd14acf9008755abc5048792a03953290f21 (diff)
downloadpoky-cc0605bad6c2bde06136f3af5eeb145a9636c5d2.tar.gz
json-c: Don't --enable-rdrand
In recent years AMD CPUs have had various problems with RDRAND giving either non-random data or no result at all, which is problematic if either build or target machine has a CPU with this problem. The fallback is /dev/urandom, and I'd trust the kernel here. --enable-rdrand was added in an upgrade to a new upstream version without mentioning any reason. [YOCTO #13534] (From OE-Core rev: fad633eb5c464d4e2a984b9259625bcd150ee357) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/recipes-devtools/json-c/json-c_0.13.1.bb2
1 files changed, 0 insertions, 2 deletions
diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb b/meta/recipes-devtools/json-c/json-c_0.13.1.bb
index 5b10e68297..e6a38995cb 100644
--- a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
+++ b/meta/recipes-devtools/json-c/json-c_0.13.1.bb
@@ -20,8 +20,6 @@ RPROVIDES_${PN} = "libjson"
20 20
21inherit autotools 21inherit autotools
22 22
23EXTRA_OECONF = "--enable-rdrand"
24
25do_configure_prepend() { 23do_configure_prepend() {
26 # Clean up autoconf cruft that should not be in the tarball 24 # Clean up autoconf cruft that should not be in the tarball
27 rm -f ${S}/config.status 25 rm -f ${S}/config.status