Without the change build fails on upstream gcc-10 as:
ld: src/util.c.1.o:/build/pflask/build/../src/printf.h:42: multiple definition of
`use_syslog'; src/cgroup.c.1.o:/build/pflask/build/../src/printf.h:42: first defined here
sysstat compresses manual pages using the `ZIP` environment variable
unless `COMPRESS_MANPG` is set.
`ZIP` seems to default to xz(1) and is for more than just compressing
manuals.
At least with `documentation.man.mandoc.enable = true;` this renders
them unreadable:
```
$ man -w mpstat
man: outdated mandoc.db lacks mpstat(1) entry, run makewhatis /nix/store/lk0r6ibvkrvaq96gp8h4rqgrd2q0c8q5-system-path/share/man
/nix/store/lk0r6ibvkrvaq96gp8h4rqgrd2q0c8q5-system-path/share/man/man1/mpstat.1.xz
```
(followed by `PAGER` showing compressed mpstat.1.xz content.)
Disable manual page compression during build and thus defer it to Nix:
```
gzipping man pages under /nix/store/wl2dwl1lhs9g5w2d5dhr0pcskp78nz42-sysstat-12.4.5/share/man/
```
This also avoids potential runtime incompatibilites in sysstat
(I am not a `services.systat` user).
* linuxPackages.rtw88: 2021-04-19 to 2022-05-08
added myself to the maintainers
* linuxPackages.rtw88: removing upper version limit for the broken mark
Very confusingly, the `isPowerPC` predicate in
`lib/systems/inspect.nix` does *not* match `powerpc64le`!
This is because `isPowerPC` is defined as
isPowerPC = { cpu = cpuTypes.powerpc; };
Where `cpuTypes.powerpc` is:
{ bits = 32; significantByte = bigEndian; family = "power"; };
This means that the `isPowerPC` predicate actually only matches the
subset of machines marketed under this name which happen to be 32-bit
and running in big-endian mode which is equivalent to:
with stdenv.hostPlatform; isPower && isBigEndian && is32bit
This seems like a sharp edge that people could easily cut themselves
on. In fact, that has already happened: in
`linux/kernel/common-config.nix` there is a test which will always
fail:
(stdenv.hostPlatform.isPowerPC && stdenv.hostPlatform.is64bit)
A more subtle case of the strict isPowerPC being used instead of the
moreg general isPower accidentally are the GHC expressions:
Update pkgs/development/compilers/ghc/8.10.7.nix
Update pkgs/development/compilers/ghc/8.8.4.nix
Update pkgs/development/compilers/ghc/9.2.2.nix
Update pkgs/development/compilers/ghc/9.0.2.nix
Update pkgs/development/compilers/ghc/head.nix
Since the remaining legitimate use sites of isPowerPC are so few, remove
the isPowerPC predicate completely. The alternative expression above is
noted in the release notes as an alternative.
Co-authored-by: sternenseemann <sternenseemann@systemli.org>
This version was last touched in February 2022, as opposed to the
version we were using before, which hasn't been touched since January
2019.
I've reviewed the diff, and it all seems reasonable. We need a newer
version of this package, because hannesha's version doesn't build with
Linux 5.18.
Switch from autoreconfHook to running autogen.sh ourselves so that
gtkdocize gets run. The GTK_DOC_CHECK autoconf macro isn't
cross-friendly, so we have to disable it when cross-compiling.
Introduce new boolean arguments "pamSupport" and "capabilitiesSupport" that
control whether "pam" and "libcap" are compiled in. These flags are true by
default, so this commit does not cause any rebuilds.
Workaround build failure on -fno-common toolchains like upstream
gcc-10. Otherwise build fails as:
ld: lockdep.o:/build/linux-5.0.21/tools/lib/lockdep/../../include/linux/rcu.h:5: multiple definition of
`rcu_scheduler_active'; common.o:/build/linux-5.0.21/tools/lib/lockdep/../../include/linux/rcu.h:5: first defined here
patchShebangs was writing a build platform bash shebang to
systemd-update-helper, which ends up in the output. To fix this, this patch
restricts patchShebangs to only run on certain directories.
Also, remove a comment stating that patchShebangs will no longer be necessary
after the next systemd release. This is not the case because /usr/bin/env
doesn't exist within the sandbox and will still need to be patched.
