Hi Martin, On Mon, Sep 30, 2019 at 05:07:09PM +0200, Martin wrote: > Note this remark by upstream in xmpp:c...@dino.im?join : > > > [12:55:59] larma: debacle: I did cross compile dino. You > > probably don't want to use the ./configure script for it, but > > use CMake directly
Yes, that's what my patch did. > > [13:00:14] larma: All I had to do was to set PKG_CONFIG_PATH > > and CMAKE_TOOLCHAIN_FILE In Debian, PKG_CONFIG_PATH is set by a cross wrapper. We set PKG_CONFIG_EXECUTABLE. dh_auto_configure takes care of that and it generally just works. > > [13:01:13] larma: We don't use valac's compilation feature (we > > only use it for transpiling), so there shouldn't be any issues > > specific to vala > > [13:03:29] larma: But that was on Fedora, not Debian That's good. The problem here is with the packaging of valac, not with dino-im. We need a valac for the build architecture (to be able to run it), but dependency resolution gets us a host architecture one. Executing it yields an "Exec format error". It needs to be fixed on the valac side. I expect that dino-im cross builds just fine once we fix the packaging of valac. Thanks for your help. Unfortunately, fixing the valac side is not trivial, because it also supports a compiling mode. Also unfortunately, the valac maintainers seem to be very busy and unable to reply to bug reports in a timely manner. Helmut