| Summary: | neochat fails to build/link on riscv64 on Debian and Ubuntu (libatomic) | ||
|---|---|---|---|
| Product: | [Applications] NeoChat | Reporter: | Rik Mills <rikmills> |
| Component: | General | Assignee: | Tobias Fella <fella> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | carl, jlp |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Rik Mills
2022-12-13 16:09:31 UTC
Did you have successful builds of neochat for riscv before? Does you have similar problems for other KDE projects? Unfortunately none of the NeoChat developers has any RISC-V hardware to test this (In reply to Tobias Fella from comment #1) > Did you have successful builds of neochat for riscv before? Debian did not AFAIK. Ubuntu did, but that was as a result of a patch to our cmake to solve a similar maridb issue. Need for that has now gone, and our cmake is the same as Debian's, hence this failure popping up. Patching our cmake again is not an option for this. > Does you have similar problems for other KDE projects? Nothing yet in big things like fw, plasma and gear. As smaller things get new releases or rebuilt, it could happen. Since I reported this, we have had a packaging fix: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/neochat/commit/?h=kubuntu_lunar_archive https://launchpad.net/ubuntu/+source/neochat/22.11-2ubuntu2/+build/24935398 Might be the basis for a fix here in KDE? (In reply to Rik Mills from comment #2) > (In reply to Tobias Fella from comment #1) > > Did you have successful builds of neochat for riscv before? > Debian did not AFAIK. Ubuntu did, but that was as a result of a patch to our > cmake to solve a similar maridb issue. Need for that has now gone, and our > cmake is the same as Debian's, hence this failure popping up. Patching our > cmake again is not an option for this. > > Does you have similar problems for other KDE projects? > Nothing yet in big things like fw, plasma and gear. As smaller things get > new releases or rebuilt, it could happen. I've seen patches for libAtomic problems in QCoro before, maybe it's related to that? > > Since I reported this, we have had a packaging fix: > > https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/neochat/ > commit/?h=kubuntu_lunar_archive > > https://launchpad.net/ubuntu/+source/neochat/22.11-2ubuntu2/+build/24935398 > > Might be the basis for a fix here in KDE? Yes, sounds like something that should be done transparently through ecm. My motivation to carry it in neochat itself is relatively low. Looks like ecm already has a CheckAtomic.cmake, so guess just need to make use of it? (In reply to Rik Mills from comment #4) > Looks like ecm already has a CheckAtomic.cmake, so guess just need to make > use of it? Yes, appears all that might be needed is something like: https://invent.kde.org/network/neochat/-/snippets/2457 |