public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kbuild@vger.kernel.org, Peter Foley <pefoley2@pefoley.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: make samples depend on headers_install
Date: Fri, 22 Jul 2016 13:59:40 +0200	[thread overview]
Message-ID: <57920AAC.8020304@suse.com> (raw)
In-Reply-To: <20160704143949.2357806-1-arnd@arndb.de>

On 2016-07-04 16:39, Arnd Bergmann wrote:
> Olof's build test setup keeps failing to compile arm64 kernels
> because of a toolchain that uses outdated kernel headers:
> 
> /work/build/batch/samples/seccomp/bpf-fancy.c:13:27: fatal error: linux/seccomp.h: No such file or directory
> 
> This is of course something he could change, but it also indicates
> that others may run into the same problem. Running 'make headers_install'
> avoids the issue by ensuring that the kernel headers are put into
> the $(objdir)/usr/include path before we build the samples.
> 
> The same problem happened for the Documentation build in the
> past and was fixed up with commit 8e2faea877eb ("Make Documenation
> depend on headers_install"). This adds an identical Makefile dependency
> for the samples/ subdirectory.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to kbuild.git#kbuild.

Michal


      reply	other threads:[~2016-07-22 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 14:39 [PATCH] kbuild: make samples depend on headers_install Arnd Bergmann
2016-07-22 11:59 ` Michal Marek [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=57920AAC.8020304@suse.com \
    --to=mmarek@suse.com \
    --cc=arnd@arndb.de \
    --cc=jkosina@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pefoley2@pefoley.com \
    /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