Re: [Discuss-gnuradio] 3.7 SWIG mess up

2013-06-01 Thread Sylvain Munaut
Hi, > It seems that CMake couldn't decide between the two python version > installed (I'm on gentoo and it maintains two // python tree) and > decided to use the interpreter of one with the libraries and include > path from the other. Apparently CMake is not bothered one bit by the > fact "v2.7.3"

Re: [Discuss-gnuradio] 3.7 SWIG mess up

2013-05-31 Thread Sylvain Munaut
Hi, > I have only seen this when using make -jN to build. Once it happens, > you either need to do a make clean or to start with an entirely new > build directory to ensure that the swig module in fact gets recompiled > and reinstalled. (It sounds like you did this but it wasn't clear.) Yes, as

Re: [Discuss-gnuradio] 3.7 SWIG mess up

2013-05-31 Thread Johnathan Corgan
On May 31, 2013, at 13:41, Sylvain Munaut <246...@gmail.com> wrote: > Trying to load anything in gnuradio compiled from master just result in : > > ImportError: dynamic module does not define init function (init_runtime_swig) > > I rebuilt it twice, each time starting from scratch and the last tim

[Discuss-gnuradio] 3.7 SWIG mess up

2013-05-31 Thread Sylvain Munaut
Trying to load anything in gnuradio compiled from master just result in : Traceback (most recent call last): File "/opt/gnuradio-3.7/bin/gr_modtool", line 26, in from gnuradio.modtool import * File "/opt/gnuradio-3.7/lib64/python2.7/site-packages/gnuradio/modtool/__init__.py", line 30, i