01-13-2022, 10:39 PM
@SoundMan57
With hints from Tim and me, the ashuffle maintainer has identified the root cause of recent build failures on Raspberry Pis and pushed new code to his repo with the tag v3.1.11.1 (It has to do with RaspiOS, which is based on debian 10, using an older version of the compiler than the version he uses in his builds).
I have confirmed that ashuffle v3.11.1 successfully builds in moOde 7.6.1.
The problem with non-ARM binaries being generated for the ashuffle github repo has been traced to the CI (continuous integration) script but the maintainer hasn't fixed that yet.
You can build the binary yourself with the following recipe (taken from the ashuffle README.md, mostly). Assuming it is followed, the resulting binary will be found at /home/pi/ashuffle/build/ashuffle
The proof of the pudding is in the eating, as my grandmother would say
Regards,
Kent
With hints from Tim and me, the ashuffle maintainer has identified the root cause of recent build failures on Raspberry Pis and pushed new code to his repo with the tag v3.1.11.1 (It has to do with RaspiOS, which is based on debian 10, using an older version of the compiler than the version he uses in his builds).
I have confirmed that ashuffle v3.11.1 successfully builds in moOde 7.6.1.
The problem with non-ARM binaries being generated for the ashuffle github repo has been traced to the CI (continuous integration) script but the maintainer hasn't fixed that yet.
You can build the binary yourself with the following recipe (taken from the ashuffle README.md, mostly). Assuming it is followed, the resulting binary will be found at /home/pi/ashuffle/build/ashuffle
Code:
# on your moOde player
cd
git clone https://github.com/joshjunz/ashuffle.git
cd ashuffle
git checkout v3.11.1
git submodule update --init --recursive
meson -Dbuildtype=release build
ninja -C buildThe proof of the pudding is in the eating, as my grandmother would say
Code:
pi@CM4:~/ashuffle $ /home/pi/ashuffle/build/ashuffle -v
ashuffle version: v3.11.1Regards,
Kent
