diff options
| author | Dima <dgoldin+github@protonmail.ch> | 2019-09-21 18:16:38 +0200 |
|---|---|---|
| committer | Dima <dgoldin+github@protonmail.ch> | 2019-10-05 09:34:35 +0200 |
| commit | bdccffa81ce1ab1f5366c833b29065dfddfb8c1a (patch) | |
| tree | f11e11e2e95510acf1cfecf3072388e0d6641bb2 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 6be720b3a756662bb31adfdc1948553a02057c16 (diff) | |
linux_5_2, linux_5_3: fixing nondeterminism
In 5.2 kernel a new mechanism was introduced which embeds the kernel
headers in the kernel image and exposes them in procfs for simplified
use by userland tools.
It was introduced in
https://github.com/torvalds/linux/commit/43d8ce9d65a54846d378545770991e65838981e0
and later modified a bit in
https://github.com/torvalds/linux/commit/f7b101d33046a837c2aa4526cef28a3c785d7af2
The archive containing the header files had nondeterminism through the
header files metadata - specifically `mtime`, but I also decided to
normalize some other aspects just in case.
In our default setup we currently compile this as a module, so to expose
the headers to test the functionality `kheaders` needs to be loaded.
See https://lkml.org/lkml/2019/10/4/1036 and
https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=fixes&id=2cc99c9cdc8fde5e92e34f9655829449cebd3e00
I commented out the documentation part of the patch to make it cleanly apply to
5.2 and 5.3, see remark in the patch itself.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions