Andreas, you didn't do anything wrong, reason:
On 16.09.19 19:38, Andrey Rahmatullin wrote: > On Mon, Sep 16, 2019 at 05:38:47PM +0200, Andreas Tille wrote: >> Determining dependency 'gtest_main' with pkg-config executable >> '/usr/bin/pkg-config' >> PKG_CONFIG_PATH: >> Called `/usr/bin/pkg-config --modversion gtest_main` -> 1 > There is no pkgconfig file for gtest_main in the archive. googletest: /usr/src/googletest/googletest/cmake/gtest.pc.in googletest: /usr/src/googletest/googletest/cmake/gtest_main.pc.in Dunno if this is only wrong packaged or if there is a deeper sense behind ... Cheers Alf second mail i bothered wrar with: On 16.09.19 19:38, Andrey Rahmatullin wrote: > There is no pkgconfig file for gtest_main in the archive. And there is a reason for it: short test: mkdir googletest cd googletest apt source googletest cd goog<tab> nano debian/rules override_dh_missing: dh_missing --fail-missing Result: make[1]: Verzeichnis „/home/agaida/fucked/googletest/googletest-1.9.0.20190831“ wird verlassen dh_installdocs -O--buildsystem=cmake dh_installchangelogs -O--buildsystem=cmake dh_installman -O--buildsystem=cmake dh_installinit -O--buildsystem=cmake dh_perl -O--buildsystem=cmake dh_link -O--buildsystem=cmake dh_strip_nondeterminism -O--buildsystem=cmake dh_compress -O--buildsystem=cmake dh_fixperms -O--buildsystem=cmake debian/rules override_dh_missing make[1]: Verzeichnis „/home/agaida/fucked/googletest/googletest-1.9.0.20190831“ wird betreten dh_missing --fail-missing dh_missing: usr/lib/x86_64-linux-gnu/pkgconfig/gmock.pc exists in debian/tmp but is not installed to anywhere dh_missing: usr/lib/x86_64-linux-gnu/pkgconfig/gtest_main.pc exists in debian/tmp but is not installed to anywhere dh_missing: usr/lib/x86_64-linux-gnu/pkgconfig/gmock_main.pc exists in debian/tmp but is not installed to anywhere dh_missing: usr/lib/x86_64-linux-gnu/pkgconfig/gtest.pc exists in debian/tmp but is not installed to anywhere dh_missing: usr/lib/x86_64-linux-gnu/cmake/GTest/GTestConfigVersion.cmake exists in debian/tmp but is not installed to anywhere dh_missing: usr/lib/x86_64-linux-gnu/cmake/GTest/GTestConfig.cmake exists in debian/tmp but is not installed to anywhere dh_missing: usr/lib/x86_64-linux-gnu/cmake/GTest/GTestTargets-none.cmake exists in debian/tmp but is not installed to anywhere dh_missing: usr/lib/x86_64-linux-gnu/cmake/GTest/GTestTargets.cmake exists in debian/tmp but is not installed to anywhere dh_missing: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: google-mock (0), googletest (3), googletest-tools (2), libgmock-dev (3), libgtest-dev (3) * dh_installdocs: google-mock (0), googletest (1), googletest-tools (0), libgmock-dev (0), libgtest-dev (0) * dh_installman: google-mock (0), googletest (0), googletest-tools (1), libgmock-dev (0), libgtest-dev (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built For a short-term work-around: Add the files to debian/not-installed make[1]: *** [debian/rules:49: override_dh_missing] Fehler 255 make[1]: Verzeichnis „/home/agaida/fucked/googletest/googletest-1.9.0.20190831“ wird verlassen make: *** [debian/rules:23: binary] Fehler 2 dpkg-buildpackage: Fehler: Unterprozess fakeroot debian/rules binary lieferte Exitstatus 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -ICVS - And no, i don't want to write a grave bug now - but i'm a bit speachless about the ignorance ... Cheers Alf
