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?
On 15.12.19 18:32, Khem Raj wrote:
On Sun, Dec 15, 2019 at 9:12 AM Alexander Kanavin
<alex.kana...@gmail.com <mailto:alex.kana...@gmail.com>> wrote:
On Sun, 15 Dec 2019 at 18:06, Khem Raj <raj.k...@gmail.com
<mailto:raj.k...@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@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
