[Top][All Lists]

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

Re: [Discuss-gnuradio] undefined symbols, causes?

From: Ilia Mirkin
Subject: Re: [Discuss-gnuradio] undefined symbols, causes?
Date: Fri, 28 Apr 2006 15:16:43 -0400
User-agent: Internet Messaging Program (IMP) H3 (4.0.3)

Usually when something like this happens, you have some versioning problems
between interfaces. And indeed your files reveal this:


atsc_fpll_sptr atsc_make_fpll();


atsc_fpll_sptr atsc_make_fpll(double a_initial_freq) { ... }

You need to figure out which interface is the right one, and use that.

I think that "f" means float, and "v" means void, for the arguments in the name


Quoting Charles Swiger <address@hidden>:

Any tips what could cause this, Python does not like the
'U'ndefined symbol.

.../gnuradio/_atsc.so: undefined symbol: _Z14atsc_make_fpllv

$ nm _atsc.so | grep atsc_make_fpll
0004e9c0 T _Z14atsc_make_fplld
        U _Z14atsc_make_fpllv

Checking the .libs objects:

$ nm atsc_fpll.o | grep atsc_make_fpll
00000cf0 T _Z14atsc_make_fplld


$ nm atsc.o | grep atsc_make_fpll
        U _Z14atsc_make_fpllv             <--- oh no!!!

SWIG missing something.
Files attached.


reply via email to

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