[yocto] Adding test case in LTP in Yocto

Hi, Anyone suggest me how to add an test case in LTP (Linux Test Procedure) in Yocto distribution. Please suggest. Thanks Umamahesh ::DISCLAIMER::

[yocto] Procedure for adding driver in Yocto

Hi I am looking for a procedure how to add an new driver in Yocto Kernel. I tried adding an sample char driver by updating Kconfig and makefile of respective directory and by default marked as built in by default. But I do not see the driver is coming up while kernel is booted. Please suggest

[yocto] Setting kernel CONFIG variables in the RPi

Apparently, the meta-raspberrypi layer does not employ the Yocto method of modifying the kernel configuration through config fragments. Instead, it uses a kernel_configure_variable function called from within a do_configure_prepend function in recipes-kernel/linux/linux-rpi.inc. The question is

[yocto] [meta-selinux][PATCH v2] policycoreutils: add PACKAGECONFIG for libpam, audit

From: Wenzong Fan * make pam and audit support configurable; * remove INITDIR from EXTRA_OEMAKE, the variable is not supported now. Signed-off-by: Wenzong Fan --- recipes-security/selinux/policycoreutils.inc | 21 ++--- 1

Re: [yocto] Openscap build fails while do_package_qa

On Wed, Oct 4, 2017 at 3:47 AM, Siva Balasubramanian wrote: > I tried building openscap from meta-security. It fails while do_package_qa. > > ERROR: openscap-1.2.14-r0 do_package_qa: QA Issue: >

Re: [yocto] How to use same user in two recipes?

> Hi > > I want to use the same user in two different recipe. > I create the user in recipe A.bb and it works fine. > Now I want to use the same user in B.bb so I add DEPENDS = "A" > thinking that sysroot will be > populated with A.bb users. > > But when I bitbake the recipe, user is not

Re: [yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

On Fri, Oct 6, 2017 at 1:40 PM, Jerry Lian wrote: > Hi, all: > > I have a basic question: how to tell the difference between > "core-image-minimal" and "core-image-base"? > * If we look at file \poky\meta\recipes-core\images\core-image-base.bb >

Re: [yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

On 9 October 2017 at 16:08, Jerry Lian wrote: > Hi, all: > > I have a basic question: how to tell the difference between > "core-image-minimal" and "core-image-base"? > * If we look at file* \poky\meta\recipes-core\images\core-image-base.bb > * >

[yocto] How to use same user in two recipes?

Hi I want to use the same user in two different recipe.  I create the user in recipe A.bb and it works fine. Now I want to use the same user in B.bb so I add DEPENDS = "A" thinking that sysroot will be populated with A.bb users. But when I bitbake the recipe, user is not found.  I conclude that

Re: [yocto] Replacing Openssl with a custom version?

Hi Ryan, On Wednesday, 11 October 2017 7:37:02 AM NZDT Ryan Pabis (pabisr) wrote: > I’m trying to build, link and install our Cisco version of ssl. And I’ve > been able to compile and link it, however I don’t understand how to install > our cisco version INSTEAD of openssl. The easiest way

Re: [yocto] errors in recipe after move from devtool

Hi Greg, On Wednesday, 11 October 2017 7:50:45 AM NZDT Greg Wilson-Lindberg wrote: > I'm still getting the: > > ERROR: zint-2.6.1-r0 do_package_qa: QA Issue: zint: /work/cortexa7hf-neon- > vfpv4-poky-linux-gnueabi/zint/2.6.1-r0/packages-split/zint/usr/lib/ > libzint.so.2.6.1 contains

[yocto] populate_sdk_ext => "Cannot install package nativesdk-git-perltools"

I'm trying to create an extended SDK for a multilib environment and I run into this error during the buildtools-tarball-1.0-r0 do_populate_sdk task: ...snip lots of configuring lines... Configuring nativesdk-buildtools-perl-dummy. Collected errors: * check_conflicts_for: The following packages

[yocto] How to use same user in two recipes?

Hello I want to use the same user in two different recipe.  I create the user in recipe A.bb and it works fine. Now I want to use the same user in B.bb so I add DEPENDS = "A" thinking that sysroot will be populated with A.bb users. But when I bitbake the recipe, user is not found.  I conclude

[yocto] Replacing Openssl with a custom version?

All, I’m trying to build, link and install our Cisco version of ssl. And I’ve been able to compile and link it, however I don’t understand how to install our cisco version INSTEAD of openssl. Any help is greatly appreciated. Regards, Ryan -- ___

[yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

Hi, all: I have a basic question: how to tell the difference between "core-image-minimal" and "core-image-base"? * If we look at file* \poky\meta\recipes-core\images\core-image-base.bb *

Re: [yocto] pkg-config search directories

Hi, Yes its the same problem, just wanted to be more specific. I have added mesa to DEPENDS but still same result. I have also tried running bitbake mesa and it is successful so pkgconfig with mesa works. Yes, I am using glmark2 recipe from meta-oe. perhaps you can recommend a better recipe then

Re: [yocto] pkg-config search directories

Hi Ross, I am still trying to configure pkg-config. Running bitbake glmark2 recipe results with an error : Checking for 'gl': not found. looking into the log file : Checking for 'gl' ['/home/wzbwjj/vpm/GR_Yocto/build/tmp/sysroots/x86_64-linux/usr/bin/pkg-config', 'gl',

[yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

Hi, all: I have a basic question: how to tell the difference between "core-image-minimal" and "core-image-base"? * If we look at file* \poky\meta\recipes-core\images\core-image-base.bb * ===

[yocto] Kernel driver installs broken in poky2.3

Re: poky2.3 kernel driver install's Poky release, pyro (2.3), file: meta/classes/module.bbclass This change, made in January 2017, is breaking do_install's for our kernel drivers, as INSTALL_MOD_PATH is not defined. Our Makefiles reference this variable. What was the purpose of this

[yocto] Openscap build fails while do_package_qa

I tried building openscap from meta-security. It fails while do_package_qa. ERROR: openscap-1.2.14-r0 do_package_qa: QA Issue: /usr/lib/openscap/ptest/tests/API/XCCDF/unittests/test_remediate_python_subs.sh contained in package openscap-ptest requires /bin/bash, but no providers found in

[yocto] u-boot recipe: Missing dependencies

Hello, it seems that even in the most current yocto u-boot recipes from openembedded some general and also x86 specific dependencies are missing. The patch below adds them. From 0502033c5e555abaadcb5e01faae041293e9 Mon Sep 17 00:00:00 2001 From: Eric Schwarz Date: Tue,

Re: [yocto] errors in recipe after move from devtool

Hi Ross, I changed the FILES_${PN}-dev to pick up the .so file and that error went away. Thanks for the cluebat, the learning curve is a bit steep and I'm still climbing. I'm still getting the: ERROR: zint-2.6.1-r0 do_package_qa: QA Issue: zint:

Re: [yocto] errors in recipe after move from devtool

On 10 October 2017 at 17:34, Greg Wilson-Lindberg wrote: > So to continue, what is the problem with symlinked libraries in a non-dev > package, don't most libraries have syslink's to them? > Typically: libfoo.so -> libfoo.so.1 libfoo.so.1 -> libfoo.so.1.2 libfoo.so.1.2 is

Re: [yocto] errors in recipe after move from devtool

Sorry, hit the wrong button in my mailer and sent this before I was finished. So to continue, what is the problem with symlinked libraries in a non-dev package, don't most libraries have syslink's to them? Secondly, the redundant RPATH, most of the links that I've found mentioning this show

[yocto] errors in recipe after move from devtool

I'm trying to develop a new recipe for zint, barcode generating software. I initially built the recipe under devtool and got it to the point that there were no errors. I then did a devtool finish command to move it to my yocto build tree under our private recipe and now when I build it I get 2

Re: [yocto] [meta-selinux][PATCH] policycoreutils: update AUDITH, PAMH

This is incorrect. You are not allowed to dynamically determine capabilities like this. Because if another component changes, the system has no way to determine if this package should also be recompiled. policycoreutils should be using 'PACKAGECONFIG', with an audit and pam option. Then set a

[yocto] [meta-selinux][PATCH] policycoreutils: update AUDITH, PAMH

From: Wenzong Fan Update definition of AUDITH, PAMH according to the upstream changes for Makefiles: commit 89ce96cac6ce5eeed78cb39c58514cd68494d7aa ... -ifeq ($(PAMH), /usr/include/security/pam_appl.h) +ifeq ($(PAMH), y) ... -ifeq ($(AUDITH),