From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected
Date: Tue, 19 Jan 2016 11:31:54 +0100 [thread overview]
Message-ID: <20160119113154.2f4613fc@free-electrons.com> (raw)
In-Reply-To: <87twm93lsb.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Tue, 19 Jan 2016 11:29:08 +0100, Peter Korsgaard wrote:
> Well, linux-headers doesn't need to do much - So with a bit of care I
> think you can.
>
> E.G. something like (completely untested):
>
> ifeq ($(LINUX_HEADERS_FROM_KERNEL),y)
> # no source
> LINUX_HEADERS_SOURCE =
> LINUX_HEADERS_DEPENDENCIES += linux-configure
The configure step of a package depends on the dependencies of that
package. So linux-configure depends on toolchain. And toolchain depends
on linux-headers -> recursive dependency.
Another try ? :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-19 10:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 17:17 [Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected Karoly Kasza
2015-03-04 22:37 ` Thomas Petazzoni
2015-03-12 14:07 ` Алексей Бродкин
2016-01-09 17:29 ` Yann E. MORIN
2016-01-18 9:21 ` Peter Korsgaard
2016-01-18 21:47 ` Yann E. MORIN
2016-01-18 21:50 ` Peter Korsgaard
2016-01-18 22:03 ` Thomas Petazzoni
2016-01-18 22:13 ` Yann E. MORIN
2016-01-18 22:21 ` Thomas Petazzoni
2016-01-18 22:21 ` Peter Korsgaard
2016-01-18 22:24 ` Thomas Petazzoni
2016-01-19 8:21 ` Peter Korsgaard
2016-01-19 10:18 ` Thomas Petazzoni
2016-01-19 10:29 ` Peter Korsgaard
2016-01-19 10:31 ` Thomas Petazzoni [this message]
2016-01-19 10:37 ` Peter Korsgaard
2016-01-19 17:22 ` Yann E. MORIN
2016-01-18 17:42 ` Arnout Vandecappelle
2016-01-19 7:25 ` Алексей Бродкин
2016-01-19 20:10 ` Yann E. MORIN
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=20160119113154.2f4613fc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.