You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hardware
I'm using Asahi Linux (arm64) on an M1 Mac.
CPU: Apple M1
RAM: 8gb
GPU: Internal
SDR: Local RTL-SDR Blog v4
Software
Operating System: Fedora 41
SDR++: 1.2.1 built at 10:49:25 on Jan 7 2025
Bug Description
When just running SDR++ using the command line, it fails because it is missing libsdrpp. sdrpp: error while loading shared libraries: libsdrpp_core.so: cannot open shared object file: No such file or directory
Then, adding the plugins directory and /usr/lib to LD_LIBRARY_PATH allows SDR++ to start, but it still fails to find its modules. LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib:/usr/lib/sdrpp/plugins sdrpp
In the logs:
It's an issue with builds on fedora then. They use nonsensical directories for everything while SDR++ was hardcoded for normal POSIX install paths (ie. no lib64 bullshit). It may get fixed later when I get around to finish the better_install branch but no ETA.
AlexandreRouma
changed the title
No sdrpp modules found when running linux arm64 build from source
SDR++ doesn't run as is on Fedora because of non-standard directories
Jan 7, 2025
Hardware
I'm using Asahi Linux (arm64) on an M1 Mac.
Software
Bug Description
When just running SDR++ using the command line, it fails because it is missing libsdrpp.
sdrpp: error while loading shared libraries: libsdrpp_core.so: cannot open shared object file: No such file or directory
Then, adding the plugins directory and
/usr/lib
toLD_LIBRARY_PATH
allows SDR++ to start, but it still fails to find its modules.LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib:/usr/lib/sdrpp/plugins sdrpp
In the logs:
Steps To Reproduce
I realise this may be specific to my M1 linux platform, and so may be difficult to reproduce.
sudo make install
sdrpp
with and without adding/usr/lib
and the plugins dir toLD_LIBRARY_PATH
and observe logsThe text was updated successfully, but these errors were encountered: