[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] 'module' object has no attribute
From: |
Guy Durrieu |
Subject: |
Re: [Discuss-gnuradio] 'module' object has no attribute |
Date: |
Wed, 19 Dec 2018 08:13:31 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 |
Le 18/12/2018 à 06:50, Guy Durrieu a écrit :
> Dave and Andrej,
>
> Thanks for your help ! I'll try your suggestions as soon as possible.
>
> Best regards.
>
> -- GD.
Hi,
I did the verifications suggested by Dave and Andrej.
What puzzle me is: despite the following declarations
----
boost::chrono::system_clock::time_point now =
boost::chrono::system_clock::now() ;
boost::chrono::system_clock::time_point nextperiod = now +
boost::chrono::milliseconds{d_period} ;
----
and although the make terminates without any error, there is no
reference to libboost_chrono.so in the generated swig.so:
---
$ ldd _wireless_swig.so
linux-vdso.so.1 (0x00007fff3cdb9000)
libpython2.7.so.1.0 => /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
(0x00007faf505bf000)
libgnuradio-wireless-1.0.0git.so.0.0.0 =>
/LOCAL/DURRIEU/gnuradio/lib/libgnuradio-wireless-1.0.0git.so.0.0.0
(0x00007faf5037a000)
libboost_system.so.1.65.1 =>
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.65.1 (0x00007faf50175000)
libgnuradio-runtime-3.7.12.0.so.0.0.0 =>
/LOCAL/DURRIEU/gnuradio/lib/libgnuradio-runtime-3.7.12.0.so.0.0.0
(0x00007faf4fde4000)
libgnuradio-pmt-3.7.12.0.so.0.0.0 =>
/LOCAL/DURRIEU/gnuradio/lib/libgnuradio-pmt-3.7.12.0.so.0.0.0
(0x00007faf4fb8f000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10
(0x00007faf4f90e000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007faf4f585000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007faf4f36d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007faf4ef7c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007faf4ed5f000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007faf4eb40000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007faf4e93c000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007faf4e739000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007faf4e39b000)
libthrift-0.9.3.so => /LOCAL/DURRIEU/gnuradio/lib/libthrift-0.9.3.so
(0x00007faf4e06c000)
libvolk.so.1.4 => /LOCAL/DURRIEU/gnuradio/lib/libvolk.so.1.4
(0x00007faf4dd04000)
libboost_program_options.so.1.65.1 =>
/usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.65.1
(0x00007faf4da83000)
libboost_filesystem.so.1.65.1 =>
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.65.1 (0x00007faf4d869000)
libboost_thread.so.1.65.1 =>
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.65.1 (0x00007faf4d644000)
liblog4cpp.so.5 => /usr/lib/x86_64-linux-gnu/liblog4cpp.so.5
(0x00007faf4d407000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007faf4d1ff000)
/lib64/ld-linux-x86-64.so.2 (0x00007faf50d9e000)
libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
(0x00007faf4cf97000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
(0x00007faf4cb54000)-
----
While if I try a simple test with the same declarations, it obviously
only works if libboost_chrono.so is referenced:
----
$ ldd a.out
linux-vdso.so.1 (0x00007fff7a615000)
libboost_chrono.so.1.65.1 =>
/usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.65.1 (0x00007f0873b96000)
libboost_system.so.1.65.1 =>
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.65.1 (0x00007f0873991000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f0873608000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007f08733f0000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0872fff000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0872df7000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f0872bd8000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f087283a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f0873fa2000)
----
I definitely don't understand what happens here during the make process.
Does it mean that boost/chrono functionnalities are not usable with
GNUradio ?
Thanks for your help.
-- GD.
Guy Durrieu
ONERA - Département Traitement de l'Information et Systèmes
CEntRe de Toulouse, 2, avenue Edouard Belin BP 74025 31055 TOULOUSE CEDEX 4
Tél. +33 5 62 25 26 59
avertissement http://www.onera.fr/onera-en/emails-terms