From: qorg11 <qorg11@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Fixed i2pd for older processors
Date: Mon, 16 Nov 2020 19:24:37 +0100 [thread overview]
Message-ID: <20201116182437.ZpPPq5PwG_jCMhrL2O9QyXjNoIqW17NYcT4dPeoZl84@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26436@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
There is an updated pull request by qorg11 against master on the void-packages repository
https://github.com/qorg11/void-packages fix-i2pd
https://github.com/void-linux/void-packages/pull/26436
Fixed i2pd for older processors
Some processors have not the AES instructions set
(https://en.wikipedia.org/wiki/AES_instruction_set) and if you try to
run i2pd in a processor without that, it will simply give "Illegal instruction"
This can be fixed by removing the `USE_AESNI=1` make
flag. (https://i2pd.readthedocs.io/en/latest/devs/building/windows/#aes-ni)
A patch file from https://github.com/void-linux/void-packages/pull/26436.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix-i2pd-26436.patch --]
[-- Type: text/x-diff, Size: 1217 bytes --]
From 84ba398e64d5a7cdf7d3ae90605af0b115a33e5c Mon Sep 17 00:00:00 2001
From: qorg11 <qorg@vxempire.xyz>
Date: Mon, 16 Nov 2020 19:24:01 +0100
Subject: [PATCH] i2pd: fix for older processors
Some processors have not the AES instructions set
(https://en.wikipedia.org/wiki/AES_instruction_set) and if you try to
run i2pd in a processor without that, it will simply give "Illegal instruction"
This can be fixed by removing the `USE_AESNI=1` make
flag. (https://i2pd.readthedocs.io/en/latest/devs/building/windows/#aes-ni)
---
srcpkgs/i2pd/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/i2pd/template b/srcpkgs/i2pd/template
index 6a93f6f94c5..3128848b14e 100644
--- a/srcpkgs/i2pd/template
+++ b/srcpkgs/i2pd/template
@@ -1,7 +1,7 @@
# Template file for 'i2pd'
pkgname=i2pd
version=2.33.0
-revision=1
+revision=2
build_style=gnu-makefile
make_build_args="USE_UPNP=yes"
makedepends="zlib-devel boost-devel libressl-devel miniupnpc-devel
@@ -24,7 +24,7 @@ make_dirs="/var/lib/i2pd 0700 _i2pd _i2pd"
case "${XBPS_TARGET_MACHINE}" in
x86_64*|i686*) ;;
- *) make_build_args+=" USE_AESNI=no USE_AVX=no" ;;
+ *) make_build_args+=" USE_AVX=no" ;;
esac
pre_install() {
next prev parent reply other threads:[~2020-11-16 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 16:53 [PR PATCH] " qorg11
2020-11-16 17:17 ` ericonr
2020-11-16 18:23 ` qorg11
2020-11-16 18:24 ` qorg11 [this message]
2020-11-16 18:30 ` [PR REVIEW] " ericonr
2020-11-16 18:51 ` qorg11
2020-11-16 20:02 ` ericonr
2020-11-17 23:52 ` [PR REVIEW] " sgn
2020-11-17 23:53 ` sgn
2020-11-17 23:53 ` sgn
2020-11-18 0:13 ` ericonr
2021-01-07 0:20 ` sgn
2021-01-07 0:21 ` sgn
2021-01-07 0:46 ` [PR PATCH] [Closed]: " qorg11
2021-01-07 0:47 ` [PR REVIEW] " qorg11
2021-04-18 4:40 ` ericonr
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=20201116182437.ZpPPq5PwG_jCMhrL2O9QyXjNoIqW17NYcT4dPeoZl84@z \
--to=qorg11@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).