From: Paul Moore <paul@paul-moore.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Dominick Grift <dominick.grift@defensec.nl>
Subject: Re: linux-next: build failure after merge of the selinux tree
Date: Tue, 19 Mar 2019 13:11:10 -0400 [thread overview]
Message-ID: <CAHC9VhQB2OECVhgQNmwikBNs=RwC+Of7kUFLfUze+Dp3WYu2Gg@mail.gmail.com> (raw)
In-Reply-To: <20190319124034.13ff6044@canb.auug.org.au>
On Mon, Mar 18, 2019 at 9:40 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the selinux tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from /home/sfr/next/next/scripts/selinux/mdp/mdp.c:35:
> /home/sfr/next/next/include/linux/kconfig.h:5:10: fatal error: generated/autoconf.h: No such file or directory
> #include <generated/autoconf.h>
> ^~~~~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> e37c1877ba5b ("scripts/selinux: modernize mdp")
>
> I have used the selinux tree from next-20190318 for today.
Thanks for the report, I just merged the fix below into selinux/next:
commit ccd19d4cafaaf36132c372e77ee9304b707c1e70
Author: Stephen Smalley <sds@tycho.nsa.gov>
Date: Tue Mar 19 09:21:06 2019 -0400
scripts/selinux: fix build
We need to add the object tree include directory to the include path
for building mdp in order to pick up generated/autoconf.h. Otherwise,
make O=/path/to/objtree breaks.
Fixes: e37c1877ba5b ("scripts/selinux: modernize mdp")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
Signed-off-by: Paul Moore <paul@paul-moore.com>
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2019-03-19 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 1:40 linux-next: build failure after merge of the selinux tree Stephen Rothwell
2019-03-19 17:11 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-27 2:10 Stephen Rothwell
2024-03-27 13:13 ` Paul Moore
2021-10-05 3:10 Stephen Rothwell
2021-10-05 13:57 ` Paul Moore
2019-12-10 1:40 Stephen Rothwell
2019-12-10 2:25 ` Paul Moore
2019-04-03 1:22 Stephen Rothwell
2019-04-03 1:25 ` Paul Moore
2017-05-22 2:48 Stephen Rothwell
2017-05-22 21:12 ` Paul Moore
2017-05-22 21:16 ` Daniel Jurgens
2017-01-10 1:27 Stephen Rothwell
2017-01-11 3:11 ` Paul Moore
2017-02-10 2:50 ` Stephen Rothwell
2017-02-10 12:34 ` Paul Moore
2012-01-05 4:24 Stephen Rothwell
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='CAHC9VhQB2OECVhgQNmwikBNs=RwC+Of7kUFLfUze+Dp3WYu2Gg@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=dominick.grift@defensec.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=sfr@canb.auug.org.au \
/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).