| Version annotated: |
1.1.1-1 |
|
Identified issues:
|
|
Identifier:
|
build_id_differences_only
|
|
Description
|
The Build ID differs, but there are no other differences.
.
Specifically, NT_GNU_BUILD_ID, .gnu_debuglink, and
/usr/lib/debug/build-id/* filenames differ, but there are no other
differences.
.
[On 'sope' seen also a difference in a .GCC.command.line section; compare 'records_build_flags'.]
.
If there _are_ other differences (or if diffoscope output is truncated),
don't tag with this issue, but look for the root problem, as explained
under build_id_variation_requiring_further_investigation.
.
When this occurs on unstable but not on testing, it's likely a form
of captures_build_path. If it uses the cmake buildsystem, very
likely to be cmake_rpath_contains_build_path.
|
|
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:
|
1020876+: "yaskkserv: reproducible-builds: buildid differences in various binaries"
|
| |
|
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).
|