discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem building OOTs with GR 3.9.3.0 PPA package


From: Josh Morman
Subject: Re: Problem building OOTs with GR 3.9.3.0 PPA package
Date: Sat, 16 Oct 2021 16:29:13 -0400

I've requested deletion of the pybind11 package from the PPA (this takes a few hours) - it should not be in there as 20.04 has a decent version of pybind11.  So at least by tomorrow, uninstalling  pybind11 and reinstalling should resolve the issue.


On Sat, Oct 16, 2021 at 2:56 PM schneider <schneider@xtort.eu> wrote:
Hi,

so I think I have an idea what happened:

My guess is that the 20.04 PPA was built using pybind11 2.4.3-2build2:
https://launchpadlibrarian.net/563330294/buildlog_ubuntu-focal-amd64.gnuradio_3.9.3.0-0~gnuradio~focal-3_BUILDING.txt.gz

If I uninstall the pybind11 version from the PPA and install pybind11
from the Ubuntu repositories, I can compile and run our OOT:

apt install pybind11-dev=2.4.3-2build2

I guess the PPA needs to be built again against the pybind11 version
which is included in the PPA.

Best
schneider


On 16.10.21 20:35, Daniel Estévez wrote:
> Hi,
>
> I can confirm that when the Docker container builds, it's installing
> pybind11-dev 2.5.0 from the PPA, as schneider mentions.
>
> This happens in
> https://github.com/daniestevez/gr-satellites/runs/3910245472
>
> Get:406 http://ppa.launchpad.net/gnuradio/gnuradio-releases/ubuntu
> focal/main amd64 pybind11-dev all 2.5.0-4~ubuntu20.04.1~ppa1 [138 kB]
>
> Yet I get the import error. So it seems something is wrong regarding the
> pybind11-dev package in the PPA?
>
> Best,
>
> Dani
>
> El 16/10/21 a las 20:10, schneider escribió:
>> Hi
>>
>> I'm experiencing the same issue with our OOT. I've got pybind11-devc
>> 2.5.0-4~ubuntu20.04.1~ppa1 installed from the PPA.
>>
>> If I also install gnuradio-dev from the PPA, I get the error mentioned
>> by Daniel. If I build GNURadio 3.9.3 from source (same pybind version as
>> mentioned above), the error goes away.
>>
>> It's not obvious to me what happening. My first questions would be: Was
>> gnuradio-dev in the PPA built using the pybind11 version which is
>> available in the PPA? Does pybind11 version in the PPA need an update?
>>
>> Best
>> schneider
>>
>> On 15.10.21 22:55, Ron Economos wrote:
>>> I just went through this myself with a user of my OOT's. It's due to a
>>> pybind11 version mismatch. The PPA is built with pybind11 v2.5.0 and if
>>> your system (such as Ubuntu 20.04) has a different version, you get that
>>> import error.
>>>
>>> You have to build/install pybind11 v2.5.0 on your system to resolve the
>>> issue.
>>>
>>> Here's the issue on my Github for reference.
>>>
>>> https://github.com/drmpeg/gr-dvbgse/issues/3
>>>
>>> Ron
>>>
>>> On 10/15/21 12:30 PM, Daniel Estévez wrote:
>>>> Hi,
>>>>
>>>> I've encountered a problem in the gr-satellites continuous integration
>>>> that I've traced to the change from GNU Radio 3.9.2.0 to 3.9.3.0 in
>>>> the Ubuntu 20.04 PPA package (which is what I'm using in my CI Docker
>>>> container).
>>>>
>>>> The problem is that after building gr-satellites from source using GNU
>>>> Radio 3.9.3.0 from the PPA package I get this error when importing the
>>>> Python module:
>>>>
>>>> Traceback (most recent call last):
>>>>    File "<string>", line 1, in <module>
>>>>    File "/usr/local/lib/python3/dist-packages/satellites/__init__.py",
>>>> line 44, in <module>
>>>>      from .satellites_python import *
>>>> ImportError: generic_type: type "ax100_decode" referenced unknown base
>>>> type "gr::block"
>>>>
>>>> The are no unusual messages during the compilation of gr-satellites.
>>>>
>>>> If instead of using the PPA package I build GNU Radio 3.9.3.0 from
>>>> source, then everything works.
>>>>
>>>> I haven't tried to do this with other OOT modules. Has anyone
>>>> encountered this problem?
>>>>
>>>> I have some Dockerfiles that can be used to replicate this problem.
>>>> See here:
>>>>
>>>> https://github.com/daniestevez/gr-satellites/issues/303#issuecomment-944604966
>>>>
>>>>
>>>>
>>>> Best,
>>>> Dani.
>>>>
>>>
>>
>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]