From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] selinux-python: add patch to make the build process more standard
Date: Wed, 17 Jan 2018 13:55:23 +0100 [thread overview]
Message-ID: <20180117135523.4728bcad@windsurf> (raw)
In-Reply-To: <20180117093134.18230-1-marcus.folkesson@gmail.com>
Hello,
On Wed, 17 Jan 2018 10:31:34 +0100, Marcus Folkesson wrote:
> Patch the Makefiles to make PREFIX and DESTDIR follow standard
> semantics to get rid of DESTDIR during compile time in
> selinux-python.mk.
>
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
Thanks for this patch. However...
> ---
> ...build-follow-standard-semantics-for-DESTD.patch | 113 +++++++++++++++++++++
> package/selinux-python/selinux-python.mk | 2 +-
> 2 files changed, 114 insertions(+), 1 deletion(-)
> create mode 100644 package/selinux-python/0001-python-build-follow-standard-semantics-for-DESTD.patch
>
> diff --git a/package/selinux-python/0001-python-build-follow-standard-semantics-for-DESTD.patch b/package/selinux-python/0001-python-build-follow-standard-semantics-for-DESTD.patch
> new file mode 100644
> index 0000000000..82c3b06086
> --- /dev/null
> +++ b/package/selinux-python/0001-python-build-follow-standard-semantics-for-DESTD.patch
> @@ -0,0 +1,113 @@
> +diff -durN python.orig/audit2allow/Makefile python/audit2allow/Makefile
> +--- python.orig/audit2allow/Makefile 2017-08-04 15:31:00.000000000 +0200
> ++++ python/audit2allow/Makefile 2018-01-17 09:44:35.659573123 +0100
.. this patch lacks a description and Signed-off-by, and should be
Git-formatted.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-17 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 9:31 [Buildroot] [PATCH] selinux-python: add patch to make the build process more standard Marcus Folkesson
2018-01-17 12:55 ` Thomas Petazzoni [this message]
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=20180117135523.4728bcad@windsurf \
--to=thomas.petazzoni@free-electrons.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