From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: yocto@yoctoproject.org
Subject: [meta-qt4][PATCH] qt4: Fix build with moc4 and boost
Date: Fri, 7 Jul 2017 12:30:58 +0200 [thread overview]
Message-ID: <20170707103058.976-1-ricardo.ribalda@gmail.com> (raw)
Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
---
recipes-qt4/qt4/qt4-4.8.7.inc | 1 +
...everywhere-opensource-src-4.8.6-QTBUG-22829.patch | 20 ++++++++++++++++++++
recipes-qt4/qt4/qt4-native.inc | 1 +
3 files changed, 22 insertions(+)
create mode 100644 recipes-qt4/qt4/qt4-4.8.7/qt-everywhere-opensource-src-4.8.6-QTBUG-22829.patch
diff --git a/recipes-qt4/qt4/qt4-4.8.7.inc b/recipes-qt4/qt4/qt4-4.8.7.inc
index 16b22a808a62..4bade85abe98 100644
--- a/recipes-qt4/qt4/qt4-4.8.7.inc
+++ b/recipes-qt4/qt4/qt4-4.8.7.inc
@@ -34,6 +34,7 @@ SRC_URI = "http://download.qt-project.org/official_releases/qt/4.8/${PV}/qt-ever
file://g++.conf \
file://linux.conf \
file://fix-for-mips-n32.patch \
+ file://qt-everywhere-opensource-src-4.8.6-QTBUG-22829.patch \
"
SRC_URI[md5sum] = "d990ee66bf7ab0c785589776f35ba6ad"
diff --git a/recipes-qt4/qt4/qt4-4.8.7/qt-everywhere-opensource-src-4.8.6-QTBUG-22829.patch b/recipes-qt4/qt4/qt4-4.8.7/qt-everywhere-opensource-src-4.8.6-QTBUG-22829.patch
new file mode 100644
index 000000000000..2b9da641e42b
--- /dev/null
+++ b/recipes-qt4/qt4/qt4-4.8.7/qt-everywhere-opensource-src-4.8.6-QTBUG-22829.patch
@@ -0,0 +1,20 @@
+Error described on: https://bugzilla.redhat.com/show_bug.cgi?id=1396755
+
+Upstream-Status: Backport
+diff -up qt-everywhere-opensource-src-4.8.7/src/tools/moc/main.cpp.QTBUG-22829 qt-everywhere-opensource-src-4.8.7/src/tools/moc/main.cpp
+--- qt-everywhere-opensource-src-4.8.7/src/tools/moc/main.cpp.QTBUG-22829 2015-05-07 09:14:44.000000000 -0500
++++ qt-everywhere-opensource-src-4.8.7/src/tools/moc/main.cpp 2016-12-08 12:32:46.638962448 -0600
+@@ -188,8 +188,12 @@ int runMoc(int _argc, char **_argv)
+ pp.macros["Q_MOC_RUN"];
+ pp.macros["__cplusplus"];
+
+- // Workaround a bug while parsing the boost/type_traits/has_operator.hpp header. See QTBUG-22829
++ // Workaround a bugs while parsing some boost headers. See QTBUG-22829
+ pp.macros["BOOST_TT_HAS_OPERATOR_HPP_INCLUDED"];
++ pp.macros["BOOST_LEXICAL_CAST_INCLUDED"];
++ pp.macros["BOOST_NEXT_PRIOR_HPP_INCLUDED"];
++ pp.macros["BOOST_TYPE_TRAITS_HPP"];
++ pp.macros["_SYS_SYSMACROS_H_OUTER"];
+
+ QByteArray filename;
+ QByteArray output;
diff --git a/recipes-qt4/qt4/qt4-native.inc b/recipes-qt4/qt4/qt4-native.inc
index 5a873de4e8f4..c0d6b3cb4cd4 100644
--- a/recipes-qt4/qt4/qt4-native.inc
+++ b/recipes-qt4/qt4/qt4-native.inc
@@ -21,6 +21,7 @@ SRC_URI = "http://download.qt-project.org/official_releases/qt/4.8/${PV}/qt-ever
file://gcc-6.patch \
file://g++.conf \
file://linux.conf \
+ file://qt-everywhere-opensource-src-4.8.6-QTBUG-22829.patch \
"
UPSTREAM_CHECK_URI = "http://download.qt.io/official_releases/qt/4.8/"
--
2.13.2
next reply other threads:[~2017-07-07 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 10:30 Ricardo Ribalda Delgado [this message]
2017-07-17 14:04 ` [meta-qt4][PATCH] qt4: Fix build with moc4 and boost Alexander Kanavin
2017-07-17 14:11 ` Ricardo Ribalda Delgado
2017-07-17 14:11 ` Alexander Kanavin
2017-07-17 14:12 ` Ricardo Ribalda Delgado
2017-07-17 14:12 ` Alexander Kanavin
2017-07-17 14:16 ` Ricardo Ribalda Delgado
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=20170707103058.976-1-ricardo.ribalda@gmail.com \
--to=ricardo.ribalda@gmail.com \
--cc=yocto@yoctoproject.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.