Following up on the email below, I've created a "community" subgroup to the OpenEmbedded group on GitLab: https://gitlab.com/openembedded/community. This should help to avoid any confusion with the

Hi, you should inherit in your image recipe the following bbclass: inherit selinux-image It will set the security label of your filesystem using your refpolicy offline so it does not need to relabel

On 11/22/19 9:03 AM, rpjday@... wrote: Would you mind opening a Yocto defect. - armin

<rpjday@...> wrote: it once generated SPDX manifest from patched sources for package and file level it has sadly regressed, so would need some love as you see above.

a lilttle more progress, and then an error -- i installed fossology on my ubuntu 18.04 dev box, then added INHERIT += "spdx" to local.conf, and tried to build a simple qemuarmx86-64, and

I don't know if any of the (too many) versions of u-boot have that feature. If you are willing to test from userspace, there is memtester: https://layers.openembedded.org/layerindex/recipe/863/ I

It looks like your question is covered here: https://forums.xilinx.com/t5/Embedded-Linux/Bitbake-recipe-help/td-p/773151 ../Randy -- # Randy MacLeod # Wind River Linux

Hi Pavan, Hopefully explained well enough here: https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-issue-libdir Regards, Quentin -- StreamUnlimited Engineering GmbH High Tech

i asked about this a couple months ago but didn't see any replies, so i'll ask again with a little more detail. colleague wants to, from YP (actually petalinux but should be irrelevant), some sort

Hello, probably coreutils package isnot explicitly installed in the SDK. You can add packages to the SDK using two variables: packages that contain tools for the host: TOOLCHAIN_HOST_TASK -

Hi All, After building the recipe, I'm getting warning message: "Warning: do_package_qa QA Issue: <recipe-dbg>: found library in wrong location. Any suggestion to resolve this issue? Regards, Pavan

Hi, I tried building extended SDK using the command $bitbake <custom-core-image> -c populate_sdk_ext, but got errors which are as follows: ERROR: Task xilinx-r5-bsp.do_fetch attempted to

Hi, We are working on Yocto 2.6.3. We are generating the sdk using“bitbake core-image-sato-sdk -c populate_sdk”. After installation of sdk, we observed, usr/bin/*.coreutils are not

Thats my take as well. By sysv being the default andsystemd being massively used we almost automatically end up with good testing of both. Greetz --

Fix busybox directory aliases issue. Set correct labels for /sbin/init.sysvinit and /bin/start_getty. Signed-off-by: Yi Zhao <yi.zhao@...> --- ...bs_dist-fix-busybox-directory-aliase.patch

This reverts commit 184857a52ecc9b7088021d7362c7d85e1c3551d6. The mesa hasn't switched to meson build in this branch. Signed-off-by: Yi Zhao <yi.zhao@...> ---

Hi Yair, On 11/14/19 2:06 AM, Yair Itzhaki wrote: SElinux+busybox should work. But there are some security label issues with busybox. I attached a fix. You can

The migration is complete. Please update your address books to point to the new list e-mail addresses. There are rewrites in place so the previous mailing list addresses will continue to work for a

It is also quite amazing that the project, by design, has entirely sidestepped the divisive init system wars that have been gripping the mainstream linux distros for years (and still are). I'd say it

We got so far and after looking at the position we ended up I decided it was easier to switch poky-altcfg rather than change poky and/or OE defaults. I resolved that bug as "complete" as we now had