[OE-core] [PATCH 07/30] gstreamer1.0-python: add a patch to fix python 3.8 builds

Alexander Kanavin alex.kanavin at gmail.com
Sun Dec 15 18:10:33 UTC 2019


On Sun, 15 Dec 2019 at 18:52, Carlos Rafael Giani <crg7475 at mailbox.org>
wrote:

> Is this related to an issue I mentioned in my RFC?
>
> > gstreamer1.0-python_1.16.1.bb currently has a problem in that the
> gst-python code tries to load /usr/lib/libpython3.7m.so. But, in a
> regular installation, only /usr/lib/libpython3.7m.so.1.0 would be availale.
> It is possible to adjust the libpython path & name during the build. But -
> what would it be adjusted to? How would the recipe know that
> "/usr/lib/libpython3.7m.so.1.0" is the correct choice? Or perhaps would it
> make sense to add the /usr/lib/libpython3.7m.so symlink to the regular
> (as in: non-dev) Python package?
>

The way I read the code [1], it only tries to do this if it's not
explicitly linked with libpython, and at least on my host, it is:

ak at linux-f9zs:~/development/poky> ldd /usr/lib64/gstreamer-1.0/
libgstpython.cpython-37m-x86_64-linux-gnu.so
        linux-vdso.so.1 (0x00007fffe931a000)
        libpython3.7m.so.1.0 => /usr/lib64/libpython3.7m.so.1.0
(0x00007fbb718e7000)
        libgstreamer-1.0.so.0 => /usr/lib64/libgstreamer-1.0.so.0
(0x00007fbb717a3000)
        libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0
(0x00007fbb71747000)
...

The use case is rather marginal I'd say: writing gstreamer plugins in
python. The *other* thing gst-python does, accessing gstreamer API from
python scripts, is not affected.

[1]
https://gitlab.freedesktop.org/gstreamer/gst-python/blob/1.16.2/plugin/gstpythonplugin.c#L227

Alex



> On 15.12.19 18:32, Khem Raj wrote:
>
>
>
> On Sun, Dec 15, 2019 at 9:12 AM Alexander Kanavin <alex.kanavin at gmail.com>
> wrote:
>
>> On Sun, 15 Dec 2019 at 18:06, Khem Raj <raj.khem at gmail.com> wrote:
>>
>>> This is expected; the patch should be merged together with 3.8 upgrade.
>>>
>>> I don’t think this patch is right though since this patch is creating
>>> py3.8 dependency if you want to upstream something that should work with
>>> all py3 I think
>>>
>>
>> It's being discussed in the upstream submission ticket, and will be
>> resolved; we can take the 3.8-specific fix meanwhile.
>>
>
> For better processing this series should be in three parts
>
> 1 Python 3.8 updates
> 2 gettext updates
> 3 rest of them
>
> I have filtered it into roughly these and currently staged in yoe/mut just
> the third part which i think can be applied with out much problem
>
> For 1 and 2 there are breakages for many packages
> And it would be better to identify them and let community know of and seek
> help
>
>
>> Alex
>>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20191215/2b4aea46/attachment-0001.html>


More information about the Openembedded-core mailing list