Debian navigation

Notes about issue build_path_captured_in_assembly_objects in unstable

Identifier: build_path_captured_in_assembly_objects
Suites: unstable / trixie / bookworm / bullseye / experimental
Description: This is issue has been fixed for GCC 13 on 2022-11-02.
Before GNU as didn't support BUILD_PATH_PREFIX_MAP, so objects compiled from
assembly sources captured the build path.
Before GNU "as" only supported --debug-prefix-map=BUILDPATH=. which can
sometimes be passed via ASMFLAGS, ASFLAGS, or similar variables.
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 20 reproducible packages in unstable/amd64: gmp gnutls28 libffi libjpeg-turbo libpsm2 libsodium libunwind mesa mpeg2dec mpg123 multiboot musl nettle pixman powermanga retroarch wavpack libdv+ openssl+ yaskkserv+

FTBFS icon 2 FTBFS packages in unstable/amd64: nspr u-boot

FTBR icon 4 unreproducible packages in unstable/amd64: aircrack-ng dietlibc libzstd wrapsrv+

timeout icon 1 build timeout packages in unstable/amd64: linux+

NFU icon 1 not for us packages in unstable/amd64: pcsx2


Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise).

A package name displayed with a bold font is an indication that this package has a note. Visited packages are linked in green, those which have not been visited are linked in blue.
A # sign after the name of a package indicates that a bug is filed against it. Likewise, a + sign indicates there is a patch available, a P means a pending bug while # indicates a closed bug. In cases of several bugs, the symbol is repeated.