Notes about issue ada_gprbuild_gcc_records_temp_paths in unstable
Identifier: | ada_gprbuild_gcc_records_temp_paths |
---|---|
Suites: | unstable / trixie / bookworm / bullseye / experimental |
Description: |
In the -dbgsym package for an Ada library, the output of readelf --debug-dump=info /usr/lib/usr/lib/debug/.build-id/*/*.debug matches DW_AT_producer GNU Ada -g -gnate[cm]=/tmp/GNAT-TEMP-[digits].TMP . The files are created by gprbuild for GCC subprocesses. The enumeration order varies during parallel builds. This issue differs from gcc_captures_build_path and cannot be solved by *-file-prefix-map. . Fix: pass -cargs:ada -gno-record-gcc-switches -gargs to gprbuild. Packages using debian_packaging.mk from gnat>=11.2 require no intervention. |
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
4 reproducible packages in unstable/amd64:
1 FTBFS packages in unstable/amd64:
1 unreproducible packages in unstable/amd64:
|
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.