From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: don't add to toolchain dependency
Date: Wed, 24 Feb 2016 00:55:41 +0100 [thread overview]
Message-ID: <56CCF17D.2030508@mind.be> (raw)
In-Reply-To: <20160222131901.3baa956e@free-electrons.com>
On 02/22/16 13:19, Thomas Petazzoni wrote:
> 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
Well, _PATCH_DEPENDENCIES already does that:
# Order-only dependency
$$($(2)_TARGET_PATCH): | $$(patsubst %,%-patch,$$($(2)_FINAL_PATCH_DEPENDENCIES))
The problem identified by Gustavo doesn't happen in a normal build, it's only
when you do make source. That's because for source we use:
$(1)-all-source: $(1)-source
$(1)-all-source: $$(foreach
p,$$($(2)_FINAL_ALL_DEPENDENCIES),$$(p)-all-source)
I have to think a bit more about possible solutions. But the good thing is that
it's less important: a normal build will still work without warning, and make
source will also still work and have all the packages, it just has a warning
that is not so nice. So if it doesn't get fixed for 2016.02 it's no disaster.
Regards,
Arnout
>
> 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
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-23 23:55 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
2016-02-23 23:55 ` Arnout Vandecappelle [this message]
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=56CCF17D.2030508@mind.be \
--to=arnout@mind.be \
--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