On 04/20/2021 07:07 PM, Brendan Horsfield wrote:
Hi Cédric,
Results of dpkg queries are given below. It looks like those files
are not part of any installed packages:
$ dpkg -S "libuhd.so.003.010.003" --> dpkg-query: no path found
matching pattern *libuhd.so.003.010.003*
$ dpkg -S "$(basename
"/usr/lib/x86_64-linux-gnu/libuhd.so.003.010.003")" --> dpkg-query:
no path found matching pattern *libuhd.so.003.010.003*
$ dpkg -S "libuhd.so.3.15.0" --> dpkg-query: no path found matching
pattern *libuhd.so.3.15.0*
$ dpkg -S "$(basename "/usr/lib/x86_64-linux-gnu/libuhd.so.3.15.0")"
--> dpkg-query: no path found matching pattern *libuhd.so.3.15.0*
What I find interesting is that when I run "gnuradio-companion" from
the terminal, it attempts to load my 2 most recent flowgraphs
"save_rx_samples_to_file.grc" and "spectrum_analyser_two_chan.grc",
even though I have never opened them in this version of
gnuradio-companion. This suggests that the built-from-source
installation has been polluted by a config file or history file from
the Ubuntu Software version of GRC that I installed over the top of
the built-from-source version.
The various versions all share the same .gnuradio directory in your home
directory, so I would expect some tripping over
each others feet.
I think I will try and scrub my system of everything related to GNU
Radio this morning, and reinstall it from source one more time. If it
still doesn't work, I will take it up with the GNU Radio mailing
list...........or possibly switch to Matlab!! :)
On Ubuntu 18.04, Gnu Radio and UHD installed from the official
repositories "just works", but won't have the Python API you're looking for.
Your problems have basically been caused by switching between various
install methods, various versions, and not really having
a good understanding of what is going on underneath. The
package-management system cannot know nor make any rational
decisions about bits and pieces you may have installed from source,
and the install-from-source has very little insight into what
you might have installed from the package management system. Once
you venture into "install from source" territory, you're
basically doing the same tasks that a systems software developer
would do, and the tools necessarily assume that you know
how to take on that role. If you're doing a lot of this "back and
forth" from various package repositories, the official repositories,
and source-based installs, you really need to be a "Linux Geek" in
order not to create the "tangle" that you've created for yourself.
Thanks & Regards,
Brendan.
On Wed, Apr 21, 2021 at 1:14 AM Cédric Hannotier via USRP-users
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> wrote:
Hi Brendan,
On 21/04/21 00:01, Brendan Horsfield wrote:
>> I do not get this part. What do you mean by "reinstalled"?
>> Did you installed GNU Radio from source or from Ubuntu Software?
>> If you download the source, build and install it (following GNU
Radio
>> wiki),
>> then you cannot install it using Ubuntu Software (or apt)
afterwards.
>> It is one or the other, not both.
>
> Hmm. I have been assuming all this time that GNU Radio
Companion is an
> optional GUI front end for GNU Radio, which must be installed
separately.
>
> In my case, I definitely installed GNU Radio from source.
However, when
> that was finished, I then went into Ubuntu Software and
installed GNU Radio
> Companion, which placed an icon on my toolbar (which is how I
launch the
> application). I am guessing this was the wrong thing to do?
Yep, wrong way.
gnuradio-companion is provided by gnuradio. It is not separated.
Most of the time,
doing "from source" installs everything under /usr/local/,
while "from binaries" installs everything under /usr/.
If you install both, you end up with 2 versions.
Best case scenario is one is masking the other.
Worst case scenario is clash between the two.
> FYI -- If I open a terminal and type "gnuradio-companion", the
GUI never
> launches, and all I get is the following error message:
>
> $ gnuradio-companion
> <<< Welcome to GNU Radio Companion 3.9.0.0 >>>
>
> Block paths:
> /usr/local/share/gnuradio/grc/blocks
>
> Loading:
>
"/home/anyone/Documents/Brendan/GNU-Radio/save_rx_samples_to_file.grc"
> >>> Converting from XML
> /usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't
> resolve package from __spec__ or __package__, falling back on
__name__ and
> __path__
> return f(*args, **kwds)
> >>> Done
>
> Loading:
>
"/home/anyone/Documents/Brendan/GNU-Radio/spectrum_analyser_two_chan.grc"
> >>> Converting from XML
> Segmentation fault (core dumped)
I do not know why it segfaults.
If it does not solve by itself after solving the other parts,
you could try GNU Radio 3.8 or ask on GNU Radio ML.
> To answer your other questions:
>
> If I type "/sbin/ldconfig -p | grep -F libuhd", here is what I get:
> libuhd.so.4.0.0 (libc6,x86-64) => /usr/local/lib/libuhd.so.4.0.0
> libuhd.so.3.15.0 (libc6,x86-64) =>
> /usr/lib/x86_64-linux-gnu/libuhd.so.3.15.0
> libuhd.so.003.010.003 (libc6,x86-64) =>
> /usr/lib/x86_64-linux-gnu/libuhd.so.003.010.003
> libuhd.so (libc6,x86-64) => /usr/local/lib/libuhd.so
>
> Finally, when I type dpkg -S "(libuhd.so.003.010.003
> "/usr/lib/x86_64-linux-gnu")", I get the response
> dpkg-query: no path found matching pattern *(libuhd.so.003.010.003
> /usr/lib/x86_64-linux-gnu)*
Sorry if I was not clear, use:
dpkg -S "libuhd.so.003.010.003"
or:
dpkg -S "$(basename
"/usr/lib/x86_64-linux-gnu/libuhd.so.003.010.003")"
I do not feed the fullpath to "dpkg -S" because with the /usr/ merge,
dpkg can be confused.
Could you do the same for libuhd.so.3.15.0?
Regards
--
Cédric Hannotier
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
<mailto:usrp-users-le...@lists.ettus.com>
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
