Re: [Discuss-gnuradio] error using new PyBombs

[Jason Matusiak]

Thanks Stefan.  I ran that and changed the libuhd*.so* to libuhd_bu*.so* 
in both /usr/lib/x86_64-linux-gnu/ and /usr/local/lib/ and yet it still 
fails at the same point.

The only other locations (which aren't in my $PATH or $LD_LIBRARY) are 
/usr/local/oecore-x86_64_older/sysroots/armv7ahf-vfp-neon-oe-linux-gnueabi/......

and

/home/jmatusiak/pybombs/.....  (which is the prefix install point, so 
the tools are putting them there I think).

Anything else I might be missing?  Also, what command can I run once I 
make a change to continue the build without blowing away the 
/home/jmatusiak/pybombs/ directory?  If I run pybombs prefix init 
~/pybombs -a myprefix -R gnuradio-default again I get:
PyBOMBS - INFO - PyBOMBS Version 2.1.1a
PyBOMBS.prefix - ERROR - Ignoring. A prefix already exists in 
`/home/jmatusiak/pybombs'


> This helps a lot to find all installations:
>
> $ sudo find / -name libuhd*.so*
>
> If the path is not inside a pybombs prefix, it is most likely an
> installation by your package manager.
>
> I had this problem as well :P
>
> Greetings
> Stefan
>
> > > For some reason, if you have conflicting UHD versions installed, the
> > > most common place for compilation to break is the swig'ging of the ATR
> > > registers. So: Please make sure there's only one UHD that cmake / swig/
> > > your compiler will find when building!
> > Thank you for the insight Marcus!!  What should I do to get rid of the old
> > UHD, just delete the target folder?  I moved my old pybombs directory to
> > pybombs_old, but I am guessing it can still see the source in there?  I
> > didn't want to delete the old stuff until I knew I had the new stuff
> > working and that I didn't forget to copy any custom files over.
> >
> > ~Jason
> >
> >
> >
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio