|
Identified issues:
|
|
Identifier:
|
captures_shell_variable_in_autofoo_script
|
|
Description
|
Something looking like autotools is capturing SHELL for use at
runtime, which should probably be fixed to /bin/sh anyway.
.
Autotools also capturing the build path.
|
|
Identifier:
|
gcc_captures_build_path
|
|
Description
|
Captures build path, e.g., /build/1st/foo-42.0 v. /build/foo-42.0/2nd
.
Until early 2024 we varied the build path when testing packages from unstable
and experimental, which we have stopped doing now as the build path is recorded
as part of the environment and thus can be used when rebuilding.
.
This issue is kept here for the time being.
.
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:
|
nondeterministic_ordering_in_guile_binaries
|
|
Description
|
The ordering of various procedures in guile .go files can vary
when built in parallel. Can be worked around by disabling
parallelism in the build process.
.
Symtoms may include wrapXXX-procedures with different numbering
and/or a reference to SOMEFILE.scm present in one build but not
the other.
.
https://bugs.debian.org/995092
https://github.com/NixOS/nixpkgs/pull/78778
https://issues.guix.gnu.org/issue/20272
https://build.opensuse.org/request/show/732638
|
|