From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] kernel: provide scripts in the sysroot
Date: Thu, 3 Oct 2013 20:02:20 -0400 [thread overview]
Message-ID: <cover.1380844647.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Khem noticed that he was seeing frequent "modpost missing" messages in his
logs for out of tree builds. This is due to the missing kernel scripts, which
we remove for packaging reasons.
Rather than jiggle the kernel install rule itself, experience shows that just
heading to the sysroot and re-creating the scripts is easy enough to do.
[PATCH 1/1] kernel: restore scripts in the sysroot
When building against the sysroot, out of tree modules can require modpost
and other utilities normally found in the kernel's scripts directory. For
the kernel source in the staging dir, these scripts have been removed to
avoid mixing archiectures when packaging kernel-dev (among other things).
Rather than further complicate the kernel's install rule, or its packaging,
we can jump into the sysroot and restore the scripts by building them, hence
making them available to packages that need them.
Khem confirmed that the same fix worked for him.
cc: Khem Raj <raj.khem@gmail.com>
Cheers,
Bruce
The following changes since commit e7a20238dc73bb449f15feaf0dead51daf796184:
maintainers: Add some maintainers (2013-10-03 10:22:30 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-oe
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe
Bruce Ashfield (1):
kernel: restore scripts in the sysroot
meta/classes/kernel.bbclass | 8 ++++++++
1 file changed, 8 insertions(+)
--
1.8.1.2
next reply other threads:[~2013-10-04 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 0:02 Bruce Ashfield [this message]
2013-10-04 0:02 ` [PATCH 1/1] kernel: restore scripts in the sysroot Bruce Ashfield
2013-10-04 0:58 ` Khem Raj
2013-10-04 0:59 ` Bruce Ashfield
2013-10-04 7:46 ` Richard Purdie
2013-10-04 12:42 ` Bruce Ashfield
2013-10-04 20:23 ` Khem Raj
2013-10-07 5:02 ` Bruce Ashfield
2013-10-07 9:58 ` Richard Purdie
2013-10-07 15:20 ` Bruce Ashfield
2013-10-07 16:18 ` Richard Purdie
2013-10-07 16:20 ` Bruce Ashfield
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=cover.1380844647.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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.