gpu-viv-mx6q and libEGL.so/libEGL.so.1

gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Eric Nelson]

Hi all,

When running the sample apps in /opt/viv_samples/vdk
under strace on a frame-buffer only build, I can see that
something is trying to load libEGL.so (no trailing 1).

Looking at the recipe, I'm not quite grokking how this is
placed into the image though.

I can see a symlink being created pointing libEGL.so at
libEGL.so.1 here:

	https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130

Somehow or another, the symlink is ending up in the -dev package
though:

$ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
	-name libEGL\*
gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1

Can anybody give some guidance on where and how that's happening?

Does anybody know where the missing reference to libEGL.so
might be coming from? This doesn't appear to be a hard-coded
linker dependency from any of the sample apps or from the
other shared libraries.

Please advise,


Eric

Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Philip Craig]

On Fri, Jul 26, 2013 at 10:44 AM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> Hi all,
>
> When running the sample apps in /opt/viv_samples/vdk
> under strace on a frame-buffer only build, I can see that
> something is trying to load libEGL.so (no trailing 1).
>
> Looking at the recipe, I'm not quite grokking how this is
> placed into the image though.
>
> I can see a symlink being created pointing libEGL.so at
> libEGL.so.1 here:
>
>
> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130
>
> Somehow or another, the symlink is ending up in the -dev package
> though:
>
> $ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
>         -name libEGL\*
> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1
>
> Can anybody give some guidance on where and how that's happening?

See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
libEGL.so then this probably needs to be changed to how libgles and
libgles2 are done. It would be nice to document exactly where the
dependency is though so that we know when we can remove the hack once
it is fixed.

> Does anybody know where the missing reference to libEGL.so
> might be coming from? This doesn't appear to be a hard-coded
> linker dependency from any of the sample apps or from the
> other shared libraries.

I can't see the dependency from inspection. What's the exact error message?

Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Philip Craig]

On Fri, Jul 26, 2013 at 7:54 PM, Philip Craig <phil@blackmoth.com.au> wrote:
> On Fri, Jul 26, 2013 at 10:44 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi all,
>>
>> When running the sample apps in /opt/viv_samples/vdk
>> under strace on a frame-buffer only build, I can see that
>> something is trying to load libEGL.so (no trailing 1).
>>
>> Looking at the recipe, I'm not quite grokking how this is
>> placed into the image though.
>>
>> I can see a symlink being created pointing libEGL.so at
>> libEGL.so.1 here:
>>
>>
>> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130
>>
>> Somehow or another, the symlink is ending up in the -dev package
>> though:
>>
>> $ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
>>         -name libEGL\*
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1
>>
>> Can anybody give some guidance on where and how that's happening?
>
> See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
> libEGL.so then this probably needs to be changed to how libgles and
> libgles2 are done. It would be nice to document exactly where the
> dependency is though so that we know when we can remove the hack once
> it is fixed.
>
>> Does anybody know where the missing reference to libEGL.so
>> might be coming from? This doesn't appear to be a hard-coded
>> linker dependency from any of the sample apps or from the
>> other shared libraries.
>
> I can't see the dependency from inspection. What's the exact error message?

I see now. The samples uses libGAL.so, and it contains the string
libEGL.so, as well as a gcoOS_LoadEGLLibrary function.

Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Otavio Salvador]

On Fri, Jul 26, 2013 at 7:05 AM, Philip Craig <phil@blackmoth.com.au> wrote:
> On Fri, Jul 26, 2013 at 7:54 PM, Philip Craig <phil@blackmoth.com.au> wrote:
>> On Fri, Jul 26, 2013 at 10:44 AM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>> Hi all,
>>>
>>> When running the sample apps in /opt/viv_samples/vdk
>>> under strace on a frame-buffer only build, I can see that
>>> something is trying to load libEGL.so (no trailing 1).
>>>
>>> Looking at the recipe, I'm not quite grokking how this is
>>> placed into the image though.
>>>
>>> I can see a symlink being created pointing libEGL.so at
>>> libEGL.so.1 here:
>>>
>>>
>>> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130
>>>
>>> Somehow or another, the symlink is ending up in the -dev package
>>> though:
>>>
>>> $ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
>>>         -name libEGL\*
>>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
>>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1
>>>
>>> Can anybody give some guidance on where and how that's happening?
>>
>> See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
>> libEGL.so then this probably needs to be changed to how libgles and
>> libgles2 are done. It would be nice to document exactly where the
>> dependency is though so that we know when we can remove the hack once
>> it is fixed.
>>
>>> Does anybody know where the missing reference to libEGL.so
>>> might be coming from? This doesn't appear to be a hard-coded
>>> linker dependency from any of the sample apps or from the
>>> other shared libraries.
>>
>> I can't see the dependency from inspection. What's the exact error message?
>
> I see now. The samples uses libGAL.so, and it contains the string
> libEGL.so, as well as a gcoOS_LoadEGLLibrary function.

Philip, are you going to cook a patch for this?

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Eric Nelson]

Hi Philip,

