https://bugs.kde.org/show_bug.cgi?id=463013
Tobias Fella <fe...@posteo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #3 from Tobias Fella <fe...@posteo.de> ---
(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.
--
You are receiving this mail because:
You are watching all bug changes.
