From: "Khem Raj" <raj.khem@gmail.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Martin Jansa <martin.jansa@gmail.com>,
openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-qt5] qtwebkit 5.15 update failure
Date: Thu, 26 Mar 2020 10:13:52 -0700 [thread overview]
Message-ID: <CAMKF1srxY6873+cEoy+2jOQrQxjbnmq+nFxXSEFpXH5pgqM2bg@mail.gmail.com> (raw)
In-Reply-To: <20200326170721.GH1578@denix.org>
On Thu, Mar 26, 2020 at 10:07 AM Denys Dmytriyenko <denis@denix.org> wrote:
>
> On Thu, Mar 26, 2020 at 01:55:29AM +0100, Martin Jansa wrote:
> > On Wed, Mar 25, 2020 at 08:02:57PM -0400, Denys Dmytriyenko wrote:
> > > | Source/WebKit/WebKitWidgets_autogen/J52LRV53MS/moc_DefaultFullScreenVideoHandler.cpp:116: error: undefined reference to 'QWebFullScreenVideoHandler::qt_metacast(char const*)'
> > > | Source/WebKit/WebKitWidgets_autogen/J52LRV53MS/moc_DefaultFullScreenVideoHandler.cpp:121: error: undefined reference to 'QWebFullScreenVideoHandler::qt_metacall(QMetaObject::Call, int, void**)'
> > > | Source/WebKit/CMakeFiles/WebKitWidgets.dir/WebKitWidgets_autogen/mocs_compilation.cpp.o:mocs_compilation.cpp:WebKit::DefaultFullScreenVideoHandler::staticMetaObject: error: undefined reference to 'QWebFullScreenVideoHandler::staticMetaObject'
> > > | /usr/src/debug/qtwebkit/5.14.99+gitAUTOINC+ab1bd15209-r0.arago8/git/Source/WebKit/qt/WidgetSupport/DefaultFullScreenVideoHandler.cpp:45: error: undefined reference to 'vtable for QWebFullScreenVideoHandler'
> > >
Yeah I have seen this failure too on master.
> > > FWIW, it was building just fine before the update...
> >
> > If you care about qtwebkit, then please send patches for this.
>
> On the other hand - if you don't care about qtwebkit, why would you update it
> from a working version to a broken one?
>
> The issue is that with the upcoming 3.1 LTS around the corner, many of us are
> trying to finalize and stabilize our own code bases in master. I was very
> close to resolving most of the breakages for my builds just couple days ago,
> and now I got few more unexpected failures from meta-qt5...
>
meta-qt5 has already branched out dunfell before bumping QT version,
so we should be good there
unless Martin plans to backport it into dunfell branch
> Anyway, I'll see if I can find some time to look into this breakage...
>
> --
> Denys
>
next prev parent reply other threads:[~2020-03-26 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 0:02 [meta-qt5] qtwebkit 5.15 update failure Denys Dmytriyenko
2020-03-26 0:55 ` [oe] " Martin Jansa
2020-03-26 17:07 ` Denys Dmytriyenko
2020-03-26 17:13 ` Khem Raj [this message]
2020-03-26 17:39 ` Denys Dmytriyenko
2020-03-26 19:34 ` Martin Jansa
2020-03-26 20:06 ` Andreas M?ller
2020-03-26 20:09 ` Denys Dmytriyenko
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=CAMKF1srxY6873+cEoy+2jOQrQxjbnmq+nFxXSEFpXH5pgqM2bg@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=denis@denix.org \
--cc=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.