Source: libimobiledevice Version: 1.4.0-1 Tags: patch User: [email protected] Usertags: ftcbfs
libimobiledevice fails to cross build from source for armhf, because its check for a consistent Python development environment fails there. It is unclear to me why this succeeds for other architectures. Generally, one can see that all cross builds try to use the build architecture library directory. The typical root cause is using the wrong sysconfigdata and the usual solution is to export _PYTHON_SYSCONFIGDATA_NAME. I'm attaching a patch for your convenience. Please consider applying it. Helmut
diff -Nru libimobiledevice-1.4.0/debian/changelog libimobiledevice-1.4.0/debian/changelog --- libimobiledevice-1.4.0/debian/changelog 2025-10-26 21:48:31.000000000 +0100 +++ libimobiledevice-1.4.0/debian/changelog 2025-11-23 19:41:42.000000000 +0100 @@ -1,3 +1,10 @@ +libimobiledevice (1.4.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Export _PYTHON_SYSCONFIGDATA_NAME for the extension build. (Closes: #-1) + + -- Helmut Grohne <[email protected]> Sun, 23 Nov 2025 19:41:42 +0100 + libimobiledevice (1.4.0-1) unstable; urgency=medium * Team upload. diff -Nru libimobiledevice-1.4.0/debian/rules libimobiledevice-1.4.0/debian/rules --- libimobiledevice-1.4.0/debian/rules 2025-10-08 01:03:27.000000000 +0200 +++ libimobiledevice-1.4.0/debian/rules 2025-11-23 19:41:42.000000000 +0100 @@ -2,6 +2,10 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,-O1 -Wl,-z,defs export DEB_BUILD_MAINT_OPTIONS=hardening=+all +include /usr/share/dpkg/architecture.mk +ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) +export _PYTHON_SYSCONFIGDATA_NAME=_sysconfigdata__${DEB_HOST_ARCH_OS}_${DEB_HOST_MULTIARCH} +endif configure_flags += \ --prefix=/usr \
