Starting with >=net-libs/libiio-0.25 SoapyPlutoSDR results in a segfault during initialization. That makes using ADALM Pluto hardware unusable. Reproducible: Always Steps to Reproduce: 1. $ SoapySDRUtil --probe="driver=plutosdr" ###################################################### ## Soapy SDR -- the SDR abstraction library ## ###################################################### Probe device driver=plutosdr ERROR: Unable to claim interface 1:7:5: Device or resource busy (16) Speicherzugriffsfehler Same behavior when using the Pluto SDR from net-wireless/gqrx.
Seems like soapyplutosdr is the problem. In reality version 0.2.1 picks up some old github commit from pre 0.1 instead of tag 0.2.1. The last github state seems to fix the problem. Will prepare a version bump for it.
Yeah, this is why using commits like that in the ebuild is risky unless we really need to do it.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=346145602ffa362e1c3156f1b869b5ad5c22a6bc commit 346145602ffa362e1c3156f1b869b5ad5c22a6bc Author: Thomas Beierlein <tomjbe@gentoo.org> AuthorDate: 2023-12-06 10:59:27 +0000 Commit: Thomas Beierlein <tomjbe@gentoo.org> CommitDate: 2023-12-06 11:01:00 +0000 net-wireless/soapyplutosdr: add 0.2.1_p20220710 Closes: https://bugs.gentoo.org/919318 Signed-off-by: Thomas Beierlein <tomjbe@gentoo.org> net-wireless/soapyplutosdr/Manifest | 1 + .../soapyplutosdr-0.2.1_p20220710.ebuild | 27 ++++++++++++++++++++++ .../soapyplutosdr/soapyplutosdr-9999.ebuild | 8 +++---- 3 files changed, 32 insertions(+), 4 deletions(-)
(In reply to Sam James from comment #2) > Yeah, this is why using commits like that in the ebuild is risky unless we > really need to do it. I would avoid it, but the real 0.2.1 still has problems. So we need to use the latest available version. But will add an issue upstream to make a new release.
See https://github.com/pothosware/SoapyPlutoSDR/issues/59
