Instead of linking the lib folder with the libraries, link the lib
directory from the dev output containing the pkgconfig files. This is
enough for finding the libs and fixes a build failure with libressl.
(Not updating to the latest version, 1.34, because it breaks e.g.
'beets'. See https://github.com/beetbox/beets/issues/2153.)
The new version requires locale / i18n to be set-up for tests or else
this message is thrown:
RuntimeError: This test suite needs a unicode locale encoding. Try setting LANG=C.UTF-8
Also, remove a test that currently fails due to the python builder in
nixpkgs. PR with fix: https://github.com/NixOS/nixpkgs/pull/17430
("python: add file encoding to run_setup.py").
The echonest plugin was removed in 3.18 because the API it used is
shutting down. You might want to try the acousticbrainz instead.
Update pluginsWithoutDeps as needed to keep preCheck working.
Both python3 and setuptools come with easy-install. For some magic
reason this hasn't caused any collisions yet, but it does with #17428.
We hereby prioritize the version that comes with setuptools.
In light of Emacs packaging improvements such as those mentioned
in #11503, and with the addition of a systemd service (#15807
and #16356), and considering that the wiki page is completely
out of date (#13217), it seems that some documentation is in order.
Enabling EFI runtime services provides a venue for injecting code into
the kernel.
When grsecurity is enabled, we close this by default by disabling access
to EFI runtime services. The upshot of this is that
/sys/firmware/efi/efivars will be unavailable by default (and attempts
to mount it will fail).
This is not strictly a grsecurity related option, it could be made into
a general option, but it seems to be of particular interest to
grsecurity users (for non-grsecurity users, there are other, more
immediate kernel injection attack dangers to contend with anyway).
Looks like mostly performance enhancements and stability fixes. The main
user facing changes appear to be:
- The -Z option was removed
- A macro named FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION is defined when
compiling with afl-gcc
Full changelog at http://lcamtuf.coredump.cx/afl/ChangeLog.txt
