From: Apelete Seketeli <apelete@seketeli.net>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-handheld][PATCH v3 0/1] Pull request 20130408
Date: Mon, 8 Apr 2013 23:18:21 +0200 [thread overview]
Message-ID: <cover.1365455095.git.apelete@seketeli.net> (raw)
Hello,
On Sunday 07 April 2013, Apelete Seketeli wrote:
> On Friday 05 April 2013, Apelete Seketeli wrote:
> > Following the patches I sent to the meta-handheld layer a few days ago
> > to add machine support for the Ben Nanonote, I found out that the
> > corresponding kernel recipe fails to build on oe-core (builds fine on
> > oe-classic).
> > A few settings were missing and, more importantly, the version of gcc
> > in oe-core seems to enable the -Wunused-but-set-variable switch, which
> > makes it error on many variables that were indeed 'unused but
> > set'. After trying to solve this issue the easy way, by setting
> > 'CFLAGS=-Wno-error=unused-but-set-variable -Wno-error=unused-but-set-parameter'
> > to no avail, I chose to annotate the aforementioned variables in the
> > kernel code with __attribute__((__unused__)).
> >
> > The patches that come as a follow-up of this message are what it's all
> > about; sorry for the inconvenience in the first place.
>
> I took the time to fix the patch for the GCC 4.6 build issue. Instead
> of just fixing the issue on my own, I looked at how it was done in the
> mainline kernel and backported the fixes through a new patch named
> fix-gcc-4.6.0-build-errors.patch; this approach seems more logical to
> me.
> While I was at it, also removed "[PATCH 2/2] ben-nanonote: add
> DEFAULTTUNE to machine configuration" from the patchset, following
> Paul's advice.
Added a header to the "fix-gcc-4.6.0-build-errors.patch" kernel patch,
describing the changes and stating the Upstream-Status.
Tested by building linux-jlime-ben-nanonote from scratch on top of
master branch.
Please pull into meta-handheld.
The following changes since commit 913735dce388f660dfbbe288ed736e12ed48c8d8:
linux-yocto-tiny-kexecboot_3.2: removed unused, non-working MTD-RW patch (2013-04-06 00:25:08 +0100)
are available in the git repository at:
git://seketeli.fr/~apelete/meta-handheld.git fix-nn-kernel-build
Apelete Seketeli (1):
linux-jlime-ben-nanonote: fix GCC-4.6 build errors
.../fix-gcc-4.6.0-build-errors.patch | 124 ++++++++++++++++++++
.../linux/linux-jlime-ben-nanonote_2.6.36.bb | 5 +-
2 files changed, 128 insertions(+), 1 deletion(-)
create mode 100644 recipes-kernel/linux/linux-jlime-ben-nanonote-2.6.36/fix-gcc-4.6.0-build-errors.patch
--
1.7.10.4
next reply other threads:[~2013-04-08 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 21:18 Apelete Seketeli [this message]
2013-04-08 21:18 ` [meta-handheld][PATCH v3 1/1] linux-jlime-ben-nanonote: fix GCC-4.6 build errors Apelete Seketeli
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.1365455095.git.apelete@seketeli.net \
--to=apelete@seketeli.net \
--cc=openembedded-devel@lists.openembedded.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