Re: gr-display "import display" causes error

Thanks Ron for your two answers. That solved my problem.

Jim

-----Original Message-----
From: Ron Economos
Sent: Wednesday, November 20, 2024 10:48 PM
To: discuss-gnuradio@gnu.org
Subject: Re: gr-display "import display" causes error

You have to do:

sudo ldconfig

also.

Ron

On 11/20/24 19:32, Elmore Family wrote:
> Ron,
>
> I still get the same error using /usr.
>
> Jim
>
> -----Original Message----- From: Ron Economos
> Sent: Wednesday, November 20, 2024 4:48 PM
> To: discuss-gnuradio@gnu.org
> Subject: Re: gr-display "import display" causes error
>
> You should have used:
>
> cmake -DCMAKE_INSTALL_PREFIX=/usr
>
> You should also use that for any OOT you install.
>
> Ron
>
> On 11/20/24 11:50, Elmore Family wrote:
>> Marcus,
>>
>> I have discovered I made two errors in this process which may be
>> contributing to this issue. However, here is what I have done and the
>> results.
>>
>> I followed the procedure that Volker outlined in the README from his
>> Github project.
>>
>> cmake -DCMAKE_INSTALL_PREFIX=/usr/bin is executed from the build
>> directory where I stored the gr-display files. /usr/bin is the directory
>> where gnuradio is installed. I assumed this directory to be correct since
>> it contains gnuradio- companion. Volker states:
>> **Hint:**
>> You can install gr-display to an other directory than gnuradio. But then
>> you have to add
>> the location of your python modules to the PYTHONPATH environment
>> variable and add the location of
>> the lib to the LD_LIBRARY_PATH environment variable.
>>
>> Since I installed gr-display to the directory containing gnuradio (I
>> think) I understood from the above hint that I didn't need to touch the
>> environment variables.
>>
>> I then performed "make" and "sudo make install" .
>>
>> The gr-display OOT is now in gnuradio and was included in the flowchart.
>>
>> Also, the README has the following:
>> To see the newly created blocks in grc you have to set the
>> local_blocks_path entry in ~/.gnuradio/config.conf.
>> Example: If you choose /usr/local/oot as installation directory, you have
>> to set
>> local_blocks_path = /usr/local/oot/share/gnuradio/grc/blocks
>>
>> I didn't do this since the OOT was installed in grc. Should I do this?
>>
>> When I run the flowchart, I get the error shown in my original posting.
>>
>> "libgnuradio-display..." is installed in "/usr/bin/lib/aarch64-linux-gnu"
>> and also in"/usr/local/lib/aarch64-linux-gnu". The install_manifest.txt
>> shows installation in the "/usr/bin/lib/aarch64-linux-gnu" directory. I
>> checked the /usr/local since you had mentioned it.
>>
>> So, the file is in 2 locations??? Is this the problem? Did I choose an
>> incorrect directory for the gnuradio location? BTW if I run
>> "gnuradio-config-info --prefix", the result is "/usr/".
>>
>> Jim
>>
>> -----Original Message----- From: Marcus Müller
>> Sent: Wednesday, November 20, 2024 7:52 AM
>> To: discuss-gnuradio@gnu.org ; Elmore's
>> Subject: Re: gr-display "import display" causes error
>>
>> Hi Jim,
>>
>> sounds like you have a local installation of gr-display (in /usr/local)
>> and the python
>> part can't find the underlying compiled C++ library. Can you check where
>> "libgnuradio-display…" has been installed to (since you probably compiled
>> this yourself,
>> there might be a `install_manifest.txt` in your build folder). That
>> directory (something
>> like /usr/local/lib64 maybe?) needs to be in the LD_LIBRARY_PATH
>> environment variable for
>> the automatic Linux library finder to be able to find it :)
>>
>> Best regards,
>> Marcus
>>
>> On 16.11.24 02:43, Elmore Family wrote:
>>> I have installed gr-display and added it to my flowgraph. When I run the
>>> flowgraph I get the following:
>>> Traceback (most recent call last):
>>> File "/home/wa4ywm/Softrock/Softrock_FT8.py", line 26, in <module>
>>> import display
>>> File "/usr/local/lib/python3.11/dist-packages/display/__init__.py",
>>> line 22, in <module>
>>> from .display_python import *
>>> ImportError: libgnuradio-display.so.3.10.0: cannot open shared object
>>> file: No such file or directory
>>> Note that when I performed the build I used the instructions in the
>>> README file. The "cmake –DCMAKE_INSTALL_PREFIX = " failed. So I used
>>> cmake ../ to build the OOT.
>>> Thanks for any help.
>>> Jim
>>
>
>


--
This email has been checked for viruses by AVG antivirus software.
www.avg.com