From: Chris PeBenito <pebenito@ieee.org>
To: David Sugar <dsugar@tresys.com>,
"selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH] Update CUSTOM_BUILDOPT
Date: Sat, 27 Oct 2018 15:11:20 -0400 [thread overview]
Message-ID: <a28aefe9-ca7c-f7ad-464a-c45539498a84@ieee.org> (raw)
In-Reply-To: <20181027161252.11199-1-dsugar@tresys.com>
On 10/27/2018 12:13 PM, David Sugar wrote:
> Have Makefile include CUSTOM_BUILDOPT in generated build.conf
> Update Makefile.devel to pass CUSTOM_BUILDOPT while building module
>
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
> Makefile | 1 +
> support/Makefile.devel | 4 ++++
> 2 files changed, 5 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index 22e31392..57d297c9 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -545,6 +545,7 @@ endif
> $(verbose) echo "MONOLITHIC ?= n" >> $(headerdir)/build.conf
> $(verbose) echo "DIRECT_INITRC ?= $(DIRECT_INITRC)" >> $(headerdir)/build.conf
> $(verbose) echo "SYSTEMD ?= $(SYSTEMD)" >> $(headerdir)/build.conf
> + $(verbose) echo "CUSTOM_BUILDOPT ?= $(CUSTOM_BUILDOPT)" >> $(headerdir)/build.conf
> $(verbose) echo "override UBAC := $(UBAC)" >> $(headerdir)/build.conf
> $(verbose) echo "override MLS_SENS := $(MLS_SENS)" >> $(headerdir)/build.conf
> $(verbose) echo "override MLS_CATS := $(MLS_CATS)" >> $(headerdir)/build.conf
> diff --git a/support/Makefile.devel b/support/Makefile.devel
> index bcca2d98..f3daca11 100644
> --- a/support/Makefile.devel
> +++ b/support/Makefile.devel
> @@ -70,6 +70,10 @@ ifeq "$(UBAC)" "y"
> M4PARAM += -D enable_ubac
> endif
>
> +ifneq "$(CUSTOM_BUILDOPT)" ""
> + M4PARAM += $(foreach opt,$(CUSTOM_BUILDOPT),-D $(opt))
> +endif
> +
> # default MLS/MCS sensitivity and category settings.
> MLS_SENS ?= 16
> MLS_CATS ?= 1024
Merged.
--
Chris PeBenito
prev parent reply other threads:[~2018-10-27 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 16:13 [PATCH] Update CUSTOM_BUILDOPT David Sugar
2018-10-27 19:11 ` Chris PeBenito [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=a28aefe9-ca7c-f7ad-464a-c45539498a84@ieee.org \
--to=pebenito@ieee.org \
--cc=dsugar@tresys.com \
--cc=selinux-refpolicy@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).