Greetings ! I am working on NXP's i.MX6UL SoC . I have built yocto successfully for the same . I want to use to my own custom linux kernel source which is cloned in my local PC in some specific direct

#zeus

<poornesh.g@...> wrote: always look into layerindex for available packages. A search for realmd reveals that there is no recipe for it. So you have to write one https://layers.openembedded.or

#zeus

Greetings ! Can any one help me out to include "realm" (used as command line tool that can be used for management of enrollment in Kerberos realms, like Active Directory domains) in Yocto (Zeus). Than

#zeus

Hi Poornesh This is not supported in Zeus, but otherwise you may be interested in the "overlay-etc" class: https://docs.yoctoproject.org/ref-manual/classes.html?highlight=overlayfs#overlayfs-etc-bbcla

#zeus #yocto

Hi, This seems like a good use for overlayfs-etc IMAGE_FEATURES? c.f. https://docs.yoctoproject.org/ref-manual/features.html#image-features See https://docs.yoctoproject.org/ref-manual/classes.html#ov

#zeus #yocto

Greetings ! I am working on NXP's i.MX6UL SoC and I have successfully built a Read-only Rootfile system through Yocto. Now I am having a requirement of making only "/etc" as Read & Writable . So , Can

#zeus #yocto

Dule, Dule, Dudule! Slusaj i prati sta ti YOCTO velicine pricaju! I pokusaj sam da se snadjes, jer te dobro navode! ;-) Zee _______

#yocto #zeus

Here is the error: | .../kernel-source/include/linux/log2.h:22:1: warning: ignoring attribute 'noreturn' because it conflicts with attribute 'const' [-Wattributes] | 22 | int ____ilog2_NaN(void); | |

#yocto #zeus

AFAICS 4.1.15 doesn't match any kernel recipes in the zeus branches of either meta-freescale or meta-imx, it might go easier if you based off of the 5.4.x kernel recipes one of those use... Scott

#yocto #zeus

perhaps there is more specific compiler error in logs above that ?

#yocto #zeus

Hello, I am trying to upgrade my distro from rocko to zeus. After I fixed all the initial parsing and build problems I have reached a point where the linux-imx doesn't build. Maybe I am underestimatin

#yocto #zeus

Hi, I am quite new to Yocto/BitBake and I have a bit of a headache trying to figure out the best way to make use of a native tool in the following context: I have one recipe that fetch and build third

#yocto #zeus

Thanks for the reply, I tried adding IMAGE_LINGUAS = " ", it passes but do_image_cpio gives nothing (means no image.gpio.gz) is generated. I don't know why.

#yocto #zeus

to get more info, can you try adding IMAGE_LINGUAS = " " and see if this changes anything ?

#yocto #zeus

Hello All, I created a simple image recipe for initramfs type of image with no IMAGE_FEATURES and simply: IMAGE_INSTALL = "packagegroup-core-boot busybox" When I bitbake the image I get the following

#yocto #zeus

I am able to build clean... One question, "clang" is a dependency for the build of the NEO driver, once built, do I still require clang as part of my image ?, or can I remove the clang component in th

#zeus

Thank you. I will most likely look into creating a dunfell based build this weekend... My current system is zeus based, centos, still using sysvinit on startup... Did run using clang 9.0 ? I appreciat

#zeus

There are no patches needed other than what is already in oe-core/meta- intel/meta-clang. I tried building zeus on Ubuntu 16.04 and didn't see any problem. zeus is no longer maintained or supported so

#zeus

Anything ?, I have yet to resolve this.

#zeus

Are there any patches required for these components (igc, opencl-clang, and intel-compute-runtime) ?

#zeus