Version annotated: |
1.0.0-1 |
Identified issues:
|
Identifier:
|
gcc_captures_build_path
|
Description
|
Captures build path, e.g., /build/1st/foo-42.0 v. /build/foo-42.0/2nd Currently we vary the build path only when testing packages from unstable and experimental, for testing and stable we recommend that rebuilds are done in the same path as the original build. . dpkg-buildflags version 1.20.6+ sets -ffile-prefix-map by default (and -fdebug-prefix-map in older versions) which fixes this issue in many cases, but not all (see: records_build_flags). . There are patches submitted upstream to address this specific issue, but they are unlikely to be merged at this point: . https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00513.html . When this is accepted into GCC upstream, we could remove this note. In the meantime, please do not remove this issue, nor mark it as deterministic, nor untag these packages.
|
Identifier:
|
build_path_captured_in_assembly_objects
|
URL
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93371
|
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.
|
|
Bugs noted:
|
1020866+: "wrapsrv: reproducible-builds: build path embedded in /usr/bin/wrapsrv"
|
|
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).
|