On 23/09/2020 00:40, Helmut Grohne wrote: > Source: qosmic > Version: 1.6.0-3 > Tags: patch upstream > User: [email protected] > Usertags: ftcbfs > > qosmic fails to cross build from source, because the upstream qosmic.pro > file hard codes the build architecture pkg-config. qmake actually > detects the correct pkg-config, but the .pro file fails to use it. > Please consider applying the attached patch to make qosmic cross > buildable. > > Helmut
Hi Helmut, Thanks for drawing my attention to this problem. Unfortunately I couldn't get the (non-cross) build to work with this patch. Extract from my build log ... ----------------------------------------------------------------------------- sh: 1: --version: not found Project MESSAGE: Config using pkg-config version sh: 1: --atleast-version: not found Project ERROR: Qosmic 1.6.0-4 3.1.1-3 requires at least version 3.1.1 of flam3 to build. make[1]: *** [Makefile:571: Makefile] Error 3 make[1]: Leaving directory '/mnt/Data/SourceCode/Debian/qosmic-1.6.0' dh_auto_clean: error: make -j12 distclean returned exit code 2 make: *** [debian/rules:11: clean] Error 25 dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -b failed ----------------------------------------------------------------------------- Looking at the original cross build log, it looks as though the first use of pkg-config $$system(pkg-config --version) is working OK, but the second use system(pkg-config --atleast-version 3.1.1 flam3) fails. I'm wondering if the syntax is wrong here, even though the non-cross build works. Should there be an equals sign in there? i.e. system(pkg-config --atleast-version=3.1.1 flam3) Alternatively, the whole test on flam3 version is superfluous on Debian, as dpkg will have checked the package dependencies before even looking at the .pro file. Maybe take it out? Any thoughts on this? Regards, Peter B
