From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCHv2] fix build of qtwebengine if qtbase has no accessibility
Date: Thu, 5 Mar 2015 15:04:03 +0100 [thread overview]
Message-ID: <20150305140403.GR2337@jama> (raw)
In-Reply-To: <3137890.DjIWZ5FYZB@fridolin>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Wed, Mar 04, 2015 at 09:47:23AM +0100, Stephan Binner wrote:
> On Wednesday 04 March 2015 03:25:46 Martin Jansa wrote:
>
> > > ++else
> > This doesn't look right and also fails to build.
>
> Yeah, dunno how I messed that up yesterday evening. :-/
I've sent additional patch to fix building with accessibility enabled.
Please get it merged in upstream, because your patch seems to be broken
in upstream 5.4 as well.
Regards,
> I will try to get the backport reviewed and integrated into 5.4 branch
> upstream and then will post patch with proper branch annotation etc.
>
> Regards,
> Stephan
>
> --
> _______________________________________________
> 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-03-05 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:25 [meta-qt5][PATCH] fix build of qtwebengine if qtbase has no accessibility Stephan Binner
2015-03-03 18:28 ` Martin Jansa
2015-03-03 19:40 ` [meta-qt5][PATCHv2] " Martin Jansa
2015-03-04 2:25 ` Martin Jansa
2015-03-04 8:47 ` Stephan Binner
2015-03-05 14:04 ` Martin Jansa [this message]
2015-03-06 7:27 ` Stephan Binner
2015-03-05 14:00 ` [meta-qt5][PATCHv1] qtwebengine: Fix build with accessibility enabled 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=20150305140403.GR2337@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 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.