Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-08-30
Date: Tue, 4 Sep 2018 11:45:12 +0200	[thread overview]
Message-ID: <20180904114512.153df013@windsurf> (raw)
In-Reply-To: <CANQCQpbSwyZXQZyOgG2-kcPFS0HcJENhzZWg9oCjaDRx5FWwYA@mail.gmail.com>

Hello,

On Mon, 3 Sep 2018 14:49:24 -0500, Matthew Weber wrote:

> Figured it out, the python3 bump and the addition of the python uuid
> dependency on util-linux, created a circular dependency making
> libselinux and util-linux build out of order.
> (6e7e733f3bb)

So, if I get it right, the circular dependency is:

 util-linux -> libselinux -> python3 -> util-linux

But wait, I realize that there is worse, with the Python libuuid thing,
we have the following circular dependency as well:

 util-linux -> python3 -> util-linux

So that last one we can fix by introducing python-util-linux, as I was
suggesting to also solve the BlueZ related circular:

  http://lists.busybox.net/pipermail/buildroot/2018-August/229558.html

But that first one is different, because it won't be solved by moving
the util-linux Python bindings to a separate package. To solve:

 util-linux -> libselinux -> python3 -> util-linux

then we need to create python-libselinux, which will build/install the
python bindings of libselinux. This way util-linux -> libselinux will
not pull in a python3 dependency. This should be doable, because
libselinux has separate make targets for building/installing the python
bindings.

These circular dependencies are annoying.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-09-04  9:45 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 [this message]
2018-09-04 22:43         ` Arnout Vandecappelle
2018-09-05  6:49           ` Thomas Petazzoni
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=20180904114512.153df013@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