[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] FunCube Dongle pro +

From: Marcus Müller
Subject: Re: [Discuss-gnuradio] FunCube Dongle pro +
Date: Sat, 01 Nov 2014 01:39:52 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

Tracing this down; Daniel, could you share what
pkg-config --static --libs libsub-1.0
in your build directory, can you do a
ldd lib/libgnuradio-fcdproplus.so

Greetings, and good night (forgot the time)

On 11/01/2014 01:04 AM, Marcus Müller wrote:
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.


On 11/01/2014 12:43 AM, Sylvain Munaut wrote:
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.



Discuss-gnuradio mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]