All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Weber <matthew.weber@rockwellcollins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] python3: ncurses condition for libselinux enabled
Date: Thu, 13 Apr 2017 16:20:41 -0500	[thread overview]
Message-ID: <CANQCQpb4ySf=NtgNbWShus4YUrJDFqhqTgB0b_oc++Ov3xrmsw@mail.gmail.com> (raw)
In-Reply-To: <20170413222710.419f6cd1@free-electrons.com>

Thomas,

On Thu, Apr 13, 2017 at 3:27 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Wed, 12 Apr 2017 23:16:13 -0500, Matt Weber wrote:
>> When libselinux is enabled, a circular dependency is
>> created.  Disable ncurses python support when libselinux
>> is enabled so that the circular busybox, ncurses,
>> python, libselinux chain is broken.
>>
>> Resolves
>> http://autobuild.buildroot.net/results/db1/db1e6f3054092fc5576ccab8e04a3b9d74ca9a8c/
>>
>> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
>
> I am not sure this is the right approach to fix this issue. It feels
> really weird to no longer be able to use ncurses support in Python(3)
> when SELinux is enabled.
>
> I believe the real issue is that Busybox really doesn't care at all
> about the Python bindings for libselinux. So perhaps we should split
> the Python bindings build/installation from libselinux into a separate
> package. I think we had a similar split for another package.
>
> It would however require some investigation to figure out if it's
> possible to build just the Python bindings, using an already built and
> installed libselinux.

I'll take a look.

-Matt

  reply	other threads:[~2017-04-13 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  4:16 [Buildroot] [PATCH 1/3] libselinux: target python interface generation Matt Weber
2017-04-13  4:16 ` [Buildroot] [PATCH 2/3] python3: ncurses condition for libselinux enabled Matt Weber
2017-04-13 20:27   ` Thomas Petazzoni
2017-04-13 21:20     ` Matthew Weber [this message]
2017-04-13 21:55       ` Arnout Vandecappelle
2017-04-14  2:29         ` Matthew Weber
2017-04-14  7:24           ` Thomas Petazzoni
     [not found]             ` <CANQCQpb+0UX5C8npsCXNVMOvR89mdF1jZ1jATLwTufK_633kWw@mail.gmail.com>
     [not found]               ` <CANQCQpbtX9ciJhtCSuA0k5Y9tFqtOuziZqpDYbjbz1viaPu6cg@mail.gmail.com>
2017-04-14 11:07                 ` Matthew Weber
2017-04-13  4:16 ` [Buildroot] [PATCH 3/3] python: " Matt Weber
2017-04-13 20:19 ` [Buildroot] [PATCH 1/3] libselinux: target python interface generation 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='CANQCQpb4ySf=NtgNbWShus4YUrJDFqhqTgB0b_oc++Ov3xrmsw@mail.gmail.com' \
    --to=matthew.weber@rockwellcollins.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 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.