From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected
Date: Tue, 19 Jan 2016 18:22:48 +0100 [thread overview]
Message-ID: <20160119172248.GA3360@free.fr> (raw)
In-Reply-To: <87powx3le0.fsf@dell.be.48ers.dk>
Peter, Thomas, All,
On 2016-01-19 11:37 +0100, Peter Korsgaard spake thusly:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> > 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 ? :-)
>
> Then linux-patch, we afaik don't need a configured linux kernel to make headers_install
Indeed, that's a good idea. We propbably could use set:
LINUX_HEADERS_PATCH_DEPENDENCIES = linux
which will guarantee that linux is patched before linux-headers is
configured (in the Buildroot sense).
Then, we basically could do:
define LINUX_HEADERS_INSTALL_STAGING_CMDS
$(MAKE) -C $(LINUX_DIR) INSTALL_HDR_PATH=$(STAGING_DIR)/usr
endef
(with extra variables as done today, of course...)
There, we can use $(LINUX_DIR) because the macro is only expanded in a
make rule, so we should be fine. Hopefully...
I can have a look at this.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-01-19 17:22 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
2016-01-19 10:37 ` Peter Korsgaard
2016-01-19 17:22 ` Yann E. MORIN [this message]
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=20160119172248.GA3360@free.fr \
--to=yann.morin.1998@free.fr \
--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