Notes about issue scons_doesnt_pass_environment_to_build_tools in unstable
| Identifier: | scons_doesnt_pass_environment_to_build_tools |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| Description: |
The build system SCons doesn't pass environment variables to the build tools (compilers etc.) by default. See scons(1): "scons does not automatically propagate the external environment used to execute scons to the commands used to build target files. This is so that builds will be guaranteed repeatable regardless of the environment variables set at the time scons is invoked" This prevents for example that SOURCE_DATE_EPOCH can be read by build tools. . This can be worked around by explicitly importing SOURCE_DATE_EPOCH in the SConstruct or similar file, such as the patch in https://bugs.debian.org/1010466 |
|
Packages in 'unstable' 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.