Thanks --- yes, that needs fixing. Unfortunately, while wearing my upstream hat, I've rewritten the build system, but I've applied some changes to make it honour variables like CC and PKG_CONFIG. The diff is here, if you're interested: https://github.com/davidgiven/wordgrinder/pull/181/files
The new version's not packaged for Debian yet as there are still some upstream fixes to be done. Is there actually a formal spec for the expected interface that polite Makefiles should honour to make cross building possible? And can you point me at the Debian tools you're using to do these checks? On Thu, 18 Nov 2021 at 06:24, Helmut Grohne <hel...@subdivi.de> wrote: > Source: wordgrinder > Version: 0.8-1 > Tags: patch > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > > wordgrinder fails to cross build from source for multiple reasons. It > starts with wordgrinder running plain make without passing any cross > tools. That part is best solved by using dh_auto_build. Then, the > makefile runs a build.lua script that hard codes the build architecture > pkg-config. PKG_CONFIG support should be added to both Makefile and > build.lua. Beyond that, it strips with the build architecture strip. In > addition to breaking cross compilation, that approach also breaks > generation of -dbgsym packages as well as DEB_BUILD_OPTIONS=nostrip. It > is best to defer stripping to dh_strip and that happens to fix the cross > build aspect as well. > > The attached patch fixes all of the issues mentioned above. However, it > does not make cross builds succeed as the test suite fails. Cross builds > do pass nocheck via DEB_BUILD_OPTIONS, but wordgrinder does not honour > that. So the next step is adding nocheck support. > > Anyway, please consider applying the attached patch as an incremental > step and close this bug when doing so even without adding nocheck > support. > > Helmut >
