Closed alba4k closed 1 year ago
Hi,
on both machines, a fully up to date arch system
maybe try in a vm?
I use Arch Linux too and ran into the same error. On another one of my systems, I did successfully upgrade to noson 5.2.2 on 28 July (originally installed 4.4.9 through AUR and upgrading from there). Doing a clean build of the package on that machine, I now get the same error. Therefore I'm led to believe that some library changed, causing the build to error now.
Same here
In case anybody is experiencing the same, try to extract this folder and copy everything in the correct subdirectories (cp -r /path/to/folder/usr/* /usr/
, it should contain everything I was able to find on the old machine with the package installed that is needed).
I was able to install it on my new computer this way and it's working as intended, except it's obviously not managed by a package manager
On ubuntu 23 (development release) , the build fails with the same issue. I guess some system headers (time.h) have been updated in the recent linux distribution. It could be a bug too. It should be tracked.
Also, you could install the AppImage , which is provided in assets from the "Release" page. It should work on any Linux.
I updated the master branch to fix this issue. The change include explicitly the header
(I'm the maintainer of the Arch AUR package)
I've just updated the package to 5.3.2-1 and built it locally without any issues.
I just also succeesfully installed it (after obviously needing to remove the stuff that I had installed manually, but that was just a sudo rm -rf /usr/*noson*
away)
Thanks a lot for fixing this issue, I'm pretty sure it can be closed as completed :)
Again, thanks a lot for continuing to support this wonderful project @janbar !
Only feedback I could give, the pulseaudio audio sharing has quite some latency, but for everything else, this app is awesome!
While trying to build the program, I get a couple of errors due to weirdly organized code:
The compilation then proceeds until 70%, where it fails due to a makefile error (2)
Is this a known issues? experiencing on multiple machines
I might look into the code when I get back from holiday, but I think this would still be an issue
Hopefully I can help more, let me know! :)