Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3,3/8] libsemanage: bump to version 2.8
Date: Thu, 11 Oct 2018 22:07:06 +0200	[thread overview]
Message-ID: <20181011220706.01ff455d@windsurf> (raw)
In-Reply-To: <20181011193707.20510-3-fontaine.fabrice@gmail.com>

Hello Fabrice,

On Thu, 11 Oct 2018 21:37:02 +0200, Fabrice Fontaine wrote:

> -LIBSEMANAGE_VERSION = 2.7
> -LIBSEMANAGE_SITE = https://raw.githubusercontent.com/wiki/SELinuxProject/selinux/files/releases/20170804
> +LIBSEMANAGE_VERSION = 2.8
> +LIBSEMANAGE_SITE = https://raw.githubusercontent.com/wiki/SELinuxProject/selinux/files/releases/20180524
>  LIBSEMANAGE_LICENSE = LGPL-2.1+
>  LIBSEMANAGE_LICENSE_FILES = COPYING
>  LIBSEMANAGE_DEPENDENCIES = host-bison host-flex audit libselinux ustr bzip2
> @@ -31,6 +31,7 @@ HOST_LIBSEMANAGE_DEPENDENCIES = host-bison host-audit host-libsepol host-libseli
>  HOST_LIBSEMANAGE_MAKE_OPTS += \
>  	$(HOST_CONFIGURE_OPTS) \
>  	PREFIX=$(HOST_DIR) \
> +	SHLIBDIR=$(HOST_DIR)/lib \

So, I was surprised you had to do this for the host variant... but not
for the target variant. So I checked, and SHLIBDIR is not used at all
by libsemanage, so this change is totally unneeded.

Also, when building host-libsemanage, I got the following build failure:

test -d -L/home/thomas/projets/buildroot/output/host/lib/python2.7/ || install -m 755 -d -L/home/thomas/projets/buildroot/output/host/lib/python2.7/
install: invalid option -- 'L'

This was due to us passing:

  PYTHONLIBDIR="-L/home/thomas/projets/buildroot/output/host/lib/python2.7/"

It turns out that libsemanage 2.7 was totally ignoring PYTHONLIBDIR,
I'm not even sure why we were passing it. However, libsemanage 2.8 now
uses it (since commit
https://github.com/SELinuxProject/selinux/commit/07629c0a9f26e6e9ebb0b2847e09a461512990c9#diff-5680af432ff62be3f5227c99d8d9b7e7),
and needs it to be a path, not a linker flag.

So I've dropped the -L to make it work.

Applied after fixing those two issues.

We *really* need one (or several?) test cases in support/testing/ to
test at least the build of the SELinux stack. Perhaps one with Python
2, one with Python 3, one minimal SELinux (just what is needed on the
target) and one full (with all the host tools).

Best regards,

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

  reply	other threads:[~2018-10-11 20:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 19:37 [Buildroot] [PATCH v3,1/8] libselinux: bump to version 2.8 Fabrice Fontaine
2018-10-11 19:37 ` [Buildroot] [PATCH v3,2/8] libsepol: " Fabrice Fontaine
2018-10-11 19:37 ` [Buildroot] [PATCH v3,3/8] libsemanage: " Fabrice Fontaine
2018-10-11 20:07   ` Thomas Petazzoni [this message]
2018-10-11 19:37 ` [Buildroot] [PATCH v3,4/8] checkpolicy: " Fabrice Fontaine
2018-10-11 19:37 ` [Buildroot] [PATCH v3,5/8] restorecond: " Fabrice Fontaine
2018-10-11 19:37 ` [Buildroot] [PATCH v3,6/8] policycoreutils: " Fabrice Fontaine
2018-10-11 19:37 ` [Buildroot] [PATCH v3,7/8] selinux-python: " Fabrice Fontaine
2018-10-11 19:37 ` [Buildroot] [PATCH v3,8/8] semodule-utils: " Fabrice Fontaine
2018-10-11 20:04 ` [Buildroot] [PATCH v3,1/8] libselinux: " 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=20181011220706.01ff455d@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