From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: don't add to toolchain dependency
Date: Mon, 22 Feb 2016 13:19:01 +0100 [thread overview]
Message-ID: <20160222131901.3baa956e@free-electrons.com> (raw)
In-Reply-To: <1456141244-624-1-git-send-email-gustavo@zacarias.com.ar>
Gustavo,
Cc'ing Yann.
On Mon, 22 Feb 2016 08:40:44 -0300, Gustavo Zacarias wrote:
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 7e20255..dc1c79e 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -8,6 +8,9 @@ LINUX_VERSION = $(call qstrip,$(BR2_LINUX_KERNEL_VERSION))
> LINUX_LICENSE = GPLv2
> LINUX_LICENSE_FILES = COPYING
>
> +# Used when BR2_KERNEL_HEADERS_AS_KERNEL=y
> +LINUX_ADD_TOOLCHAIN_DEPENDENCY = NO
This is annoying, because we *do* need the toolchain dependency to
build the Linux kernel. I think we would rather need to do:
LINUX_HEADERS_PATCH_DEPENDENCIES = linux-patch
Though I'm not sure how great it is to have a non-package listed in the
<pkg>_DEPENDENCIES variable. Surely it might break graph-depends and
other similar tooling.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-22 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 11:40 [Buildroot] [PATCH] linux: don't add to toolchain dependency Gustavo Zacarias
2016-02-22 12:19 ` Thomas Petazzoni [this message]
2016-02-23 23:55 ` Arnout Vandecappelle
2016-02-24 13:02 ` Gustavo Zacarias
2016-02-24 14:04 ` Thomas Petazzoni
2016-03-01 8:47 ` Peter Korsgaard
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=20160222131901.3baa956e@free-electrons.com \
--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