[Bug 759133] glimagesink: dlopen's wrong libGLESv2 and libEGL on Raspberry Pi

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=759133

--- Comment #8 from Yann Dirson <ydirson at free.fr> ---
(In reply to Nicolas Dufresne (stormer) from comment #7)
> The name with the ABI version are the correct one, while the name without
> (RPI) are incorrect. RPi GL stack is not a properly installed and symlink on
> the raspian distribution.

It's not only an installation issue, it's at least a build issue.  There is no
symlink because the SONAME of the lib does not include an ABI number.  Now is
it
just a "vendor just did not bother" issue, or is it deeper, still has to be
seen.

> (In reply to Yann Dirson from comment #6)
> > libEGL is also subject to this problem, and there the case is worse, as
> > libegl1-mesa is required by xserver-xorg-core.  Now Raspbian should probably
> > provide an Xorg linked against /opt/vc/ (if that works at all),
> > but at the very least they should compile it --with-egl-module-name as you
> > noted.
> 
> Even with Mesa, the installation offers the standard name libEGL.so.1 (with
> ABI). What we can commonly find, is to rename all GL/EGL/GLES library with a
> vendor specific names, and use symlinks to allow changing the stack.
> 
> What I would suggest, is whether to add an easy hardcoded Raspbian
> configuration, or try and convince Raspbian maintainer to fix it.

It's not a Raspbian specific problem.  For the same reason, yocto has no
symlinks
either.  The issue is really an upstream one.  IIRC Broadcom released this set
of
libs as opensource, but I don't know their maintainance status, should check.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.