Bug#1086731: z3 FTCBFS: python3 dependency not installable
sylvestredeb at ledru.info
sylvestredeb at ledru.info
Mon Nov 4 22:11:21 GMT 2024
OK, thanks.
I merged the patch into the repo (with an upstream release).
if the build is successful, i will upload it
thanks!
S
Le lundi 4 novembre 2024 à 22:03, Helmut Grohne <helmut at subdivi.de> a écrit :
>
>
> Source: z3
> Version: 4.8.12-3.1
> Tags: patch
> User: debian-cross at lists.debian.org
> Usertags: cross-satisfiability
>
> z3 cannot be cross built from source, because its python3 dependency
> fails to install. A host architecture Python fails postinst, but it also
> is not what z3 needs for building as it wants to run Python during
> build.
>
> In a divide and conquer approach, I first looked into adding support for
> a nopython build profile such that the separate bindings could be
> approached separately. Doing so, I recommend using dh-sequence-*
> build-dependencies as they can be conditionalized using build profiles.
> Likewise, I recommend installing the documentation symlink using
> dh_installdocs --linkdoc, because it also handles build profiles at no
> extra effort. While at it, I noticed that the libz3-java -> libz3-dev
>
> dependency is not tight enough for using --linkdoc. Completely removing
> Python dependencies happens to break the build, because even with
> -DZ3_BUILD_PYTHON_BINDINGS=OFF Python and setuptools are being used, so
> we need to depend on those without a profile.
>
> It turns out that a nojava+nopython cross build just works. The z3
> Python module is based on ctypes. From a packaging point of view, this
> mostly means we can handle it as if it was a pure Python module. Hence,
> annotating the python3 dependency with :any or :native is reasonable.
> Once doing so, a nojava cross build also succeeds.
>
> Cross building with java is a more distant topic not solved here. The
> javahelper package is Arch:all and implicitly M-A:no. Any package
> depending on it currently cannot satisfy its cross Build-Depends. This
> is a problem that should be solved at the javahelper side rather than
> here.
>
> Given all of this, I am attaching a patch fixing all mentioned issues
> but the javahelper one. Please let me know if this change is acceptable
> or whether I should split it into smaller pieces for the individual
> problems.
>
> Helmut
> _______________________________________________
> Pkg-llvm-team mailing list
> Pkg-llvm-team at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team
More information about the Pkg-llvm-team
mailing list