As it seems, at compile time, the 5.1.1 version was used, whilst at
runtime the 5.2.0 version from your ~/Documents/target prefix seems to
be found. That's a bit strange, since pybombs should use the qwt version
that it downloaded (ie. 5.2.0 in your case). Maybe it's all the other
way around...

If you

export LD_PRELOAD=/usr/lib64/libqwt.so.5

before running your GNU Radio application from the same terminal, does
it help? what about using export
LD_PRELOAD=/home/tsvcis/Documents/pybombs/src/qwt5/lib/libqwt.so.5**?

Greetings,
Marcus

**
On 01/26/2015 10:46 PM, Richard Bell wrote:
> OK Marcus. The shared object file does exist in two directories. Full
> output of comands below, with matches bolded:
>
> ldd
> /home/tsvcis/Documents/target/lib64/libgnuradio-qtgui-3.7.7git.so.0.0.0 |
> grep qwt
>
>   *  libqwt.so.5 => /home/tsvcis/Documents/target/lib/libqwt.so.5
> (0x00007f5d2a4c1000)*
>
>
> [tsvcis@tsvtester ~]$ sudo find / -name 'libqwt.so.5*'
> [sudo] password for tsvcis:
> /home/tsvcis/Documents/pybombs/src/qwt5/lib/libqwt.so.5.2.0
> /home/tsvcis/Documents/pybombs/src/qwt5/lib/libqwt.so.5.2
> */home/tsvcis/Documents/pybombs/src/qwt5/lib/libqwt.so.5*
> /home/tsvcis/Documents/target/lib/libqwt.so.5.2.0
> /home/tsvcis/Documents/target/lib/libqwt.so.5.2
> */home/tsvcis/Documents/target/lib/libqwt.so.5*
> */usr/lib64/libqwt.so.5*
> /usr/lib64/libqwt.so.5.1.1
> /usr/lib64/libqwt.so.5.1
>
> The only thing I could think to do was rename the files in /usr/lib64.
> I don't see this as having an effect. What should I do to resolve this
> from here?
>
> Thanks a lot,
> Rich
>
> On Mon, Jan 26, 2015 at 11:31 AM, Marcus Müller
> <[email protected] <mailto:[email protected]>> wrote:
>
>     Hi Richard,
>
>     this looks like you've installed a "good" version of QWT, which is
>     used when building GNU Radio, but when running a GNU Radio
>     program, a different version of the QWT library is loaded, which
>     leads to missing symbols.
>
>     My first approach would be to run ldd on
>     /home/tsvcis/Documents/target/lib64/libgnuradio-qtgui-3.7.7git.so.0.0.0
>     , and see which qwt lib linux will try to load at runtime:
>     ldd
>     
> /home/tsvcis/Documents/target/lib64/libgnuradio-qtgui-3.7.7git.so.0.0.0|grep
>     qwt.
>
>     Then search for files that have the same base name, in this case
>     libqwt.so .
>
>     Greetings,
>     Marcus
>
>     On 01/26/2015 07:59 PM, Richard Bell wrote:
>>     *Problem*: I can't use qtgui blocks. Wxgui blocks work. My system
>>     is CentOS 6.6 running gnuradio 3.7.6 installed using pybombs.
>>
>>     *Debug*: I've run cmake in pybombs/gnuradio/src/build to make
>>     sure qtgui was enabled during install, and it is. The only
>>     gnuradio components disabled that are listed by cmake are
>>     doxygen, sphinx, gr-comedi and gr-zeromq.
>>
>>     I then opened a terminal to test library imports. I can 'import
>>     gnuradio' and I can 'from gnuradio import wxgui', as you would
>>     expect. When I try, 'from gnuradio import qtgui', I get the
>>     following output:
>>
>>     >>> import gnuradio
>>     >>> from gnuradio import wxgui
>>     >>> from gnuradio import qtgui
>>     Traceback (most recent call last):
>>       File "<stdin>", line 1, in <module>
>>       File
>>     
>> "/home/tsvcis/Documents/target/lib64/python2.6/site-packages/gnuradio/qtgui/__init__.py",
>>     line 34, in <module>
>>         from qtgui_swig import *
>>       File
>>     
>> "/home/tsvcis/Documents/target/lib64/python2.6/site-packages/gnuradio/qtgui/qtgui_swig.py",
>>     line 26, in <module>
>>         _qtgui_swig = swig_import_helper()
>>       File
>>     
>> "/home/tsvcis/Documents/target/lib64/python2.6/site-packages/gnuradio/qtgui/qtgui_swig.py",
>>     line 22, in swig_import_helper
>>         _mod = imp.load_module('_qtgui_swig', fp, pathname, description)
>>     ImportError:
>>     /home/tsvcis/Documents/target/lib64/libgnuradio-qtgui-3.7.7git.so.0.0.0:
>>     undefined symbol: _ZN7QwtPlot16staticMetaObjectE
>>     >>>
>>
>>     *Conclusion: *There is a problem with my qtgui install but I
>>     don't know how to debug any further to apply a fix. I've googled
>>     the traceback output with no luck. I'm hoping someone has come
>>     across and fixed this issue before who could explain what's going on.
>>
>>     v/r,
>>     Rich
>>
>>
>>     _______________________________________________
>>     Discuss-gnuradio mailing list
>>     [email protected] <mailto:[email protected]>
>>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>     _______________________________________________
>     Discuss-gnuradio mailing list
>     [email protected] <mailto:[email protected]>
>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>

_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to