[yocto] Triggering rebuild on a recipe when MACHINE changes

I have a few recipes that should rebuild when value of MACHINE variable changes. How can this be accomplished? I tried using do_compile[vardeps] += "MACHINE", but this didn't seem to have any affect. -- Pagarbiai, Linux programuotojas Kristupas Savickas +370 633 36795 --

[yocto] Error: pulsar-image-14.0.0-r0 do_rootfs: Could not invoke dnf. Command

Iam trying build an image for R-CAR H3 using GENIVI 14 (ROCKO). *My Native System:* OS: Ubuntu 16.04 RAM: 64 GB *The build configuration is:* BB_VERSION = "1.36.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux"

[yocto] [YP Core] Thud moved out of active releases

Hello all, is it intended that the thud release 2.6 documents overview went into archived documents? I can't find any news about it and thud is still promoted as latest release on the frontpage. (https://www.yoctoproject.org/) Or is this standard procedure and 2.6.1 will follow shortly?

Re: [yocto] [PATCH V2] patchwork: Add a dockerfile for deploy patchwork and patchtest

On 1/16/19 12:37 AM, changqing...@windriver.com wrote: From: Changqing Li Ping? Jose, are you maintaining this repo? http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/about/ You were the committer for most of the recent work. ../Randy Add a dockerfile for easy deploy patchwork and

Re: [yocto] Yocto Porject

On Mon, 2019-01-28 at 10:33 -0800, Scott Rifenbark wrote: > Hi Don,  > > I can't really advise you on this as I am not a Yocto developer.  > However, I can forward this question to the yocto@yoctoproject.org > mail group and, in particular, to a resource that is looking closely > at kernel stuff

[yocto] Expansion Error during parsing of glibc_2.28 recipe

Hello, I'm trying to upgrade the glibc recipe from version 2.27 to 2.28 in Yocto Sumo 2.5. Building the recipe for both qemux86 and for arm-cortex-a8 machines throws an Expansion error as below. WARNING: /source/meta-openembedded/meta-oe/recipes-extended/liblockfile/ liblockfile_1.14.bb: Unable

[yocto] [meta-raspberrypi] change kernel version from recipe

Hi, which is the right way to change the Kernel version to build when using meta-raspberrypi ? For example I want to change from 4.14.39 to 4.14.52, without changing anything else in the meta-raspberrypi layer. is it possible ? Is it just to define "LINUX_VERSION" in the local.conf file ? Should

Re: [yocto] [EXTERNAL] SRC URI checksums

Thank you. I must have based the recipe on one that downloaded a tarball, and didn't notice until now the checksums never had to be changed. On Mon, Jan 28, 2019 at 11:25 AM Burton, Ross wrote: > > On Mon, 28 Jan 2019 at 19:23, Lukasz Zemla wrote: > > Checksums were introduced to ensure data

Re: [yocto] [EXTERNAL] SRC URI checksums

On Mon, 28 Jan 2019 at 19:23, Lukasz Zemla wrote: > Checksums were introduced to ensure data consistency. They are not checked if > SRC_URI points to repository (svn, git, hg..., it is assumed that repository > provides its own mechanism to ensure data correctness). To clarify, the checksums

Re: [yocto] [EXTERNAL] SRC URI checksums

> I have a recipe that has a SRC_URI retrieving from a mercurial repo: > SRC_URI = "hg://server/project;module=name;rev=tip" > SRC_URI[md5sum] = "xxx" > SRC_URI[sha256sum] = "yyy" > > I changed the SRC_URL to retreive from a specific revision instead of tip: > SRC_URI =

Re: [yocto] Yocto Porject

Hi Don, I can't really advise you on this as I am not a Yocto developer. However, I can forward this question to the yocto@yoctoproject.org mail group and, in particular, to a resource that is looking closely at kernel stuff to help improve that manual and get it more up-to-date. That guy is

[yocto] SRC URI checksums

I have a recipe that has a SRC_URI retrieving from a mercurial repo: SRC_URI = "hg://server/project;module=name;rev=tip" SRC_URI[md5sum] = "xxx" SRC_URI[sha256sum] = "yyy" I changed the SRC_URL to retreive from a specific revision instead of tip: SRC_URI =

[yocto] Yocto Project Unassigned Bugs - Help Needed

All, The triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the

[yocto] Help with cleaning/rebuidling

The first time I did a build, my mosquitto recipe worked. Then I did a 'bitbake -ccleanall mosquitto', and now when I do 'bitbake mosquitto', I get this error: DEBUG: Executing python function sysroot_cleansstate DEBUG: Python function sysroot_cleansstate finished DEBUG: SITE files

[yocto] setting arch of a single package of a recipe

Is it possible, when splitting a recipe into multiple packages, to change the arch of only one package? (example: setting foopackage-doc arch to "all") I can't seem to find a way to set PACKAGE_ARCH for a single package. I've tried PACKAGE_ARCH_${PN}-doc which didn't work. Grepping for

[yocto] Fixing devtool issue with kernel bbhappen do_patch recipe

Hi all, We found a possible bug with boucman_work as mentionned in the IRC. It seems that when using the SDK there's an issue with the generated file workspace/appends/linux-yocto_4.18.bbappend (or equivalent depending on kernel and distro). In the do_patch rule, if some script are intended to

Re: [yocto] [PATCH] u-boot: update commit id to the latest one of u-boot upstream

On Mon, 28 Jan 2019 at 11:20, wrote: > There are 2 CVE issues fixing in latest u-boot upstream, so > update commit id to involve these fixing patches. We generally don't update commit id's to something random, as that means picking a source tree in the middle of a development cycle. If you want

Re: [yocto] [poky] Bitbake Issue in Yocto 2.7 M2 rc1:

On Mon, 28 Jan 2019 at 07:04, pawanKumar wrote: > While running bitbake command, I'm facing issue as: > Error: OE-cores config sanity checker detected a potential misconfiguaration. > Either fix the cause of this error or at your own risk disable the checker > (see sanity.conf) Above that it

[yocto] [PATCH] u-boot: update commit id to the latest one of u-boot upstream

From: MengLi There are 2 CVE issues fixing in latest u-boot upstream, so update commit id to involve these fixing patches. Signed-off-by: Meng Li --- meta/recipes-bsp/u-boot/u-boot-common.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[yocto] : [meta]: [recipes-bsp]: u-boot: update commit id to the latest one of u-boot upstream

From: Limeng Hi Richard, Could you please help to merge this patch into meta/recipes-bsp/u-boot, branch is master? There are 2 CVE issues fixing in latest u-boot upstream, so update commit id to involve these fixing patches. thanks, Limeng --