From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC] john: make simd a build option, off by default
Date: Sun, 31 May 2020 17:48:58 +0200 [thread overview]
Message-ID: <20200531154858.-36p1zBsD91C3-WNPjiWMPzwSIekV53LXrpsKaYQ5zU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22467@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
There is an updated pull request by abenson against master on the void-packages repository
https://github.com/abenson/void-packages fix_john_simd
https://github.com/void-linux/void-packages/pull/22467
[RFC] john: make simd a build option, off by default
This solves the problem of SIMD features being enabled and leaking in on all
architectures, not just ppc*. It is now provided as a build option if there
if is a want/need to enable these for custom builds.
A patch file from https://github.com/void-linux/void-packages/pull/22467.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix_john_simd-22467.patch --]
[-- Type: text/x-diff, Size: 1734 bytes --]
From dd40427aef8e23c82cb45a634064cb023067bfb9 Mon Sep 17 00:00:00 2001
From: Andrew Benson <andrew.benson.2@us.af.mil>
Date: Sun, 31 May 2020 10:39:23 -0500
Subject: [PATCH] john: make simd a build option, off by default
This solves the problem of SIMD features being enabled and leaking in on all
architectures, not just ppc*. It is now provided as a build option if there
if is a want/need to enable these for custom builds.
---
srcpkgs/john/template | 12 +++---------
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/srcpkgs/john/template b/srcpkgs/john/template
index 21c23d89d36..bb5fd8cdbba 100644
--- a/srcpkgs/john/template
+++ b/srcpkgs/john/template
@@ -1,12 +1,12 @@
# Template file for 'john'
pkgname=john
version=1.9.0
-revision=1
+revision=2
_jumbover=1
wrksrc="${pkgname}-${version}-jumbo-${_jumbover}"
build_wrksrc="src"
build_style=gnu-configure
-configure_args="--with-systemwide"
+configure_args="--with-systemwide $(vopt_enable simd)"
makedepends="libressl-devel gmp-devel libgomp-devel libpcap-devel bzip2-devel zlib-devel"
short_desc="John the Ripper password cracker (jumbo-${_jumbover} patch included)"
maintainer="Piraty <piraty1@inbox.ru>"
@@ -16,13 +16,7 @@ distfiles="$homepage/k/$pkgname-${version}-jumbo-${_jumbover}.tar.xz"
checksum=f5d123f82983c53d8cc598e174394b074be7a77756f5fb5ed8515918c81e7f3b
python_version=2 #unverified
-# the build system checks the host cpu for features, so when building on
-# a modern power9 system, it will attempt to shove in -mvsx and so on,
-# which breaks builds for 970 and 32-bit
-case "$XBPS_TARGET_MACHINE" in
- ppc64le*) ;;
- ppc*) configure_args+=" --disable-simd";;
-esac
+build_options="simd"
pre_configure() {
unset CPP AS LD
next prev parent reply other threads:[~2020-05-31 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 15:42 [PR PATCH] " abenson
2020-05-31 15:48 ` abenson [this message]
2020-05-31 15:59 ` [PR PATCH] [Merged]: " abenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200531154858.-36p1zBsD91C3-WNPjiWMPzwSIekV53LXrpsKaYQ5zU@z \
--to=abenson@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).