From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/crc32c/
Date: Sun, 24 Oct 2021 06:58:31 +0000 (UTC) [thread overview]
Message-ID: <1635058650.d3887e9f15fade5c6dbbd79a11bb5a54a3e18c6a.arthurzam@gentoo> (raw)
commit: d3887e9f15fade5c6dbbd79a11bb5a54a3e18c6a
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 24 06:53:06 2021 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sun Oct 24 06:57:30 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d3887e9f
dev-libs/crc32c: fix for arm64 without crc32
On arm64, the build system decided if the current CPU supports crc32
instructions, but forcing the compiler to support it and then checking
if it compiles. By removing the forcing, we really check if the arch
supports it.
Bit thanks to Sam James <sam <AT> gentoo.org> for testing and finding the
issue in build system.
Closes: https://bugs.gentoo.org/818874
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-libs/crc32c/{crc32c-1.1.2.ebuild => crc32c-1.1.2-r1.ebuild} | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/dev-libs/crc32c/crc32c-1.1.2.ebuild b/dev-libs/crc32c/crc32c-1.1.2-r1.ebuild
similarity index 91%
rename from dev-libs/crc32c/crc32c-1.1.2.ebuild
rename to dev-libs/crc32c/crc32c-1.1.2-r1.ebuild
index 6eee30bb278..e7e06e01ec2 100644
--- a/dev-libs/crc32c/crc32c-1.1.2.ebuild
+++ b/dev-libs/crc32c/crc32c-1.1.2-r1.ebuild
@@ -24,7 +24,9 @@ PATCHES=(
DOCS=( README.md )
src_prepare() {
- sed -e '/-Werror/d' -i CMakeLists.txt || die
+ sed -e '/-Werror/d' \
+ -e '/-march=armv8/d' \
+ -i CMakeLists.txt || die
cmake_src_prepare
}
next reply other threads:[~2021-10-24 6:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 6:58 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 16:44 [gentoo-commits] repo/gentoo:master commit in: dev-libs/crc32c/ WANG Xuerui
2023-04-30 7:53 Andreas Sturmlechner
2023-03-15 19:57 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-02-25 5:46 Arthur Zamarin
2023-02-09 15:14 Arthur Zamarin
2023-02-09 15:14 Arthur Zamarin
2022-02-02 0:08 Sam James
2022-02-01 7:36 Agostino Sarubbo
2022-02-01 7:30 Agostino Sarubbo
2022-02-01 5:57 Sam James
2022-01-31 20:11 Arthur Zamarin
2022-01-31 20:08 Arthur Zamarin
2022-01-17 8:13 Joshua Kinard
2021-10-27 22:35 Sam James
2021-10-21 17:57 Arthur Zamarin
2021-10-12 18:57 Sam James
2021-10-12 18:57 Sam James
2021-10-04 22:58 Sam James
2021-09-16 1:49 Sam James
2021-09-10 1:27 Sam James
2021-09-07 3:07 Sam James
2021-09-05 16:41 Arthur Zamarin
2021-09-05 16:41 Arthur Zamarin
2021-08-13 15:20 Marek Szuba
2019-04-29 14:24 Jason Zaman
2019-02-01 12:17 Jason Zaman
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=1635058650.d3887e9f15fade5c6dbbd79a11bb5a54a3e18c6a.arthurzam@gentoo \
--to=arthurzam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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