Skip to content
GitLab
Projects
Groups
Topics
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Register
Sign in
Toggle navigation
Menu
Reproducible Builds
reproducible-notes
Compare revisions
96429a0527f3f0013b27c29739d21324d298418c...235a6ab8be4f06c0e7c1536b8c83820ff49daf67
Commits (2)
issues: records_build_flags: Update the status of upstreaming.
· 2de30c8a
Vagrant Cascadian
authored
Feb 20, 2021
2de30c8a
issues: gcc_captures_build_path: Update to reflect current
· 235a6ab8
Vagrant Cascadian
authored
Feb 20, 2021
dpkg-buildflags defaults.
235a6ab8
Hide whitespace changes
Inline
Side-by-side
issues.yml
View file @
235a6ab8
...
...
@@ -1538,8 +1538,9 @@ records_build_flags:
.
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html
.
If/when this is accepted, this issue should be fixed for all packages and
you should not need to fix it specifically in your package.
Though the patch is currently unlikely to be merged. If/when this
is accepted, this issue should be fixed for all packages and you
should not need to fix it specifically in your package.
.
For more background information see:
.
...
...
@@ -1776,8 +1777,9 @@ gcc_captures_build_path:
and experimental, for stretch, buster and bullseye we recommend that rebuilds
are done in the same path as the original build.
.
dpkg-buildflags sets -fdebug-prefix-map by default (and -ffile-prefix-map in
our test infrastructure) which fixes this issue in many cases, but not all.
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:
...
...