From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: "radek.dostal@streamunlimited.com"
<radek.dostal@streamunlimited.com>,
"andriy.danylovskyy@streamunlimited.com"
<andriy.danylovskyy@streamunlimited.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [warrior] [meta-qt4] 3rdparty: javascriptcore: JITStubs.cpp: allow builds of JavaScriptCore with gcc v8
Date: Wed, 20 Nov 2019 21:06:08 +1300 [thread overview]
Message-ID: <29155136.VOVqtgXEB2@shodan> (raw)
In-Reply-To: <6a6629bc-00c4-7229-1c38-0096c3a5b0c3@topic.nl>
Hi Mike
On Wednesday, 20 November 2019 9:00:10 PM NZDT Mike Looijmans wrote:
> I ran into this issue yesterday, and this patch solves the compilation on
> warrior. However, it's a patch for Qt itself, and not for OE.
>
> Is there already a warrior patch in the making, or should I submit one?
Quentin sent one yesterday (with the same subject). If you could give it a try
and confirm it fixes the failure that would be great.
Thanks
Paul
--
Paul Eggleton
Intel System Software Products
next prev parent reply other threads:[~2019-11-20 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 12:37 [warrior] [meta-qt4] 3rdparty: javascriptcore: JITStubs.cpp: allow builds of JavaScriptCore with gcc v8 Quentin Schulz
2019-11-20 8:00 ` Mike Looijmans
2019-11-20 8:06 ` Paul Eggleton [this message]
2019-11-20 8:36 ` Quentin Schulz
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.1f62d4fc-3660-4f61-b518-4309c3d785b7@emailsignatures365.codetwo.com>
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.5728a17c-b790-49b0-bf2c-61576ca07c85@emailsignatures365.codetwo.com>
2019-12-05 14:48 ` [warrior] [meta-qt4] qt4-xqq fails to compile on arm64 Mike Looijmans
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=29155136.VOVqtgXEB2@shodan \
--to=paul.eggleton@linux.intel.com \
--cc=andriy.danylovskyy@streamunlimited.com \
--cc=mike.looijmans@topic.nl \
--cc=radek.dostal@streamunlimited.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.