FTBFS with OpenCV 3.1 in artful proposed

Bug #1699794 reported by Rik Mills
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Simons ESyS Stuff
Invalid
High
simon (Ubuntu)
New
Critical
Unassigned

Bug Description

On a test build in my ppa, current simon FTBFS on all architectures when built against OpenCV 3.1 in proposed.

As the current simon packages depend on OpenCv 2.4, this is likely to block the ongoing OpenCV 3.1 transition if not resolved.

See the sample attached build log for amd64.

I have subsequently tried a build of the latest simon beta (0.4.90), but this also FTBFS in artful.

Revision history for this message
Rik Mills (rikmills) wrote :
Rik Mills (rikmills)
description: updated
Revision history for this message
Mattia Rizzolo (mapreri) wrote :
tags: added: opencv3.1
Revision history for this message
Rik Mills (rikmills) wrote :

Log of the 0.4.90 beta failed build

Revision history for this message
In , Rik Mills (rikmills) wrote :
Download full text (8.4 KiB)

Ref bug: https://bugs.launchpad.net/ubuntu/+source/simon/+bug/1699794

This blocks transition to OpenCV 3.1 in artful, so maye have to lose Simon from artful release/archive if not resolvable.

In version 0.4.1:

[ 39%] Linking CXX shared module ../../../lib/simonatspicommandplugin.so
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/plugins/Commands/ATSPI && /usr/bin/cmake -E cmake_link_script CMakeFiles/simonatspicommandplugin.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc -shared -o ../../../lib/simonatspicommandplugin.so CMakeFiles/simonatspicommandplugin.dir/simonatspicommandplugin_automoc.cpp.o CMakeFiles/simonatspicommandplugin.dir/atspicommandmanager.cpp.o CMakeFiles/simonatspicommandplugin.dir/atspiconfiguration.cpp.o CMakeFiles/simonatspicommandplugin.dir/atspiscanner.cpp.o -L/usr/share/OpenCV/3rdparty/lib/x86_64-linux-gnu -Wl,-rpath,/usr/share/OpenCV/3rdparty/lib/x86_64-linux-gnu:/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/lib: /usr/lib/x86_64-linux-gnu/libQtXml.so /usr/lib/x86_64-linux-gnu/libqaccessibilityclient.so.0.1.0 ../../../lib/libsimonactions.so.0.4.1 -lQtCore -lQtDBus -lQtGui ../../../lib/libsimonscenarios.so.0.4.1 /usr/lib/libkdeui.so.5.14.30 /usr/lib/x86_64-linux-gnu/libQtSvg.so /usr/lib/x86_64-linux-gnu/libQtXml.so /usr/lib/x86_64-linux-gnu/libQtGui.so /usr/lib/libkdecore.so.5.14.30 /usr/lib/x86_64-linux-gnu/libQtDBus.so /usr/lib/x86_64-linux-gnu/libQtCore.so -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/lib
CMakeFiles/simonatspicommandplugin.dir/atspiscanner.cpp.o: In function `QHash<QAccessibleClient::AccessibleObject, QPair<QString, QList<QAccessibleClient::AccessibleObject> > >::findNode(QAccessibleClient::AccessibleObject const&, unsigned int*) const':
atspiscanner.cpp:(.text._ZNK5QHashIN17QAccessibleClient16AccessibleObjectE5QPairI7QString5QListIS1_EEE8findNodeERKS1_Pj[_ZNK5QHashIN17QAccessibleClient16AccessibleObjectE5QPairI7QString5QListIS1_EEE8findNodeERKS1_Pj]+0x1c): undefined reference to `qHash(QAccessibleClient::AccessibleObject const&)'
collect2: error: ld returned 1 exit status
plugins/Commands/ATSPI/CMakeFiles/simonatspicommandplugin.dir/build.make:193: recipe for target 'lib/simonatspicommandplugin.so' failed
make[3]: *** [lib/simonatspicommandplugin.so] Error 1

In version 0.4.90:

[ 10%] Building CXX object simonlib/simonactions/CMakeFiles/simonactions.dir/simonactions_automoc.cpp.o
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/simonlib/simonactions && /usr/bin/c++ -DBACKEND_TYPE_BOTH -DHAVE_LIBSAMPLERATE_H -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=19 -DKDE_DEPRECATED_WARNINGS -DMAKE_SIMONACTIONS_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -DUSE_PLASMA -DUSE_WITH_SIMON -DWITH_SIMONCV -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/simonlib/simonactions -I/<<PKGBUILDDIR>>/simonlib/simonactions...

