Notes about issue records_build_flags in experimental
| Identifier: | records_build_flags |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| Description: |
Records $CFLAGS, which vary intentionally due to the «-fdebug-prefix-map=${BUILDPATH}=.», «-ffile-prefix-map=${BUILDPATH}=.» or «-fmacro-prefix-map=${BUILDPATH}=.» flags. . We have a patch pending to GCC to fix this issue centrally: . https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html . 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. . There is also a work-in-progress patch to dpkg that could address this issue: . https://bugs.debian.org/985553 . For more background information see: . • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html |
|
Packages in 'experimental' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
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.