From: Apelete Seketeli <apelete@seketeli.net>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-opie][PATCH 0/1] Pull request 20130423
Date: Tue, 23 Apr 2013 23:48:23 +0200 [thread overview]
Message-ID: <cover.1366753073.git.apelete@seketeli.net> (raw)
Hello,
The patch that comes as a follow-up of this message fix a compile
error when building uicmoc-native with GCC-4.7.
The modifications are done on top of the master branch in the
meta-opie layer, and tested by building uicmoc-native from scratch.
Please pull into the meta-opie layer.
The following changes since commit c242efc6ca55772a88602f1f8f94dff697b38430:
layer.conf: use ??= to set variables (2013-03-25 22:42:32 +0000)
are available in the git repository at:
git://seketeli.fr/~apelete/meta-opie.git fix-uicmoc-build
Apelete Seketeli (1):
uicmoc: fix compile issue with GCC-4.7
recipes-qt/uicmoc/uicmoc-2.3.10/gcc4.7.patch | 11 +++++++++++
recipes-qt/uicmoc/uicmoc_2.3.10.bb | 1 +
2 files changed, 12 insertions(+)
create mode 100644 recipes-qt/uicmoc/uicmoc-2.3.10/gcc4.7.patch
--
1.7.10.4
next reply other threads:[~2013-04-23 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 21:48 Apelete Seketeli [this message]
2013-04-23 21:48 ` [meta-opie][PATCH 1/1] uicmoc: fix compile issue with GCC-4.7 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.1366753073.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