Problems compiling rtl-sdr on debian
Hello all! Just been trying to compile rtl-sdr ( http://sdr.osmocom.org/trac/wiki/rtl-sdr ) on my linux box but I'm having a few problems. Btw the linux distro is debian running a 64-bit kernel; 3.10-1-amd64. Here's the problem. I can't seem to get rtl-sdr to compile quite right either with the cmake or autotools instructions from the sdr website. I've tried both methods; only one completes (but produces an unstable version) the other version dosen't compile at all. Here's the output I get from trying to build by using cmake - http://slothpuck.no-ip.org/tmp/cmake-build.txt and then with autotools method - http://slothpuck.no-ip.org/tmp/autoconf-build.txt I get a lot of errors with the cmake method with lots of warnings about unused paramaters; the autotools method dosen't even complete. The cmake version does however but appears to be very unstable. If I try to run one of the programs made by rtl-sdr -- the program rtl_tcp with another program such as gqrx, .e.g by starting rtl_tcp in a terminal then run gqrx in another ( http://www.oz9aec.net/index.php/gnu-radio/gqrx-sdr ) I find it causes rtl_tcp to crash - either with a segfault, or with a "worker cond timeout, signal caught exiting!" message (rtl_tcp hung in this case). I do have libusb (both library and dev) and gnuradio installed btw. any thoughts on what might be going wrong at all? Thanks ljones
Am Sonntag, 4. August 2013, 17:24:09 schrieb lee jones:
Hello all!
Just been trying to compile rtl-sdr ( http://sdr.osmocom.org/trac/wiki/rtl-sdr ) on my linux box but I'm having a few problems. Btw the linux distro is debian running a 64-bit kernel; 3.10-1-amd64.
Here's the problem. I can't seem to get rtl-sdr to compile quite right either with the cmake or autotools instructions from the sdr website. I've tried both methods; only one completes (but produces an unstable version) the other version dosen't compile at all.
Look at the following line - it is telling you everything you want to know... Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Good luck Andreas
Look at the following line - it is telling you everything you want to know... Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Will try that though not sure why on the other method the configure script wouldn't complete! x.x ljones On 8/4/13, df8oe@gmx.de <df8oe@gmx.de> wrote:
Am Sonntag, 4. August 2013, 17:24:09 schrieb lee jones:
Hello all!
Just been trying to compile rtl-sdr ( http://sdr.osmocom.org/trac/wiki/rtl-sdr ) on my linux box but I'm having a few problems. Btw the linux distro is debian running a 64-bit kernel; 3.10-1-amd64.
Here's the problem. I can't seem to get rtl-sdr to compile quite right either with the cmake or autotools instructions from the sdr website. I've tried both methods; only one completes (but produces an unstable version) the other version dosen't compile at all.
Look at the following line - it is telling you everything you want to know...
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Good luck Andreas
-- :) SP
On 8/4/13, lee jones <slothpuck@gmail.com> wrote:
Look at the following line - it is telling you everything you want to know... Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Will try that though not sure why on the other method the configure script wouldn't complete! x.x
Ok I gave that a try. I managed to track down the missing pkgconfig file. The line about not finding pkgconfig has now gone - but all of the errors at compile time are all still there, and rtl_tcp still crashes. Installing pkg-config got rid of the error, but not much else unfortunarly x.x ljones
I also have re-tried with installing the pkgconfig file recompiling by using autoconf rather than cmake. But I still get lots of errors; http://slothpuck.no-ip.org/tmp/autoconf-build2.txt what's concerning me are all those "unused parameter" error messages, as if they aren't being built in and that's maybe why rtl_tcp just hangs or crashes. ljones On 8/4/13, lee jones <slothpuck@gmail.com> wrote:
On 8/4/13, lee jones <slothpuck@gmail.com> wrote:
Look at the following line - it is telling you everything you want to know... Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Will try that though not sure why on the other method the configure script wouldn't complete! x.x
Ok I gave that a try. I managed to track down the missing pkgconfig file.
The line about not finding pkgconfig has now gone - but all of the errors at compile time are all still there, and rtl_tcp still crashes. Installing pkg-config got rid of the error, but not much else unfortunarly x.x
ljones
-- :) SP
Apologies for continually replying but I also just noticed these three lines in dmesg as I've been trying all of this out: [ 66.714466] rtl_tcp[3670]: segfault at 0 ip 00007f5d329389f2 sp 00007fff71c8e780 error 6 in libusb-1.0.so.0.1.0[7f5d32930000+15000] [ 87.168292] rtl_tcp[3812]: segfault at 0 ip 00007f0d2fc609f2 sp 00007f0d2e26cb50 error 6 in libusb-1.0.so.0.1.0[7f0d2fc58000+15000] [ 398.814077] rtl_tcp[8760]: segfault at 0 ip 00007f623a1a09f2 sp 00007f62384acb40 error 6 in libusb-1.0.so.0.1.0[7f623a198000+15000] Maybe this is a case of something not liking libusb at all? BTW here's some info on the version of libusb I have installed on my system: # aptitude show libusb-1.0-0 Package: libusb-1.0-0 State: installed Automatically installed: no Multi-Arch: same Version: 2:1.0.16-3 Priority: optional Section: libs ljones On 8/4/13, lee jones <slothpuck@gmail.com> wrote:
I also have re-tried with installing the pkgconfig file recompiling by using autoconf rather than cmake. But I still get lots of errors;
http://slothpuck.no-ip.org/tmp/autoconf-build2.txt
what's concerning me are all those "unused parameter" error messages, as if they aren't being built in and that's maybe why rtl_tcp just hangs or crashes.
ljones
On 8/4/13, lee jones <slothpuck@gmail.com> wrote:
On 8/4/13, lee jones <slothpuck@gmail.com> wrote:
Look at the following line - it is telling you everything you want to know... Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Will try that though not sure why on the other method the configure script wouldn't complete! x.x
Ok I gave that a try. I managed to track down the missing pkgconfig file.
The line about not finding pkgconfig has now gone - but all of the errors at compile time are all still there, and rtl_tcp still crashes. Installing pkg-config got rid of the error, but not much else unfortunarly x.x
ljones
-- :)
SP
-- :) SP
Am Montag, 5. August 2013, 00:01:19 schrieb lee jones:
Apologies for continually replying but I also just noticed these three lines in dmesg as I've been trying all of this out:
[ 66.714466] rtl_tcp[3670]: segfault at 0 ip 00007f5d329389f2 sp 00007fff71c8e780 error 6 in libusb-1.0.so.0.1.0[7f5d32930000+15000] [ 87.168292] rtl_tcp[3812]: segfault at 0 ip 00007f0d2fc609f2 sp 00007f0d2e26cb50 error 6 in libusb-1.0.so.0.1.0[7f0d2fc58000+15000] [ 398.814077] rtl_tcp[8760]: segfault at 0 ip 00007f623a1a09f2 sp 00007f62384acb40 error 6 in libusb-1.0.so.0.1.0[7f623a198000+15000]
Maybe this is a case of something not liking libusb at all? BTW here's some info on the version of libusb I have installed on my system:
# aptitude show libusb-1.0-0 Package: libusb-1.0-0 State: installed Automatically installed: no Multi-Arch: same Version: 2:1.0.16-3 Priority: optional Section: libs
You have missing packages at all - I think *dev-packages. Do you have run 'make clean' before trying to build again? This can reduce error.messages to the ones you need for lacating the problem... Here you can find a small howto on compiling rtlsdr: http://pd0mz.nl/2012/04/13/rtl2832u-chipset-makes-a-cheap-software-defined-r... Good luck Andreas
lee jones wrote:
[ 66.714466] rtl_tcp[3670]: segfault at 0 ip 00007f5d329389f2 sp 00007fff71c8e780 error 6 in libusb-1.0.so.0.1.0[7f5d32930000+15000] [ 87.168292] rtl_tcp[3812]: segfault at 0 ip 00007f0d2fc609f2 sp 00007f0d2e26cb50 error 6 in libusb-1.0.so.0.1.0[7f0d2fc58000+15000] [ 398.814077] rtl_tcp[8760]: segfault at 0 ip 00007f623a1a09f2 sp 00007f62384acb40 error 6 in libusb-1.0.so.0.1.0[7f623a198000+15000]
This shows a crash inside the library. That is caused either by a bug in the library or by a bug in the application.
Maybe this is a case of something not liking libusb at all? BTW here's some info on the version of libusb I have installed on my system:
# aptitude show libusb-1.0-0 Package: libusb-1.0-0 State: installed Automatically installed: no Multi-Arch: same Version: 2:1.0.16-3 Priority: optional Section: libs
Actually this is not libusb at all. You have libusbx installed, it was changed to be the default in debian and several other distributions immediately after a Red Hat employee changed the default in Fedora and wrote a one-line blog post about it. The libusbx community doesn't value code quality highly so it's about equally likely that the problem is in libusbx as that it is in the application calling libusbx. It would be interesting to see the output from a run that uses libusb-1.0.9 or better yet the code from libusb.git, but that requires building it from source and running with the special-built library. You could look at https://libusb.org/wiki/debug for copypaste instructions. //Peter
It would be interesting to see the output from a run that uses libusb-1.0.9 or better yet the code from libusb.git
Should I apt-get remove the libusb (libusbx) before I try this or leave it installed?
Hi, Which version of Debian are you using? I'm using debian 7 but upgraded. Looking at /etc/debian_version it reports "jessie/sid".
ljones On 8/5/13, Peter Stuge <peter@stuge.se> wrote:
lee jones wrote:
[ 66.714466] rtl_tcp[3670]: segfault at 0 ip 00007f5d329389f2 sp 00007fff71c8e780 error 6 in libusb-1.0.so.0.1.0[7f5d32930000+15000] [ 87.168292] rtl_tcp[3812]: segfault at 0 ip 00007f0d2fc609f2 sp 00007f0d2e26cb50 error 6 in libusb-1.0.so.0.1.0[7f0d2fc58000+15000] [ 398.814077] rtl_tcp[8760]: segfault at 0 ip 00007f623a1a09f2 sp 00007f62384acb40 error 6 in libusb-1.0.so.0.1.0[7f623a198000+15000]
This shows a crash inside the library. That is caused either by a bug in the library or by a bug in the application.
Maybe this is a case of something not liking libusb at all? BTW here's some info on the version of libusb I have installed on my system:
# aptitude show libusb-1.0-0 Package: libusb-1.0-0 State: installed Automatically installed: no Multi-Arch: same Version: 2:1.0.16-3 Priority: optional Section: libs
Actually this is not libusb at all. You have libusbx installed, it was changed to be the default in debian and several other distributions immediately after a Red Hat employee changed the default in Fedora and wrote a one-line blog post about it.
The libusbx community doesn't value code quality highly so it's about equally likely that the problem is in libusbx as that it is in the application calling libusbx.
It would be interesting to see the output from a run that uses libusb-1.0.9 or better yet the code from libusb.git, but that requires building it from source and running with the special-built library. You could look at https://libusb.org/wiki/debug for copypaste instructions.
//Peter
-- :) SP
On 8/5/13, lee jones <slothpuck@gmail.com> wrote:
It would be interesting to see the output from a run that uses libusb-1.0.9 or better yet the code from libusb.git
Should I apt-get remove the libusb (libusbx) before I try this or leave it installed?
Hi, Which version of Debian are you using? I'm using debian 7 but upgraded. Looking at /etc/debian_version it reports "jessie/sid".
ljones
I've still not tried this btw. If I remove libusb-1.0-0 it appears it will break all manner of stuff x.x . Is there any sort of workaround possible? ljones
lee jones wrote:
It would be interesting to see the output from a run that uses libusb-1.0.9 or better yet the code from libusb.git
I've still not tried this btw. If I remove libusb-1.0-0 it appears it will break all manner of stuff x.x . Is there any sort of workaround possible?
Use the principle documented at http://libusb.org/wiki/debug //Peter
sigh, it all broke... command line tools still work, rtl_fm will allow me to listen to fm stations, rtl_test shows no errors, but anything else (gqrx, gnuradio) segfaults or just hangs. Haven't recompiled since late july, and will now downgrade from testing to stable and re-attack everything... going to let debian work out the bugs in the libusb transition before attempting testing again. Jared On Mon, Aug 19, 2013 at 5:10 PM, Peter Stuge <peter@stuge.se> wrote:
lee jones wrote:
It would be interesting to see the output from a run that uses libusb-1.0.9 or better yet the code from libusb.git
I've still not tried this btw. If I remove libusb-1.0-0 it appears it will break all manner of stuff x.x . Is there any sort of workaround possible?
Use the principle documented at http://libusb.org/wiki/debug
//Peter
participants (4)
-
df8oe＠gmx.de -
Jared Clements -
lee jones -
Peter Stuge