[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#965398: caml-crush: FTBFS: DWARF version 0 unhandled



Control: reassign -1 binutils 2.34.90.20200706-1
Control: reassign 965372 binutils 2.34.90.20200706-1
Control: forcemerge -1 965372
Control: retitle -1 FTBFS: DWARF version 0 unhandled
Control: affects -1 dwz src:caml-crush src:ocaml-mccs src:ocamlnet src:extlib

On Mon, Jul 20, 2020 at 08:57:07PM +0200, Sebastian Ramacher wrote:
> Source: caml-crush
> Version: 1.0.9-1
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the past)
> 
> binNMUs of caml-crush failed with:
> | dh_dwz -a -O--no-parallel
> |   dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd
> | dwz: debian/caml-crush-server/usr/bin/pkcs11proxyd: DWARF version 0 unhandled
> | dh_dwz: error: dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd returned exit code 1
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=caml-crush&arch=amd64&ver=1.0.9-1%2Bb1&stamp=1595270582&raw=0

See #965115 #965300 #965372

I don't think the current approach of reporting one bug per ocaml 
package and then manually disabling dwz in every single package
is a good way forward.

What changed was binutils (#965115), and the fix will likely have to be 
either in binutils or in dwz.

> Cheers

cu
Adrian


Reply to: