Re: [Discuss-gnuradio] Build GR 3.8 from source

Hi Michael,

'sudo pip3 install click-plugins' took care of the problem with cmake.
Then 'make' started OK, but when it got to 13%, it just hung in a tight
loop. After about an hour of waiting, I did a control-C and it finally
recognized it. I repeated the 'make' and it stopped in the same place.
See the following...

[ 13%] Building CXX object
gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/CMakeFiles/runtime_swig.dir/runtime_swigPYTHON_wrap.cxx.o
/home/pi/gnuradio/build/gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/runtime_swigPYTHON_wrap.cxx:
In function 'void SWIG_Python_addvarlink(PyObject*, char*, PyObject*
(*)(), int (*)(PyObject*))':
/home/pi/gnuradio/build/gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/runtime_swigPYTHON_wrap.cxx:73109:16:
warning: 'char* strncpy(char*, const char*, size_t)' specified bound
depends on the length of the source argument [-Wstringop-overflow=]
strncpy(gv->name,name,size);
~~~~~~~^~~~~~~~~~~~~~~~~~~~
/home/pi/gnuradio/build/gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/runtime_swigPYTHON_wrap.cxx:73106:27:
note: length computed here
size_t size = strlen(name)+1;
~~~~~~^~~~~~
In file included from /usr/include/c++/8/vector:69,
from
/home/pi/gnuradio/build/gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/runtime_swigPYTHON_wrap.cxx:3060:
/usr/include/c++/8/bits/vector.tcc: In function 'void std::vector<_Tp,
_Alloc>::_M_range_insert(std::vector<_Tp, _Alloc>::iterator,
_ForwardIterator, _ForwardIterator, std::forward_iterator_tag) [with
_ForwardIterator = __gnu_cxx::__normal_iterator<const
std::complex<double>*, std::vector<std::complex<double>,
std::allocator<std::complex<double> > > >; _Tp = std::complex<double>;
_Alloc = std::allocator<std::complex<double> >]':
/usr/include/c++/8/bits/vector.tcc:672:7: note: parameter passing for
argument of type 'std::vector<std::complex<double>,
std::allocator<std::complex<double> > >::iterator' {aka
'__gnu_cxx::__normal_iterator<std::complex<double>*,
std::vector<std::complex<double>, std::allocator<std::complex<double> >
> >'} changed in GCC 7.1
vector<_Tp, _Alloc>::
^~~~~~~~~~~~~~~~~~~
/usr/include/c++/8/bits/vector.tcc:672:7: note: parameter passing for
argument of type '__gnu_cxx::__normal_iterator<const
std::complex<double>*, std::vector<std::complex<double>,
std::allocator<std::complex<double> > > >' changed in GCC 7.1
/usr/include/c++/8/bits/vector.tcc:672:7: note: parameter passing for
argument of type '__gnu_cxx::__normal_iterator<const
std::complex<double>*, std::vector<std::complex<double>,
std::allocator<std::complex<double> > > >' changed in GCC 7.1
^Cmake[2]: ***
[gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/build.make:63:
gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/CMakeFiles/runtime_swig.dir/runtime_swigPYTHON_wrap.cxx.o]
Interrupt
make[1]: *** [CMakeFiles/Makefile2:1497:
gnuradio-runtime/swig/CMakeFiles/runtime_swig.dir/all] Interrupt
make: *** [Makefile:141: all] Interrupt

I checked the memory space with 'df' and still have over 25GB available,
so that shouldn't be a problem.

What do you suggest?

Thanks,
---
Barry Duggan

On 2019-07-20 19:26, Michael Dickens wrote:
> Here are the (current) key issues:
> {{{
> -- Python checking for click - found
> -- Python checking for click-plugins - not found
> }}}
>
> These are Python packages. If you get them installed hopefully the
> "cmake" command will finish & you can get on with building from
> source! - MLD
>
> On Sat, Jul 20, 2019, at 6:56 PM, Barry Duggan wrote:
>> I used """cmake -DENABLE_GR_UHD=OFF
>> -DCMAKE_INSTALL_PREFIX="/usr/local"
>> -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/usr/bin/python3 ../ >
>> cmake_out.txt 2>&1""". The file is attached.
>>
>> There are several 'missing' packages, but I don't know which ones are
>> important.
>> ---
>> Barry Duggan
>>
>> Attachments:
>> * cmake_out.txt

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio