[oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

[Martin Jansa]

I've fixed the gcc7 + security_flags.inc issues in 5.8.0, that's now merged
in master.

Then I've rebased Samuli's upgrade to 5.9.0 to build on top of that and
added another upgrade to 5.9.2. That's currently in master-next branch.

But there is still this issue with qemux86 on x86_64 builders, so I'm not
going to merge this all until it's fixed in qtwebengine's chromium.
https://bugreports.qt.io/browse/QTBUG-59504
maybe we could just revert:
https://codereview.qt-project.org/#/c/189044/2/src/buildtools/configure_target.pro
but someone with deeper mksnapshot knowledge should confirm if the
requirement for multilib toolchain isn't valid after all, some of the
comments make some sense to me, so maybe the meta-browser fix actually
breaks mksnapshot, but nobody noticed it as we don't have good tests for it
in runtime.

Regards,

On Fri, Jun 30, 2017 at 1:43 PM, Andreas Müller <
schnitzeltony at googlemail.com> wrote:

> On Fri, Jun 23, 2017 at 2:58 AM, Trevor Woerner <twoerner at gmail.com>
> wrote:
> > On Thu, Jun 22, 2017 at 3:35 PM, Denys Dmytriyenko <denis at denix.org>
> wrote:
> >> On Thu, Jun 15, 2017 at 01:25:12AM -0400, Trevor Woerner wrote:
> >>> On Fri, Jun 9, 2017 at 4:16 AM, Martin Jansa <martin.jansa at gmail.com>
> wrote:
> >>> > Then why does it work for chromium which used to have the same issue?
> >>>
> >>> https://github.com/OSSystems/meta-browser/blob/master/
> recipes-browser/chromium/chromium/chromium/m32.patch
> >>
> >> Hmm, I'm wondering who comes up with such nonsense upstream that we
> have to
> >> patch it out? Is it due to laziness or are there some real limitations?
> >
> > Unfortunately genius and insanity are virtually indistinguishable from
> > each other ;-)
> > --
> Is anybody still working on Qt5.9 (or better on 5.9.1 which just
> arrived)? I want to avoid double efforts fixing qtwebengine/gcc7 on
> 5.8 or creating patches for 5.9.1 based on this series.
>
> Andreas
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>