Search Criteria
Package Details: snapcast 0.31.0-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/snapcast.git (read-only, click to copy) |
---|---|
Package Base: | snapcast |
Description: | Synchronous multi-room audio player |
Upstream URL: | https://github.com/badaix/snapcast |
Keywords: | audio multi-room |
Licenses: | GPL |
Submitter: | mogwai |
Maintainer: | mogwai |
Last Packager: | mogwai |
Votes: | 37 |
Popularity: | 0.023307 |
First Submitted: | 2016-01-01 21:21 (UTC) |
Last Updated: | 2025-02-24 18:13 (UTC) |
Dependencies (15)
- alsa-lib
- avahi
- expat (expat-gitAUR)
- flac (flac-gitAUR)
- jackAUR (jack2-gitAUR, pipewire-full-jack-gitAUR, pipewire-jack-gitAUR, jack2, pipewire-jack)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libsoxr
- libvorbis (libvorbis-aotuvAUR, libvorbis-aotuv-lancerAUR, libvorbis-gitAUR)
- opus (opus-gitAUR)
- alsa-utils (alsa-utils-gitAUR) (make)
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR) (make)
- python-mpd2 (python-mpd2-gitAUR) (optional) – stream plugin script
- python-musicbrainzngs (optional) – stream plugin script
- python-websocket-client (optional) – stream plugin script
Latest Comments
1 2 3 4 5 6 .. 9 Next › Last »
mogwai commented on 2025-02-24 18:14 (UTC)
@BrainDamage: done
mogwai commented on 2025-02-23 20:32 (UTC)
@kingo55: That's how AUR packages work: if any of the dependencies are updated, it's your own responsibility to recompile it, even if the package itself has not been updated. Most dependency updates are fine, it's mainly the major release upgrades that need recompiling. Apparently that was the case with flac now.
kingo55 commented on 2025-02-23 02:04 (UTC)
There must have been some dependency changes because I had to reinstall this when libFLAC.so.12 was removed recently.
I'm an AUR noob so I'm not sure if this has to be handled in this package.
BrainDamage commented on 2025-02-22 11:20 (UTC)
jack is missing from the depedencies, the buildsystem does attempt to detect it at build time and then include if available, and will skip otherwise. Adding jack to the dep list would make this package align with the overall arch policy of building with all available features.
mogwai commented on 2025-01-26 17:58 (UTC)
@rnestler: Fixed
rnestler commented on 2025-01-26 15:25 (UTC)
The snapserver plug-ins in in
/usr/share/snapserver/plug-ins/
aren't marked as executable and thus trying to use them leads to an error:Running
sudo chmod +x /usr/share/snapserver/plug-ins/meta_mopidy.py
fixes it.In the PKGBUILD the mode on the files seems to be explicitly set to be non-executable:
rnestler commented on 2024-09-01 21:47 (UTC)
@m040601 I got it to compile successfully using a distcc setup as documented in https://wiki.archlinux.org/title/Distcc#Cross_compiling_with_distcc
m040601 commented on 2024-05-15 04:26 (UTC) (edited on 2024-05-15 05:00 (UTC) by m040601)
Update on my efforts to try to update to the latest "snapcast" 0.28 on ArchlinuxArm, Raspberry Pi 2b (1GB RAM, 32bit not 64bit), armv7h
Thanks to @mogwai for the help and tips trying to troubleshoot this.
TLDR, May the 15th, 2024:
Unfortunately I am still not able to do it. Probably insufficient memory ? And I am loosing hope I will ever be able to do it. So I guess I'll have to be stuck with "snapcast" 0.26 version on this machine. Which, although slow and painfull, has always compiled. And still works reliably.
It was always clear that as @mogwai says,
I knew that also. And I also knew that I could compile and run "snapcast" 0.2x ... up till 0.26 in the last years.
But now, I can never pass that "14%" done stage, before the system runs out of memory, and the "OOM" kill it, and aborts the compilation.
Since my last trials some weeks ago, (read the previous comments on this same page), I decided to wait some weeks to see if ArchlinuxArm would update some important outdated packages. So for example I am now using
And I also followed this advice,
@mogwai, out of curiosity,
Which system is that actually ?
I personally still have the other system with 2GB RAM (snow chromebook) but I have not yet tested compiling snapcast 0.28 there. (broken cable). Will update here when done
mogwai commented on 2024-04-20 21:00 (UTC)
@m040601: No, none of the alarm parts are hopelessly outdated. They are outdated, but there are more than sufficient to compile any modern package. I've got a working snapcast binary for armv7h here that I compiled on my alarm system and that is running on my 32-bit alarm system right now.
What's the real problem is that the alarm maintainers did not properly block upstream changes to
/etc/makepkg.conf
that are incompatible with armv7h. Please remove-mno-omit-leaf-frame-pointer
from theCFLAGS
in/etc/makepkg.conf
and try again. It's simply the case that this new flag that got introduced a few weeks ago is incompatible with 32-bit systems.NB: This doesn't mean that you won't run into other problems like out-of-memory, though.
m040601 commented on 2024-04-20 20:47 (UTC) (edited on 2024-04-20 23:23 (UTC) by m040601)
@mogwai : Thanks for your help, trying to troubleshoot and understand these issues. Much appreciated, specially for slightly older hardware that should still be suppoorted.
Yes I know it does. Let me restate again to be crystal clear again. I dont mean it does not run on Arm. I mean it does not even compile or ArchlinuxArm, specifically the armv7h, that is the Raspberrpy Pi 2 v1.1 (32 bit). That is not the Raspberry Pi 2 1.2, which is the same processor as the Raspberry Pi 3 and runs 64bit ArchlinuxArm. Not because it is Arm, but because ArchlinuxArm is hopelessly outdated.
$ uname -a
$ pacman -Qi linux
By the day, when you say:
QUESTION 1:
Which specific armv7h board or chromebook did you test this with ? How much memory does that system have ?
Yes of course. That is very true for arm and compiling c++ applications in general. I also have another armv7h system also running ArchlinuxArm. It is a Samsung Chromebook (snow version). Instead of 1000MB of the Raspberry Pi, it has 2GB or RAM. And a 2 core but snappier CPU. It is always much much faster compiling.
Right now in my system, it is not related to not having enough memory. It is simply that the compiler is outdated. There is no way to even start the build.
Lets go step by step.
sudo pacman -S boost cmake
No problem with those above.
Let's try "snapcast":
$ yay -S snapcast
No problems above.
No problems above.
That is the problem. It's not that there is little memory available. It is an outdated version of the compiler in the ArchlinuxArm repos. It should be "13" but it is "12" from 2022.
$ pacman -Qo /usr/bin/c++
$ pacman -Qo /usr/bin/gcc
pacman -Qi gcc
EDIT: Some usefull references:
https://archlinuxarm.org/forum/viewtopic.php?f=9&t=16808&sid=0689e401e72d76f2b8ec819be12d1f40 ,
https://archlinuxarm.org/forum/viewtopic.php?f=7&t=16848&sid=0689e401e72d76f2b8ec819be12d1f40 ,
1 2 3 4 5 6 .. 9 Next › Last »