I’ve been trying out pybombs for building the latest gnuradio. I had a
successful build at home last week, but I am having repeated failures in
test environment VM (virtualbox, ubuntu 12.04 x64).
I am running the build like this: sudo ./pybombs install gnuradio
Here’s the relevant part of the make output:
[ 68%] Built target gnuradio-blocks
Linking CXX shared module _vocoder_swig.so
[ 68%] Built target _vocoder_swig
make: *** [all] Error 2
bash return val = 2
Traceback (most recent call last):
File “./pybombs”, line 91, in
File “/home/spacequest/pybombs/mod_pybombs/pybombs_ops.py”, line 49,
File “/home/spacequest/pybombs/mod_pybombs/recipe.py”, line 512, in
st = self.install_src();
File “/home/spacequest/pybombs/mod_pybombs/recipe.py”, line 582, in
File “/home/spacequest/pybombs/mod_pybombs/recipe.py”, line 612, in
assert(st == 0);
It appears that your error is not with pybombs but with building
Can you post a bit more of the compile log?
I am trying to get you the full output. Apparently tee-ing the output
file results in a truncated file for some reason. Do you know if there
a logging feature in pybombs? I haven’t seen one yet. In any event,
portion I posted was the full extent of the error-related output.
Everything above had proceeded correctly. I sort of wonder if this is
-j4 make option getting in the way. It seems that pybombs is setting
by default, if I am not mistaken.
I realize the build error is with building gnuradio, but pybombs handles
all the dependencies and manages the build process, which is why I am
If you go into the pybombs/src/gnuradio/build directory and run “make
-j4” you’ll replicate exactly what pybombs is doing and maybe get a hint
of what’s up. Plus you can check if just “make” works.
Sent on the Sprint® Now Network from my BlackBerry®