[meta-freescale] [meta-fsl-arm][PATCH] piglit: Add Vivante GPU support

Otavio Salvador otavio at ossystems.com.br
Mon Jan 27 06:25:53 PST 2014

Hello Eric and Rogerio,

On Mon, Jan 27, 2014 at 12:23 PM, Eric Nelson
<eric.nelson at boundarydevices.com> wrote:
> On 01/27/2014 06:50 AM, Otavio Salvador wrote:
>> On Mon, Jan 27, 2014 at 11:40 AM, Eric Nelson
>> <eric.nelson at boundarydevices.com> wrote:
>>> I'm not sure I understand how these could be related,
>>> but I ran a clean build overnight without success.
>>> Note that this was a straight-forward fsl-image-gui image
>>> with piglit appended to IMAGE_INSTALL in local.conf.
>> Interesting. I've been building fsl-image-gui with success. Could you
>> try this and see if it helps?
> Right. I can do that as well.
>> If it does, we have a missing dependency in pitlit or something like that.
> Yes. Sorry if that wasn't clear.
> The issue is that piglit seems to require /usr/bin/env during its'
> rootfs operation, and I saw similar issues when building other recipes
> that are based on Python.
> The offending logfile is attached and the error message is this:
> Computing transaction...error: Can't install
> python-core-2.7.3-r0.3 at cortexa9hf_vfp_neon: no package provides /usr/bin/env
> Hmmm. Looking at a successful image (fsl-image-gui without piglit)
> shows that /usr/bin/env is present through busybox:
>         ./usr/bin/env -> /bin/busybox.nosuid
> I thought I looked at this previously and only saw a symlink in
> /bin/env.
> So perhaps the issue is either a dependency issue for Python
> or an issue with how busybox expresses what it provides.
> I'll try to look further later.

I can take a look at this; I suspect it is a regression of last
changes from update-alternatives which has been moved to opkg-utils
and there are some  known issues. I will try to reproduce it once I
get my autobuilder free.

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

More information about the meta-freescale mailing list