From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/1] kernel.bbclass: remove explicit version.h target
Date: Thu, 18 Oct 2012 10:47:04 -0400 [thread overview]
Message-ID: <cover.1350571171.git.bruce.ashfield@windriver.com> (raw)
Hi all,
I'm doing a quick RFC on a patch to get 3.7 based kernels building
again.
The patch has the details on the kernel commits that have moved
version.h around, which breaks our builds due to an explicit reference
in kernel.bbclass.
I thought about making the call conditional, but as the patch says,
this introduces a bit more complexity where it might not be
required. Removing the reference to version.h fixes the build, and
didn't break any of my older kernel builds (2.6.39, 3.0, 3.2, 3.4)
while still producing version.h.
I can't locate the original reason that version.h was being directly
built, so that's why this is a RFC. I'm hoping someone will yell if
this breaks a use case that I don't know about.
This is stacked on top of my yocto master branch, since it was a
RFC. I can rebase onto oe-core, or master under test as appropriate.
Cheers,
Bruce
The following changes since commit e6e2b9bd66100c078c029ca7e34829cf1dfb5490:
documentation: poky-ref-manual - edits to MACHINE type variables. (2012-10-18 12:15:04 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
kernel.bbclass: remove explicit version.h target
meta/classes/kernel.bbclass | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-10-18 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 14:47 Bruce Ashfield [this message]
2012-10-18 14:47 ` [PATCH 1/1] kernel.bbclass: remove explicit version.h target Bruce Ashfield
2012-10-18 14:53 ` Darren Hart
2012-10-18 15:12 ` Richard Purdie
2012-10-18 16:35 ` Bruce Ashfield
2012-10-19 21:24 ` Saul Wold
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.1350571171.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox