All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Stiffler <j-stiffler@ti.com>
To: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: k2 build failures
Date: Tue, 3 May 2016 08:25:27 -0400	[thread overview]
Message-ID: <572898B7.4050309@ti.com> (raw)
In-Reply-To: <4B26FB5A64EBA14C87266869E037F9581426AF5A@DFLE09.ent.ti.com>

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]



On 5/2/2016 2:59 PM, Stiffler, Jacob wrote:
>
> With migrating to krogoth, the k2 build failures are due to conflicts 
> between the ocl-gl-headers and mesa, and I’ve discovered why mesa is 
> being pulled in.
>
> In the opencv recipe, we are inheriting “cmake_qt5”. This bbclass was 
> changed to add the dependency on qtbase, and this brings in mesa for 
> keystone.
>
> I’m not sure of the best way to handle this. The easiest hack is the 
> remove qtbase from the opencv dependencies for keystone only.
>
> Would it be possible to replace opencl’s dependency on 
> “ocl-gl-headers” with “mesa-gl”? In the past, I made some attempts to 
> use “mesa”, but with the SGX platforms, there was always a conflict 
> with the ti sgx drivers, as both were installing common gles files. I 
> do not remember mesa-gl being an option before.
>

I treid replacing opencl's dependency on ocl-gl-headers with 
virtual/libgl. This appears to work for keystone, but for am57xx-evm, 
there is a conflict between mesa-gl and libgbm recipes as mesa-gl also 
provides a libgbm package. How can this conflict be resolved?

> Thank you,
>
> Jake
>
>
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


[-- Attachment #2: Type: text/html, Size: 4027 bytes --]

  reply	other threads:[~2016-05-03 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 18:59 k2 build failures Stiffler, Jacob
2016-05-03 12:25 ` Jacob Stiffler [this message]
2016-05-03 15:50   ` Denys Dmytriyenko

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=572898B7.4050309@ti.com \
    --to=j-stiffler@ti.com \
    --cc=meta-arago@arago-project.org \
    /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.