Thorden wrote: > The first option doesn't work, as it still can't find the libasound > thing. Is there a way to tell it where it is? This is unlikely to be easy to be easy as your Linux skills are limited and this is likely to be very fiddly & messy. The path is usually built into the executable. The executable is searching in standard places but the NAS is not "standard".
So there are main options: 1. Alter the system search paths 2. Executables often search the local directory first before looking elsewhere. As an initial check for step 1 - is there a directory called called /etc/ld.so.conf - if there is what files are in there ? Is there one called somehting like x86_64-linux-gnu.conf - if so what is in the file / If it is another directory - what is in that directory. As an initial test for step 2 - can youcopy the file libasound.so.2 from /volume1/@appstore/AudioStation/lib/ to the same directory as squeezelite . If necessary change ownership and group of the libasound file to saem as squeezelite. Try running squeezelite without the "LD_LIBRARY_PATH" > I created a file called squeezelite.sh in /volume1/homes. It contains > only the command: > LD_LIBRARY_PATH=/volume1/@appstore/AudioStation/lib > /volume1/homes/admin/squeezelite -d all=info -a 88200:1298:16:1 -o > hw:0,0 > I did chmod u+x on the .sh file. > Trying to execute it gives "-ash: squeezelite.sh: command not found" > It looks like it couldeven find the command squeezelite.sh - did you use "./squeezelite,.sh" ? What did you use to try to execute it ? The first line of the script should have the path the shell to be used - I don't know what shell is running on the your system probably bash but could be ash or even busybox. > By the way, the LD_LIBRARY_PATH command only works when I have sudoed to > root. Guess it will fail with the Local Player/squeezebox user? That could be due to wrong permission or owner/group on any of the directories on the path to libasound.so or even the file itself. Also the problem could be permission on the ALSA audio devices in /proc/asound If you can get step 1 or 2 working - then it will avoid the script part which is probably best although permission will still need to be sorted. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=97766 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
