It does require patching because of the -Werror in `Make.defaults`.
Second pitfall: the Makefile is trying to be smart regarding the ARFLAGS and that leads to a failure. Sadly we might have to replicate the logic that's in there with the correct checks.
For ARFLAGS logic see this patch: https://github.com/rhboot/pesign/commit/377da9b127b89a30ef2258bc3bfaee6565484611 I suppose it will be fine if we set ARFLAGS="-cvqs" in the ebuild.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0d2ffd3ca0142f69bf52e19f151ae7d2f6c8e707 commit 0d2ffd3ca0142f69bf52e19f151ae7d2f6c8e707 Author: Stefan Strogin <steils@gentoo.org> AuthorDate: 2019-07-26 23:30:43 +0000 Commit: Stefan Strogin <steils@gentoo.org> CommitDate: 2019-07-27 00:21:56 +0000 app-crypt/pesign: bump version to 113 Closes: https://bugs.gentoo.org/689590 Package-Manager: Portage-2.3.69, Repoman-2.3.16 Signed-off-by: Stefan Strogin <steils@gentoo.org> app-crypt/pesign/Manifest | 1 + app-crypt/pesign/files/pesign-113-nss.patch | 47 ++++++++++++++++++++++++++ app-crypt/pesign/pesign-113.ebuild | 52 +++++++++++++++++++++++++++++ 3 files changed, 100 insertions(+)
