From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] qt5: bump latest version to 5.12.1
Date: Mon, 11 Feb 2019 21:47:55 +0100 [thread overview]
Message-ID: <20190211214755.3ba7bbb6@gmx.net> (raw)
In-Reply-To: <20190205223104.52ac8996@gmx.net>
On Tue, 5 Feb 2019 22:31:04 +0100, Peter Seiderer <ps.report@gmx.net> wrote:
> On Tue, 5 Feb 2019 22:27:07 +0100, Peter Seiderer <ps.report@gmx.net> wrote:
>
> > qt5base:
> > - removed 0002-double-conversion-enable-for-aarch64_be.patch
> > (superseeded by upstream commits [1] and [2])
> > - removed 0003-double-conversion-enable-for-or1k.patch
> > (superseeded by upstream commits [1] and [2])
> > - rebased 0004-double-conversion-enable-for-microblaze.patch
> >
> > [1] https://code.qt.io/cgit/qt/qtbase.git/commit/?id=6a39e49a6cdeb28a04a3657bb6a22f848d5dfa9d
> > [2] https://code.qt.io/cgit/qt/qtbase.git/commit/?id=4d40f09a45202dff901d4f970a6a7e939797138b
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > Changes v1 -> v2:
> > - fix qt5canvas3d hash entry (spotted by Gael PORTAY)
> > - remove the two patches taken from upstream fixing qendian/qswap
> > compile related failures
> > -
>
> ...and: - version bump updated from 5.12.0 to 5.12.1
...and qt5webengine compile using raspberrypi3_qt5we_defconfig still fails...
...and qt5webengine legal-info information needs to be fixed (will fix it with
the next patch iteration)...
Regards,
Peter
>
> Regards,
> Peter
prev parent reply other threads:[~2019-02-11 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 21:27 [Buildroot] [PATCH v2] qt5: bump latest version to 5.12.1 Peter Seiderer
2019-02-05 21:31 ` Peter Seiderer
2019-02-11 20:47 ` Peter Seiderer [this message]
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=20190211214755.3ba7bbb6@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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.