Public bug reported:
gloo-rocm uses Architecture: any for its binary packages, but it has a
Build-Depends on hipcc which is only available on:
- amd64
- amd64v3
- arm64
- ppc64el
This causes FTBFS on architectures where hipcc is not available.
Fix:
Restrict the Architecture field in debian/control to amd64 arm64 ppc64el
to match hipcc availability.
** Affects: gloo-rocm (Ubuntu)
Importance: Undecided
Assignee: Igor Luppi (igorluppi)
Status: In Progress
** Summary changed:
- Remove gloo-rocm armhf, riscv64 and s390x archs.
+ gloo-rocm should restrict Architecture to match hipcc availability
** Changed in: gloo-rocm (Ubuntu)
Status: New => In Progress
** Changed in: gloo-rocm (Ubuntu)
Assignee: (unassigned) => Igor Luppi (igorluppi)
** Description changed:
gloo-rocm uses Architecture: any for its binary packages, but it has a
Build-Depends on hipcc which is only available on:
- amd64
- amd64v3
- arm64
- ppc64el
+ - amd64
+ - amd64v3
+ - arm64
+ - ppc64el
+
This causes FTBFS on architectures where hipcc is not available.
Fix:
Restrict the Architecture field in debian/control to amd64 arm64 ppc64el
to match hipcc availability.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2143585
Title:
gloo-rocm should restrict Architecture to match hipcc availability
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gloo-rocm/+bug/2143585/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
