# Re: FunCube Dongle pro + **URL:** \ **Category:** GNU Radio\ **Created:** [October 31, 2014, 11:31pm UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862 "2014-10-31T23:31:57Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\ **Post date:** [October 31, 2014, 11:31pm UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/1 "2014-10-31T23:31:57Z")
> This is because the version of the libusb library you have is too old to have > that particular API call in it. I use ubuntu 12.04 and libusb-1.0-0-dev Do you what version of libusb is compatible? ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 12:01am UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/2 "2014-11-01T00:01:46Z")
The problem is that Ubuntu 12.04 seems to carry 1.0.9 around, so this seems strange. I’m a bit conflicted – the missing symbol looks like it should belong to libudev and not libusb-versionhell. This might indicate that you’re bound to update libudev, which is rather system central, and which might be a bit of a hassle; I’d personally recommend updating to Ubuntu 14.04 LTS or the brand new 14.10 [1]. It feels like the module should link against libudev, as it includes libudev.h and uses symbols from that library, but I can’t find a single reference to udev in the cmake files of gr-fcdproplus. this is but a shot in the dark, but could you delete the contents of your build folder, and rund cmake with “-DCMAKE\_CXX\_FLAGS=-ludev” Greetings, Marcus [1] [https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Upgrading\_from\_Ubuntu\_12.04\_LTS\_or\_Ubuntu\_13.10](https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Upgrading_from_Ubuntu_12.04_LTS_or_Ubuntu_13.10) ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [October 31, 2014, 11:42pm UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/3 "2014-10-31T23:42:06Z")
On 10/31/2014 06:27 PM, Daniel B. wrote: > > This is because the version of the libusb library you have is too old > > to have that particular API call in it. > > I use ubuntu 12.04 and libusb-1.0-0-dev > Do you what version of libusb is compatible? > I think that 1.0.9 and newer are compatible. ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 12:30am UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/4 "2014-11-01T00:30:24Z")
If I was forced to make a wild guess I’d probably assume it uses some USB-HID interface for configuration, and udev for hotplug detection. I think I’ll have the libery of including Mr. Schroer in this discussion 🙂 Greetings, Marcus ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 12:44am UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/5 "2014-11-01T00:44:43Z")
What I find strange is that the symbol error is found at runtime and not at link-time. That suggest either there is two libudev and the one used for runtime is different than the one found for link-time, or that this library was copied over from another system. Cheers, Sylvain ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 12:05am UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/6 "2014-11-01T00:05:57Z")
On 10/31/2014 07:00 PM, Marcus M. wrote: > single reference to udev in the cmake files of gr-fcdproplus. > > > On 10/31/2014 06:27 PM, Daniel B. wrote: > > > > > > This is because the version of the libusb library you have is too > > > > old to have that particular API call in it. > > > > > > I use ubuntu 12.04 and libusb-1.0-0-dev > > > Do you what version of libusb is compatible? > > > I think that 1.0.9 and newer are compatible. Hmm, I wonder why it cares about udev? When I saw “enumerate” I thought this was a libusb thing, but clearly not. I thought that FCD devices just “manifested” as audio anyway–no direct libusb required? ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 1:05am UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/7 "2014-11-01T01:05:36Z")
Oh indeed, good point! Sylvain: you’re right. How gr-fcdproplus ends up being able to compile and link is still a mystery to me. I was expecting a horrible “symbol export forwarding hack” involving libusb, but no: $\>nm -D /lib64/libusb-1.so U udev\_device\_get\_action U udev\_device\_get\_devnode U udev\_device\_get\_sysname U udev\_device\_new\_from\_syspath U udev\_device\_unref U udev\_enumerate\_add\_match\_subsystem U udev\_enumerate\_get\_list\_entry U udev\_enumerate\_new … gives me all of the udev symbols as undefined, which obviously is correct, because they should be dynamically loaded from libusb: $\>ldd /lib64/libusb-1.0.so libusb-1.0.so|grep udev linux-vdso.so.1 =\> (0x00007fff6b7fc000) libudev.so.1 (0x00000038b6600000) … Trying to build this now, but I’m currently on a machine where I haven’t even installed GR yet 😕 this might take a second. Greetings, Marcus ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 1:41am UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/8 "2014-11-01T01:41:22Z")
Tracing this down; Daniel, could you share what pkg-config --static --libs libsub-1.0 says? in your build directory, can you do a ldd lib/libgnuradio-fcdproplus.so Greetings, and good night (forgot the time) Marcus ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 11:01am UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/9 "2014-11-01T11:01:34Z")
udev\_enumerate\_new is called from the latest hidapi code. Some distros provide a hidapi package. So the actual fcdproplus tries to detect if an hidapi package is installed. Otherwise it uses the hidapi code provided with fcdproplus, which uses udev\_enumerate\_new. So it would be interesting waht cmake has reported. Near the end of the cmake output you see something like this ( in the case that the hidapi package is installed): GNURADIO\_PMT\_FOUND = TRUE – checking for module ‘alsa’ – found alsa, version 1.0.28 – Found ALSA 1.0.28 – checking for module ‘libusb-1.0’ – found libusb-1.0, version 1.0.19 – Found libusb-1.0: /usr/include/libusb-1.0, /usr/lib64/libusb-1.0.so – Found Doxygen: /usr/bin/doxygen (found version “1.8.5”) – System Hidapi Lib /usr/lib64/libhidapi-libusb.so is used – Audio LIBS: /usr/local/gnuradio-orig/lib/libgnuradio-audio.so As Marcus already proposed, it might be helpfull to see the output of ldd lib/libgnuradio-fcdproplus.so inside the build directory and additionally from the gnuradio install directory. I think udev\_enumerate\_new is provided from newer versions of libudev. If you want to use a hidapi version without udev\_enumerate\_new just checkout the with\_hidapi release. – Volker Am 01.11.2014 um 01:39 schrieb Marcus M.: ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [November 1, 2014, 4:30pm UTC](https://www.ruby-forum.com/t/re-funcube-dongle-pro/232862/10 "2014-11-01T16:30:47Z")
Thank you all for your help! As Marcus suggested, by passing the “-DCMAKE\_CXX\_FLAGS=-ludev” in cmake, I managed to solve the problem. I report here the output of the command “pkg-config --static --libs libusb-1.0”: -pthread -lusb-1.0 -lrt and the output of the command: “ldd lib/libgnuradio-fcdproplus.so” ``` linux-vdso.so.1 => (0x00007fff107ff000) libhidapi-libusb.so.0 => /usr/local/lib/libhidapi-libusb.so.0 ``` (0x00007fcdf2952000) libboost\_system.so.1.48.0 =\> /usr/lib/libboost\_system.so.1.48.0 (0x00007fcdf2736000) libgnuradio-runtime-3.7.5.1.so.0.0.0 =\> /usr/local/lib/libgnuradio-runtime-3.7.5.1.so.0.0.0 (0x00007fcdf2459000) libgnuradio-blocks-3.7.5.1.so.0.0.0 =\> /usr/local/lib/libgnuradio-blocks-3.7.5.1.so.0.0.0 (0x00007fcdf1fbe000) libgnuradio-audio-3.7.5.1.so.0.0.0 =\> /usr/local/lib/libgnuradio-audio-3.7.5.1.so.0.0.0 (0x00007fcdf1d8c000) libstdc++.so.6 =\> /usr/lib/x86\_64-linux-gnu/libstdc++.so.6 (0x00007fcdf1a8b000) libgcc\_s.so.1 =\> /lib/x86\_64-linux-gnu/libgcc\_s.so.1 (0x00007fcdf1875000) libc.so.6 =\> /lib/x86\_64-linux-gnu/libc.so.6 (0x00007fcdf14b6000) librt.so.1 =\> /lib/x86\_64-linux-gnu/librt.so.1 (0x00007fcdf12ad000) libusb-1.0.so.0 =\> /lib/x86\_64-linux-gnu/libusb-1.0.so.0 (0x00007fcdf109e000) libpthread.so.0 =\> /lib/x86\_64-linux-gnu/libpthread.so.0 (0x00007fcdf0e81000) libvolk.so.0.0.0 =\> /usr/local/lib/libvolk.so.0.0.0 (0x00007fcdf0b66000) libgnuradio-pmt-3.7.5.1.so.0.0.0 =\> /usr/local/lib/libgnuradio-pmt-3.7.5.1.so.0.0.0 (0x00007fcdf0923000) libboost\_filesystem.so.1.48.0 =\> /usr/lib/libboost\_filesystem.so.1.48.0 (0x00007fcdf0704000) libboost\_thread.so.1.48.0 =\> /usr/lib/libboost\_thread.so.1.48.0 (0x00007fcdf04e8000) libm.so.6 =\> /lib/x86\_64-linux-gnu/libm.so.6 (0x00007fcdf01ec000) libasound.so.2 =\> /usr/lib/x86\_64-linux-gnu/libasound.so.2 (0x00007fcdefefe000) /lib64/ld-linux-x86-64.so.2 (0x00007fcdf2d6b000) liborc-0.4.so.0 =\> /usr/lib/x86\_64-linux-gnu/liborc-0.4.so.0 (0x00007fcdefc83000) libdl.so.2 =\> /lib/x86\_64-linux-gnu/libdl.so.2 (0x00007fcdefa7f000) Although FCDpro+ run now, grnuradio crashes. I see nothing on FFT and a lot of “aOaOaOaOaOaOaO” in Reports area. Thank you again On Saturday, November 1, 2014 12:01 PM, Volker S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: udev\_enumerate\_new is called from the latest hidapi code. Some distros provide a hidapi package. So the actual fcdproplus tries to detect if an hidapi package is installed. Otherwise it uses the hidapi code provided with fcdproplus, which uses udev\_enumerate\_new. So it would be interesting waht cmake has reported. Near the end of the cmake output you see something like this ( in the case that the hidapi package is installed): GNURADIO\_PMT\_FOUND = TRUE – checking for module ‘alsa’ – found alsa, version 1.0.28 – Found ALSA 1.0.28 – checking for module ‘libusb-1.0’ – found libusb-1.0, version 1.0.19 – Found libusb-1.0: /usr/include/libusb-1.0, /usr/lib64/libusb-1.0.so – Found Doxygen: /usr/bin/doxygen (found version “1.8.5”) – System Hidapi Lib /usr/lib64/libhidapi-libusb.so is used – Audio LIBS: /usr/local/gnuradio-orig/lib/libgnuradio-audio.so As Marcus already proposed, it might be helpfull to see the output of ldd lib/libgnuradio-fcdproplus.so inside the build directory and additionally from the gnuradio install directory. I think udev\_enumerate\_new is provided from newer versions of libudev. If you want to use a hidapi version without udev\_enumerate\_new just checkout the with\_hidapi release. – Volker Am 01.11.2014 um 01:39 schrieb Marcus M.: > On 11/01/2014 01:04 AM, Marcus M. wrote: > > > ``` > > U udev_device_new_from_syspath > > > > ``` > > > > $\>ldd /lib64/libusb-1.0.so > > Marcus > > > > > ``` > > > Sylvain > > > > > > ``` > > > > * * * > > > > Discuss-gnuradio mailing list > > [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > > [Discuss-gnuradio Info Page](https://lists.gnu.org/mailman/listinfo/discuss-gnuradio)