Having just bumped openmpi with new dependencies, pmix etc need to be keyworded for compatibility.
Unable to check for sanity: > package masked: sys-cluster/ucx-1.13.1, by keywords: -riscv
manual list it is, then... interesting that nattka make-package-list didn't solve for this.
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8773617f69643dfbae7ae8e2fb05ce67617f0642 commit 8773617f69643dfbae7ae8e2fb05ce67617f0642 Author: Marek Szuba <marecki@gentoo.org> AuthorDate: Mon Jul 5 13:13:03 2021 Commit: Marek Szuba <marecki@gentoo.org> CommitDate: Mon Jul 5 15:38:04 2021 sys-cluster/ucx: keyword 1.10.0_rc5 for -riscv "#error: Unsupported architecture". According to the source code (i.e. git master on GitHub), ucx currently only supports amd64, arm64 and ppc64. Signed-off-by: Marek Szuba <marecki@gentoo.org> sys-cluster/ucx/ucx-1.10.0_rc5.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) If this is true it may mean we need to drop more arches here too. I will leave that to the arch teams to figure out.
new unbundled dep
ppc64 done
arm64 done
Unable to check for sanity: > incorrect keywords: ia64
ia64 was dropped from gentoo
All sanity-check issues have been resolved
ping loong, sparc
Sorry for the delay. Turns out all versions of sys-cluster/ucx contain non-trivial arch-specific code, like the "bistro" component that JITs indirect jumps to pointers. And it's only ported to amd64, arm64 and ppc64. Given sys-cluster/pmix unconditionally RDEPENDs on sys-cluster/ucx, and sys-cluster/openmpi unconditionally RDEPENDs on sys-cluster/pmix, I think it's probably best to globally mask openmpi and only unmask on those 3 supported arches. And of course sys-cluster/ucx should be KEYWORDS="-* ~amd64 ~arm64 ~ppc64 ~x86" to reflect the reality...
(In reply to WANG Xuerui from comment #11) > Sorry for the delay. > > Turns out all versions of sys-cluster/ucx contain non-trivial arch-specific > code, like the "bistro" component that JITs indirect jumps to pointers. And > it's only ported to amd64, arm64 and ppc64. All versions of the upstream software too, I guess. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=978c8e081d9b625ce7414fa19839afe80cac52f1 commit 978c8e081d9b625ce7414fa19839afe80cac52f1 Author: Justin Lecher <jlec@gentoo.org> AuthorDate: Sun Apr 1 16:36:57 2018 Commit: Justin Lecher <jlec@gentoo.org> CommitDate: Sun Apr 1 16:51:33 2018 sys-cluster/ucx: New package Signed-off-by: Justin Lecher <jlec@gentoo.org> Package-Manager: Portage-2.3.27, Repoman-2.3.9 sys-cluster/ucx/Manifest | 1 + sys-cluster/ucx/metadata.xml | 12 ++++++++++++ sys-cluster/ucx/ucx-1.2.2.ebuild | 29 +++++++++++++++++++++++++++++ 3 files changed, 42 insertions(+) create mode 100644 sys-cluster/ucx/Manifest create mode 100644 sys-cluster/ucx/metadata.xml create mode 100644 sys-cluster/ucx/ucx-1.2.2.ebuild Originally added with KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux" These upstream "error unsupported architectures" didn't include i686, just x86_64 / ppc64 / aarch64, since at least https://github.com/openucx/ucx/commit/a6b55450c81b90661ff45d05bb836241a9545c41#diff-e78e8403c1cc6f845126743fbbc7fd4c2b95c67a309d9acb8726060e35921c07R32 Which is version 1.2.0 I was hoping that this was just keywords being carried forward despite no longer working, but in fact someone simply added a brand new package with keywords that have never been tested a single time in almost a decade. Sad...
There is a PR adding loong support to sys-cluster/ucx upstream, but the work is stalled. I've contacted the PR author and plan to take over the work myself.
