From: "Jan Kundrát" <jan.kundrat@cesnet.cz>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python3: require util-linux' <uuid.h>
Date: Thu, 7 Mar 2019 17:23:36 +0100 [thread overview]
Message-ID: <e5b1510a81bda096dacc133276f1ff2643131dcc.1551975775.git.jan.kundrat@cesnet.cz> (raw)
Without this dependency, a top level parallel build fails for me (-j24):
/home/ci/build/build/host-python3-3.7.2/Modules/_uuidmodule.c: In function 'py_uuid_generate_time_safe':
/home/ci/build/build/host-python3-3.7.2/Modules/_uuidmodule.c:15:5: error: unknown type name 'uuid_t'; did you mean 'uid_t'?
uuid_t uuid;
^~~~~~
uid_t
/home/ci/build/build/host-python3-3.7.2/Modules/_uuidmodule.c:32:5: error: implicit declaration of function 'uuid_generate_time'; did you mean 'py_uuid_generate_time_safe'? [-Werror=implicit-function-declaration]
uuid_generate_time(uuid);
^~~~~~~~~~~~~~~~~~
py_uuid_generate_time_safe
I *suspect* that this is due to host-uboot-tools which provide
/usr/include/uuid.h and which gets accidentally picked by python3.
There's a bugreport [1] upstream which at leeast appears to be relevant.
[1] https://bugs.python.org/issue32627
Signed-off-by: Jan Kundr?t <jan.kundrat@cesnet.cz>
---
package/python3/python3.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/python3/python3.mk b/package/python3/python3.mk
index ef2c4857d8..dcec210674 100644
--- a/package/python3/python3.mk
+++ b/package/python3/python3.mk
@@ -40,7 +40,7 @@ HOST_PYTHON3_CONF_ENV += \
PYTHON3_DEPENDENCIES = host-python3 libffi
-HOST_PYTHON3_DEPENDENCIES = host-expat host-zlib host-libffi
+HOST_PYTHON3_DEPENDENCIES = host-expat host-zlib host-libffi host-util-linux
PYTHON3_INSTALL_STAGING = YES
--
2.19.1
next reply other threads:[~2019-03-07 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 16:23 Jan Kundrát [this message]
2019-03-07 20:24 ` [Buildroot] [PATCH] package/python3: require util-linux' <uuid.h> Thomas Petazzoni
2019-03-12 15:26 ` Jan Kundrát
2019-03-12 15:38 ` Thomas Petazzoni
2019-03-07 20:50 ` Arnout Vandecappelle
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=e5b1510a81bda096dacc133276f1ff2643131dcc.1551975775.git.jan.kundrat@cesnet.cz \
--to=jan.kundrat@cesnet.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.