From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH 2/2] qt5-plugin-generic-vboxtouch: add -Wno-narrowing to fix build with gcc-5.2
Date: Wed, 5 Aug 2015 14:37:04 +0200 [thread overview]
Message-ID: <20150805123704.GA2452@jama> (raw)
In-Reply-To: <CAMKF1sqPdo2ByELw+pCkVPGtYHRXVJAWEo8d3tONXtKcyJmu3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]
On Tue, Aug 04, 2015 at 04:05:26PM -0700, Khem Raj wrote:
> On Mon, Aug 3, 2015 at 12:00 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> > recipes-qt/qt5/qt5-plugin-generic-vboxtouch_git.bb | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/recipes-qt/qt5/qt5-plugin-generic-vboxtouch_git.bb b/recipes-qt/qt5/qt5-plugin-generic-vboxtouch_git.bb
> > index 5352d15..2676bdd 100644
> > --- a/recipes-qt/qt5/qt5-plugin-generic-vboxtouch_git.bb
> > +++ b/recipes-qt/qt5/qt5-plugin-generic-vboxtouch_git.bb
> > @@ -9,12 +9,15 @@ LIC_FILES_CHKSUM = " \
> > file://evdevmousehandler.cpp;beginline=1;endline=40;md5=9081062f6e7f74b6e62ad7ecee4a71be \
> > "
> >
> > -PV = "1.0+gitr${SRCPV}"
> > +PV = "1.1.3+gitr${SRCPV}"
> >
> > DEPENDS = "qtbase"
> >
> > +# Needed with gcc-5.2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65801
>
> this comment it wrong. It should have said needed with gcc5 < 5.2
>
> > +CXXFLAGS += "-Wno-narrowing"
>
> we now have 5.2 in OE-Core and its fixed in 5.2, Can you try to remove it ?
I wrote this change, because it was failing with gcc-5.2 (I don't
remember if it was failing with 5.1 as well).
>
> > +
> > SRC_URI = "git://github.com/nemomobile/qt5-plugin-generic-vboxtouch.git"
> > -SRCREV = "7d7a6dfd501c43687e7bb110610cac5f7c9abd4b"
> > +SRCREV = "d613ad1cc64d7a6a9b38df4d49146170be6876aa"
> > S = "${WORKDIR}/git/vboxtouch"
> >
> > inherit qmake5
> > --
> > 2.5.0
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-08-05 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 14:16 [meta-qt5][WIP][PATCH 1/3] licenses: Add LGPL_Exception texts and reference them from LICENSE Martin Jansa
2015-04-17 14:16 ` [meta-qt5][WIP][PATCH 2/3] git-recipes: upgrade to latest revision in 5.4 branch Martin Jansa
2015-04-17 14:16 ` [meta-qt5][WIP][PATCH 3/3] WIP: recipes-git: upgrade to latest revision in 5.5 branch Martin Jansa
2015-08-03 19:00 ` [meta-qt5][PATCH 1/2] recipes-git: upgrade to 5.5 Martin Jansa
2015-08-03 19:00 ` [meta-qt5][PATCH 2/2] qt5-plugin-generic-vboxtouch: add -Wno-narrowing to fix build with gcc-5.2 Martin Jansa
2015-08-04 23:05 ` Khem Raj
2015-08-05 12:37 ` Martin Jansa [this message]
2015-08-06 3:30 ` Khem Raj
2015-08-06 3:31 ` Khem Raj
2015-08-03 19:05 ` [meta-qt5][PATCH 1/2] recipes-git: upgrade to 5.5 Martin Jansa
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=20150805123704.GA2452@jama \
--to=martin.jansa@gmail.com \
--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