Read more...

no longer affects: simonsesys
Changed in simonsesys:
importance: Unknown → High
status: Unknown → New
Revision history for this message
Rik Mills (rikmills) wrote :

Had a play with a few options, but still get a FTBFS.

Simon seems to have a work in progress Qt5/Kf5 port

https://cgit.kde.org/simon.git/log/?h=kf5

So one option here would be temporarily removing Simon from artful archive, with a view to bringing it back once that port has a release, or is near enough for a decent git snapshot build.

Revision history for this message
Valorie Zimmerman (valorie-zimmerman) wrote :

Rik, I agree that seems the best idea. Perhaps ping the Simon devels and see if it can return soon, or will have to wait.

There is active porting work going on, but I've not seen a mention of Simon.

Revision history for this message
Rik Mills (rikmills) wrote : Re: [Bug 1699794] Re: FTBFS with OpenCV 3.1 in artful proposed

On 24/06/17 20:23, Valorie Zimmerman wrote:
> Rik, I agree that seems the best idea. Perhaps ping the Simon devels and
> see if it can return soon, or will have to wait.
>
> There is active porting work going on, but I've not seen a mention of
> Simon.

Pinged on IRC for now.

https://phabricator.kde.org/project/view/213/

Release of a KF5 port there is still under 'distant future'.

Revision history for this message
Rik Mills (rikmills) wrote :

Oooooh. Fails the same building against the old OpenCV. :/

Revision history for this message
In , Cfeck (cfeck) wrote :

It is unlikely that OpenCV 3.1 is the reason for the failures, because I have been compiling using that version for a long time.

The regression might be caused by update to Qt 5.9.0 or a GCC compiler update. All errors point to QHash template usage.

Revision history for this message
In , Rik Mills (rikmills) wrote :

(In reply to Christoph Feck from comment #1)
> It is unlikely that OpenCV 3.1 is the reason for the failures, because I
> have been compiling using that version for a long time.

Yes, I can see it fails against the old 2.49 as well

> The regression might be caused by update to Qt 5.9.0 or a GCC compiler
> update. All errors point to QHash template usage.

Still on Qt 5.7.1 for a short while, so not that. Compiler seems more likely
.

Revision history for this message
In , Cfeck (cfeck) wrote :

Hm, this is for the Qt4 version; cannot help there, because I can only test the KF5 builds right now.

You could try adding missing "#include <QHash>" lines to the files which appear in the error messages.

Revision history for this message
In , Rik Mills (rikmills) wrote :

I should note that while simon was removed from the ubuntu artful (17.10) -release pocket to allow the OpenCV transition to finish, but the failing build remains in -proposed pocket, so if this can be fixed it will slide straight back into the main archive.

Steve Langasek (vorlon)
Changed in simon (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Steve Langasek (vorlon) wrote :

There doesn't appear to have been any progress on resolving this for close to three months. I'm going to go ahead and remove the package from artful-proposed so that it's not showing up on proposed-migration as requiring action. If a fix becomes available and the Kubuntu team wishes to reupload it, we can fast-track this through NEW again based on the past package history.

Removing packages from artful-proposed:
 simon 0.4.1-0ubuntu11 in artful
Comment: Ubuntu-only package, FTBFS with current toolchain; LP: #1699794
1 package successfully removed.

Revision history for this message
Rik Mills (rikmills) wrote :

On 11/09/17 07:13, Steve Langasek wrote:
> There doesn't appear to have been any progress on resolving this for
> close to three months. I'm going to go ahead and remove the package
> from artful-proposed so that it's not showing up on proposed-migration
> as requiring action. If a fix becomes available and the Kubuntu team
> wishes to reupload it, we can fast-track this through NEW again based on
> the past package history.

This removal seems fair, as there has been little to zero progress for a
0.5 KDE4 release, and certainly nothing to fix this FTBFS. Plus the KF5
porting branch has not seen an upstream commit for 6 weeks.

Revision history for this message
In , Justin Zobel (justin-zobel) wrote :

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Changed in simonsesys:
status: New → Incomplete
Revision history for this message
In , Bug-janitor (bug-janitor) wrote :

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Revision history for this message
In , Bug-janitor (bug-janitor) wrote :

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

Changed in simonsesys:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.