With the symlinked build it's only renaming 'coreutils' to
'gcoreutils' and leaving all the actual command symlinks alone.
Instead of custom renaming scripts, let's use --program-prefix
from the autotools kitchen sink. This has the nice(?) bonus that
the manpages also get prefixed with 'g' now.
The build system refuses to enable both single-binary build and
--program-prefix - but the symlink-based single-binary build couldn't
possibly work either (as it will be looking at "$0" for which command
to execute).
Copied from linux_4_4 (except for the EFI stub thing).
Otherwise the firewall module fails to evaluate:
Failed assertions:
- This kernel does not support rpfilter
Add the Perl module `Swim`, version 0.1.44, generated by
`nix-generate-from-cpan`.
This Perl module is the reference implementation for the lightweight
markup language [Swim].
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
[Swim]: <https://github.com/ingydotnet/swim-info>
Add the Perl module `HTML::Escape`, version 1.10, generated by
`nix-generate-from-cpan`.
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
Add the Perl module `Module::Build::Pluggable::PPPort`, version 0.04,
generated by `nix-generate-from-cpan`.
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
Add the Perl module `Module::Build::Pluggable`, version 0.10,
generated by `nix-generate-from-cpan`.
I have tested this change per nixpkgs manual section 11.1 ("Making
patches").
I'm getting new error in X.0.log:
"Synaptics driver unable to detect protocol"
but the touchpad still works fine. It seems the driver is trying to
additionally apply to my regular (wireless) mouse which fails.
I hope this is just harmless.
I'm getting new error in X.0.log:
"Synaptics driver unable to detect protocol"
but the touchpad still works fine. It seems the driver is trying to
additionally apply to my regular (wireless) mouse which fails.
I hope this is just harmless.
- Fixes#19673; it caused problems in combination with buildEnv.
- As noted, X falls back to /tmp:
https://github.com/NixOS/nixpkgs/issues/19673#issuecomment-258871876
- Removing the directory is still required, as X would attempt to write
into it if allowed - and probably succeed in case the user set
nix.readOnlyStore = false; (X runs as root).
- Archeology link: 9d1569316.
