All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Rogerio Nunes <ronunes@gmail.com>,
	 Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Rogerio Nunes <rogerio.nunes@freescale.com>
Subject: Re: [meta-fsl-arm][PATCH] piglit: Add Vivante GPU support
Date: Mon, 27 Jan 2014 07:25:30 -0700	[thread overview]
Message-ID: <52E66C5A.5030706@boundarydevices.com> (raw)
In-Reply-To: <CACb8hfGfrWGJoMntLj6OyKuTXKDFV0te06urUqFZg+tqCrf70g@mail.gmail.com>

Thanks Rogerio,

On 01/27/2014 07:10 AM, Rogerio Nunes wrote:
> Hi guys,
>
> On Mon, Jan 27, 2014 at 8:50 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> Hi Eric,
>>
>> On Mon, Jan 27, 2014 at 11:40 AM, Eric Nelson
>> <eric.nelson@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?
>>
>> If it does, we have a missing dependency in pitlit or something like that.
>>
>
> Same here. The tools-testapps IMAGE_FEATURE includes piglit in the
> fsl-image-gui already.
>
> I haven't tested with IMAGE_INSTALL, but I have the same understanding
> as Otavio, that if the build is breaking, then there's probably a
> dependency missing in the base recipe.
>

So perhaps the answer is simple... Don't do that (use IMAGE_INSTALL
for piglit).

I just mentioned that I have been able to succesfully build
fsl-image-gui, and I didn't see that it was already including
piglit.

I'll test later today.

Regards,


Eric


  reply	other threads:[~2014-01-27 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24  1:20 [meta-fsl-arm][PATCH] piglit: Add Vivante GPU support ronunes
2014-01-24  1:33 ` Otavio Salvador
2014-01-24 10:37   ` Burton, Ross
2014-01-26 15:57 ` Eric Nelson
2014-01-26 19:15   ` Otavio Salvador
2014-01-26 19:44     ` Rogerio Nunes
2014-01-27 13:40       ` Eric Nelson
2014-01-27 13:50         ` Otavio Salvador
2014-01-27 14:10           ` Rogerio Nunes
2014-01-27 14:25             ` Eric Nelson [this message]
2014-01-27 19:49               ` Eric Nelson
2014-01-28  3:56                 ` Rogerio Nunes
2014-01-27 14:23           ` Eric Nelson
2014-01-27 14:25             ` Otavio Salvador

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52E66C5A.5030706@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=rogerio.nunes@freescale.com \
    --cc=ronunes@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.