Bug#948763: z3: cannot be built on buildds
Ximin Luo
infinity0 at debian.org
Mon Jan 13 22:02:12 GMT 2020
Helmut Grohne:
> Control: retitle -1 cannot migrate to testing
>
> Hi Fabian,
>
> On Mon, Jan 13, 2020 at 04:27:15PM +0100, Fabian Wolff wrote:
>> On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne <helmut at subdivi.de> wrote:
>>> Source: z3
>>> Version: 4.8.7-3
>>> Severity: serious
>>>
>>> z3 cannot be built on buildds, because its Build-Depends cannot be
>>> satisfied on buildds. Failing to build on buildds is a serious problem.
>>
>> It builds now on all but three architectures, including, in particular, all
>> release architectures.
>
> Oh, I'm wrong here. It did build. But the dependency issue prevents it
> from migrating to testing. So you want to fix that anyway.
>
Why is testing migration prevented, when the builds completed fine? Why is there a "dependency issue" when clearly the dependencies were satisfied?
>> Thanks for your suggestions, but I'm not very familiar with how Multi-Arch
>> annotations should be used; I just accepted a patch to make the z3 package
>> more cross-build friendly (see #948109).
>
> That bug is not at all about cross building nor multi-arch. It seems you
> (and your contributors) are conflating multiple issues. Things become
> much easier once you start separating them.
>
>> Can you give me a patch where you set the build dependency annotations in a
>> sound way that also works for cross-building? Otherwise, I would have to
>> simply remove all annotations again in order to fix this bug (but clearly,
>> that would not be the most desirable solution).
>
> No. The expectation that every package can be cross built is misguided.
> z3 uses java stuff, which is an unsolved problem. Therefore you cannot
> make z3's dependencies cross-satisfiable at this time. If you want to do
> so anyway, be prepared to invest quite some work.
>
> For this reason, reverting the annotations is not the worst of options.
>
The sbuild command-line I gave near the end of #948109 works perfectly fine to cross-compile java bindings and the files have the correct binary format (for the foreign architecture).
Granted, I didn't actually run the bindings, but I don't see why they wouldn't work.
I can understand that, based on what your expectations are of the current tool chain you believe it shouldn't work, but *I actually tried it empirically and it works*.
X
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
More information about the Pkg-llvm-team
mailing list