On 07/26/2013 03:05 AM, Philip Craig wrote:
> On Fri, Jul 26, 2013 at 7:54 PM, Philip Craig <phil@blackmoth.com.au> wrote:
>> On Fri, Jul 26, 2013 at 10:44 AM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>> Hi all,
>>>
>>> When running the sample apps in /opt/viv_samples/vdk
>>> under strace on a frame-buffer only build, I can see that
>>> something is trying to load libEGL.so (no trailing 1).
>>>
>>> Looking at the recipe, I'm not quite grokking how this is
>>> placed into the image though.
>>>
>>> I can see a symlink being created pointing libEGL.so at
>>> libEGL.so.1 here:
>>>
>>>
>>> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130
>>>
>>> Somehow or another, the symlink is ending up in the -dev package
>>> though:
>>>
>>> $ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
>>>          -name libEGL\*
>>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
>>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1
>>>
>>> Can anybody give some guidance on where and how that's happening?
>>
>> See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
>> libEGL.so then this probably needs to be changed to how libgles and
>> libgles2 are done. It would be nice to document exactly where the
>> dependency is though so that we know when we can remove the hack once
>> it is fixed.
>>
>>> Does anybody know where the missing reference to libEGL.so
>>> might be coming from? This doesn't appear to be a hard-coded
>>> linker dependency from any of the sample apps or from the
>>> other shared libraries.
>>
>> I can't see the dependency from inspection. What's the exact error message?
>
> I see now. The samples uses libGAL.so, and it contains the string
> libEGL.so, as well as a gcoOS_LoadEGLLibrary function.
>

Thanks for finding this.

Since these are binaries, we'll need to defer to Freescale/Vivante
for a proper fix.

Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Eric Nelson]

Hi Philip,

On 07/26/2013 02:54 AM, Philip Craig wrote:
> On Fri, Jul 26, 2013 at 10:44 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi all,
>>
>> When running the sample apps in /opt/viv_samples/vdk
>> under strace on a frame-buffer only build, I can see that
>> something is trying to load libEGL.so (no trailing 1).
>>
>> Looking at the recipe, I'm not quite grokking how this is
>> placed into the image though.
>>
>> I can see a symlink being created pointing libEGL.so at
>> libEGL.so.1 here:
>>
>>
>> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130
>>
>> Somehow or another, the symlink is ending up in the -dev package
>> though:
>>
>> $ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
>>          -name libEGL\*
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1
>>
>> Can anybody give some guidance on where and how that's happening?
>
> See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
> libEGL.so then this probably needs to be changed to how libgles and
> libgles2 are done. It would be nice to document exactly where the
> dependency is though so that we know when we can remove the hack once
> it is fixed.
>
>> Does anybody know where the missing reference to libEGL.so
>> might be coming from? This doesn't appear to be a hard-coded
>> linker dependency from any of the sample apps or from the
>> other shared libraries.
>
> I can't see the dependency from inspection. What's the exact error message?
>

No error message was generated. The apps just silently exited.

strace showed attempts to load libEGL.so without the .1 trailer.

Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Eric Nelson]

Hi Philip,

On 07/26/2013 02:54 AM, Philip Craig wrote:
> On Fri, Jul 26, 2013 at 10:44 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi all,
>>
>> When running the sample apps in /opt/viv_samples/vdk
>> under strace on a frame-buffer only build, I can see that
>> something is trying to load libEGL.so (no trailing 1).
>>
>> Looking at the recipe, I'm not quite grokking how this is
>> placed into the image though.
>>
>> I can see a symlink being created pointing libEGL.so at
>> libEGL.so.1 here:
>>
>>
>> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130
>>
>> Somehow or another, the symlink is ending up in the -dev package
>> though:
>>
>> $ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
>>          -name libEGL\*
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1
>>
>> Can anybody give some guidance on where and how that's happening?
>
> See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
> libEGL.so then this probably needs to be changed to how libgles and
> libgles2 are done. It would be nice to document exactly where the
> dependency is though so that we know when we can remove the hack once
> it is fixed.
>

Seeing and understanding are completely different things ;)

I'm reading this to mean that this clause translates to
libEGL.so:
	libEGL${SOLIBSDEV}

I'm also unclear on whether simply moving that clause to
FILES_libegl-mx6 is the right thing to do.

Regards,


Eric

Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Otavio Salvador]

On Fri, Jul 26, 2013 at 11:15 AM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 07/26/2013 02:54 AM, Philip Craig wrote:
>> See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
>> libEGL.so then this probably needs to be changed to how libgles and
>> libgles2 are done. It would be nice to document exactly where the
>> dependency is though so that we know when we can remove the hack once
>> it is fixed.
>>
>
> Seeing and understanding are completely different things ;)
>
> I'm reading this to mean that this clause translates to
> libEGL.so:
>         libEGL${SOLIBSDEV}
>
> I'm also unclear on whether simply moving that clause to
> FILES_libegl-mx6 is the right thing to do.

The point is the binaries are wrong; the .so files shouldn't be used
at runtime but just at linking time.

So we can /workaround/ it and include another FIXME comment for it.

To add this to  the package, we'll also need to add an INSANE_SKIP for it.

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750