From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libselinux: fix build with python 3.8
Date: Mon, 21 Oct 2019 10:06:01 +0200 [thread overview]
Message-ID: <20191021100601.0b88caa0@windsurf.home> (raw)
In-Reply-To: <20191020203119.99538-1-james.hilliard1@gmail.com>
On Sun, 20 Oct 2019 14:31:19 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> diff --git a/package/libselinux/libselinux.mk b/package/libselinux/libselinux.mk
> index c707c8a25e..75f01a84b7 100644
> --- a/package/libselinux/libselinux.mk
> +++ b/package/libselinux/libselinux.mk
> @@ -33,7 +33,7 @@ endif
> ifeq ($(BR2_PACKAGE_PYTHON)$(BR2_PACKAGE_PYTHON3),y)
> ifeq ($(BR2_PACKAGE_PYTHON3),y)
> LIBSELINUX_DEPENDENCIES += python3 host-swig
> -LIBSELINUX_PYINC = -I$(STAGING_DIR)/usr/include/python$(PYTHON3_VERSION_MAJOR)m
> +LIBSELINUX_PYINC = -I$(STAGING_DIR)/usr/include/python$(PYTHON3_VERSION_MAJOR)
Considering the number of packages that hardcode this path, perhaps we
should have a variable provided by some common code, so that if it
changes again in the future, we don't have to chase down multiple
packages ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-21 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 20:31 [Buildroot] [PATCH 1/1] package/libselinux: fix build with python 3.8 James Hilliard
2019-10-21 8:06 ` Thomas Petazzoni [this message]
2019-10-21 15:18 ` James Hilliard
2019-10-21 19:06 ` Thomas Petazzoni
2019-10-21 19:25 ` James Hilliard
2019-10-21 21:18 ` Thomas Petazzoni
2019-10-21 21:42 ` James Hilliard
2019-10-22 7:40 ` Thomas Petazzoni
2019-10-22 7:45 ` Thomas Petazzoni
2019-10-22 9:10 ` Thomas Petazzoni
2019-10-25 9:28 ` 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=20191021100601.0b88caa0@windsurf.home \
--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