On Wed, Aug 10, 2022 at 08:03:45AM +0200, Andreas Beckmann wrote:
> dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_client: Unknown
> debugging section .debug_addr
> dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_server: Unknown
> debugging section .debug_addr
FWIW this kind of
Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27375
OK, so it turns out this error is due to Clang's adoption of DWARFv5 [1]
which dwz doesn't fully support yet [2]. Until that is fixed, the issue
can be worked around by using DWARFv4 by adding `-gdwarf-4` to flags.
--
Control: retitle 1016936 dwz: Unknown debugging section .debug_addr causes some
builds to fail
Control: tags 1016936 + upstream
Hello,
This error also occurred for me when building PolyMC under Clang, but
not GCC. It seems this problem is common for many Clang builds [1].
Fedora also seems to
Package: dwz
Version: 0.14-1
Followup-For: Bug #1016936
It also fails for nodejs (gcc 11 on mips64el):
https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=18.8.0%2Bdfsg-1=1662286086=0
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500,
Package: dwz
Version: 0.14-1
Severity: serious
Control: block 1016935 with -1
Hi,
assaultcube recently started to FTBFS with a dwz error. Since both
src:assaultcube and src:dwz haven't been changed for a long time and
successfully built previously, I suspect this is related to GCC 12
becoming
5 matches
Mail list logo
