On Fri, 24 May 2024 at 17:33, Michael Lynch via lists.openembedded.org
<mlynch=hi-techniques....@lists.openembedded.org> wrote:
>
> For informational purposes the two recipes in question here are 
> intel-compute-runtime and intel-graphics-compiler.  Both are items needed to 
> use OpenCL with INTEL GPUs.
>
> Alex, it sounds like the "wrong" thing to do is to "rollback" the meta-clang 
> layer back to the "mickledore" branch as was suggested?  Here's the weird 
> thing, the layer compatibility for meta-clang in the "mickledore" branch 
> actually lists "scarthgap" in addition to "mickeldore" and one other.  Where 
> as layer compatibility of meta-clang in the "scarthgap" branch is set to 
> "scarthgap" only.  Did someone maybe do the wrong thing with layer 
> compatibility in meta-clang on the mickledore branch?  Just curious because 
> it seemed that mixing layer branches to make things build seemed a bit off of 
> the whole philosophy of how yocto/bitbake was intended to work but I thought 
> maybe that was just me not understanding everything completely.

Let's continue in the proper list.

This is the commit that added scarthgap compatibility to mickledore:
https://github.com/kraj/meta-clang/commit/8fbc4b443893ab3842063e65d8fe27a5d166bd3e

So this was intentional and not a mistake, but it's still problematic:
what if something else in your setup would require meta-clang to be at
scarthgap branch? You might get cryptic errors when that happens and
no easy way to resolve the conflict.

Sadly llvm 16 support in the intel items is a deeper issue than I
thought, and certainly not a trivial fix. Upstream will get to it, at
some point:
https://github.com/intel/intel-graphics-compiler/issues/289


Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63197): https://lists.yoctoproject.org/g/yocto/message/63197
Mute This Topic: https://lists.yoctoproject.org/mt/106285424/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to