Cannot build zanshin 0.5.0. Please note that 0.4.0 used to build without problems. [ 44%] Building CXX object tests/features/zanshin/features/step_definitions/CMakeFiles/zanshi_compilation.cpp.o [ 44%] Linking CXX executable zanshin-cuke-steps /usr/lib64/gcc/x86_64-slackware-linux/7.2.0/../../../../x86_64-slackware-linux/bin/ld: ../../pp.a(WireServer.cpp.o): undefined reference to symbol 'pthread_condattr_setclock@@GLIBC_2.3.3 /lib64/libpthread.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[2]: *** [tests/features/zanshin/features/step_definitions/CMakeFiles/zanshin-cuke-steps.res/step_definitions/zanshin-cuke-steps] Error 1 make[1]: *** [CMakeFiles/Makefile2:2363: tests/features/zanshin/features/step_definitions/CMa make: *** [Makefile:141: all] Error 2
Using gcc 7.2, glibc-2.26, Plasma 5.11.4, frameworks 5.41.0, applications 17.12. Distribution: Slackware64-current using kernel 4.14.11
Ahh... forgot: Qt 5.9.3
That's pretty much what I got here (except distribution is openSUSE Tumbleweed...) and it builds just fine. I'm not sure what's happening on your end unfortunately, sounds like an ABI issue in your pthread somehow? I'm guessing, really don't have enough of a clue here.
Googling it seems that the ld command line should have switches in different order. I don't know how to do that but looks like it could be the reason.
See this: https://github.com/BVLC/caffe/issues/1327
Hm... except I don't control that order at all from the CMakeLists.txt files... Note BTW that it seems to be in the tests, so if you just plan to use zanshin or package it you could build with BUILD_TESTING to OFF and it wouldn't get near those files. Not a proper solution but I hope that helps nonetheless.
Excellent. Setting BUILD_TESTING to OFF enabled the build to complete without problem. I now have Zanshin built and working under my Plasma setup. The switch I added to cmake was -DBUILD_TESTING=OFF and I was golden. So at least we have a good workaround. Thanks Kevin!!
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!
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!
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!