From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/isa-l/
Date: Thu, 1 Feb 2024 09:25:50 +0000 (UTC) [thread overview]
Message-ID: <1706779535.1ee253aa6283cbe750d69e62e44fc82d8cc18bfc.marecki@gentoo> (raw)
commit: 1ee253aa6283cbe750d69e62e44fc82d8cc18bfc
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 1 09:20:22 2024 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Thu Feb 1 09:25:35 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1ee253aa
dev-libs/isa-l: keyword 2.30.0-r1 for -x86
Build failures. Test failures. Even if it did work, it would be rather
slow because the workaround for the former involves disabling
arch-optimised code paths. Upstream comments in the relevant issue
suggest they do not particularly care for 32-bit PCs.
Probably shouldn't have been keyworded for this arch in the first place.
Bug: https://bugs.gentoo.org/923425
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
dev-libs/isa-l/isa-l-2.30.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/isa-l/isa-l-2.30.0-r1.ebuild b/dev-libs/isa-l/isa-l-2.30.0-r1.ebuild
index 6cb8319addff..6e494ec705a8 100644
--- a/dev-libs/isa-l/isa-l-2.30.0-r1.ebuild
+++ b/dev-libs/isa-l/isa-l-2.30.0-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/intel/${PN}/archive/refs/tags/v${PV}.tar.gz -> ${P}.
LICENSE="BSD"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~riscv -x86"
IUSE="cpu_flags_x86_avx512f"
# AVX512 support in yasm is still work in progress
next reply other threads:[~2024-02-01 9:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 9:25 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-12 11:33 [gentoo-commits] repo/gentoo:master commit in: dev-libs/isa-l/ Michał Górny
2025-07-12 11:33 Michał Górny
2025-07-04 18:12 Arthur Zamarin
2025-07-04 15:40 Arthur Zamarin
2025-06-28 20:48 Sam James
2025-06-28 10:35 Michał Górny
2025-06-22 12:06 Sam James
2025-06-22 12:06 Sam James
2025-06-21 12:38 Sam James
2025-06-21 9:20 Michał Górny
2025-06-21 7:36 Sam James
2025-06-17 3:31 WANG Xuerui
2025-06-07 14:46 Sam James
2025-06-07 14:27 Sam James
2025-05-23 4:48 Sam James
2025-02-27 3:13 Sam James
2025-02-08 10:17 Arthur Zamarin
2024-11-02 8:49 Michał Górny
2024-10-07 17:32 Michał Górny
2024-10-07 17:32 Michał Górny
2024-10-07 15:50 Michał Górny
2024-04-19 12:09 Marek Szuba
2024-01-31 12:21 Marek Szuba
2023-10-31 0:06 Sam James
2023-05-17 14:59 Guilherme Amadio
2023-05-16 12:09 Arthur Zamarin
2023-05-16 12:09 Arthur Zamarin
2021-12-18 0:32 Marek Szuba
2021-12-17 23:18 Marek Szuba
2021-12-17 23:18 Marek Szuba
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=1706779535.1ee253aa6283cbe750d69e62e44fc82d8cc18bfc.marecki@gentoo \
--to=marecki@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