SUMMARY I'm building v2.9.0 on Debian buster (well, actually, Devuan Beowulf, which is the same thing but with systemd yanked out). CMake'ing works, and compilation goes fine. But during linking, I get the following: /usr/bin/ld: CMakeFiles/testsqltrack.dir/TestSqlTrack.cpp.o: in function `TestSqlTrack::initTestCase()': /usr/local/src/amarok-2.9.0/tests/core-impl/collections/db/sql/TestSqlTrack.cpp:52: undefined reference to `Collections::DatabaseCollection::setMountPointManager(MountPointManager*)' collect2: error: ld returned 1 exit status make[2]: *** [tests/core-impl/collections/db/sql/CMakeFiles/testsqltrack.dir/build.make:136: tests/testsqltrack] Error 1 make[1]: *** [CMakeFiles/Makefile2:3603: tests/core-impl/collections/db/sql/CMakeFiles/testsqltrack.dir/all] Error 2 and the same for a a few other targets. STEPS TO REPRODUCE 1. Install all relevant Debian packages for Amarok feature prerequisites 2. Run CMake on the v2.9.0 sources (downloaded today, 2019-07-14), with an out-of-source build directory 3. build SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux KDE Plasma Version: 5.54.0-1 KDE Frameworks Version: Not sure what number to put here. Qt Version: 5.11.3+dfsg1-1 ADDITIONAL INFORMATION Devuan Beowulf with no custom-built packages.
Did you try building with testing disabled? Since the testing framework needs to be built before compiling Amarok you might want to build without testing.
(In reply to Myriam Schweingruber from comment #1) > Did you try building with testing disabled? No, I used the default options. With testing disabled, the build concludes without errors.
I guessed as much.
(In reply to Myriam Schweingruber from comment #3) > I guessed as much. It's still a build failure, albeit of the testing code. Aren't you supposed to change the component or mark it somehow instead of testing it?
no, it is not a bug, you just need to either install and build the testing framework, or disable the testing (which is enabled by default). So definitely neither a build failure nor a bug, as testing is usually a requirement. IIRC this is also specified in the build instructions.