From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-08-30
Date: Wed, 5 Sep 2018 08:49:27 +0200 [thread overview]
Message-ID: <20180905084927.2a3fa35c@windsurf> (raw)
In-Reply-To: <a9927d39-0d18-8d49-7ac6-07ac9dfb4daa@mind.be>
Hello,
On Wed, 5 Sep 2018 00:43:32 +0200, Arnout Vandecappelle wrote:
> So what does gentoo do? They simply don't have a dependency on util-linux in
> the python3.7.0.ebuild. Indeed, it turns out that the _uuid module is entirely
> optional. It is only used to access the uuid_generate_time_safe() function, but
> the uuid.py module can also get this function through ctypes (i.e. dlopen()). So
> perhaps a simpler solution is to just remove the build-time python3 ->
> util-linux dependency? Runtime is still needed to support the dlopen path.
Aaah, seems like a very good idea. This would solve all the circular
dependencies we're seeing, with essentially no additional complexity.
The only downside is that the python3 util-linux support would not work
in static-linking scenarios, because in such cases dlopen() is not
available. But python3 anyway has "depends on !BR2_STATIC_LIBS", so
we're good :-)
Adam: could you look at implementing this solution, and do a runtime
check that the uuid-related feature of Python 3 are working as
expected ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-05 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180831060016.342FF22A3A@mail.bootlin.com>
2018-09-02 19:57 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-08-30 Carlos Santos
2018-09-03 15:29 ` Matthew Weber
2018-09-03 19:49 ` Matthew Weber
2018-09-04 9:45 ` Thomas Petazzoni
2018-09-04 22:43 ` Arnout Vandecappelle
2018-09-05 6:49 ` Thomas Petazzoni [this message]
2018-09-18 21:49 ` Thomas Petazzoni
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=20180905084927.2a3fa35c@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