Re: [yocto] Installation help

; >>>       Please ensure your host's network is configured correctly, > >>>       or set BB_NO_NETWORK = "1" to disable network access if > >>>       all required sources are on local disk. > >>> > >>> -- &

Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

We never digged deep enough to find the cause, but when we separated the SSTATE to only have one DISTRO in the same SSTATE, the problem disappeared. -- Best Regards Ulf Samuelsson -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctopr

Re: [yocto] kernel module override

t; > Russell > > Rename your out of tree module to something else. Patch the module that you want to replace so it does not do anything. Enable it and build it. You can also remove the dependency by patching the Kconfig files. Ulf Samuelsson > > -- >

Re: [yocto] Managing multiple builds

bpn = d.getVar('BPN') newbpn = bpn.replace('-development', '') d.setVar('BPN', newbpn) # Use default FILESPATH searching for patches and files filespath = d.getVar('FILESPATH') newfilespat

Re: [yocto] Make one directory writeable

again mount the overlayfs, you get your modifications back. Best Regards, Ulf Samuelsson +46 722 427 437 > 13 feb. 2019 kl. 08:21 skrev Bhupendra Singh > : > > Hello > I have built core-image-minimal with read only rootfs then now I want to > make one directory (like /m

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

7;t You need to RDEPEND on A? -- Best Regards Ulf Samuelsson -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

Maybe it would be good to have a working example in the tree. Best Regards, Ulf Samuelsson > 6 feb. 2019 kl. 02:22 skrev Khem Raj : > > > >> On Sat, Feb 2, 2019 at 7:17 PM Ken Sloat >> wrote: >> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield >> wrote: &g

Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

> 3 feb. 2019 kl. 20:09 skrev Ken Sloat : > >> On Sun, Feb 3, 2019 at 12:51 AM Ulf Samuelsson wrote: >> >>> Den 2019-02-03 kl. 04:16, skrev Ken Sloat: >>> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield >>> wrote: >>>> &g

Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

be added automatically, but this might be required, - or a workaround... FILES_${PN} = " \ /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \ ${sysconfdir}/modules-load.d/${MODULE_NAME}.conf \ " -- Best Regards Ulf Samuelsson -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] adding task before a task T but after all other tasks that T depends on?

I build. How do I add a task z, which runs after any of x,y,z, but before T? The list of possible tasks might be extended in the future, so I really would want to specify: ”addtask w after T[depends] before T” or similar. Best Regards, Ulf Samuelsson

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

> 18 jan. 2019 kl. 16:56 skrev Alexander Kanavin : > > > >>> On 18 Jan 2019, at 16.34, Burton, Ross wrote: >>> >>> On Fri, 18 Jan 2019 at 15:08, Ulf Samuelsson wrote: >>> We could insert a check if the KNOWN_TASKS is valid in a verification

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

> 18 jan. 2019 kl. 15:40 skrev Richard Purdie > : > > On Fri, 2019-01-18 at 15:16 +0100, Ulf Samuelsson wrote: >>> 18 jan. 2019 kl. 12:29 skrev Richard Purdie < >>> richard.pur...@linuxfoundation.org>: >>> >>>> On Fri, 2019-01-18 at 05:

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

> 18 jan. 2019 kl. 12:29 skrev Richard Purdie > : > >> On Fri, 2019-01-18 at 05:30 +0100, Ulf Samuelsson wrote: >> So if KNOWN_TASKS is defined in a configuration file in oe-core, it >> would be OK? >> It needs to be extended to check for KNOWN_TASKS == Non

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

So if KNOWN_TASKS is defined in a configuration file in oe-core, it would be OK? It needs to be extended to check for KNOWN_TASKS == None of course. Best Regards, Ulf Samuelsson +46 722 427 437 > 18 jan. 2019 kl. 00:17 skrev Burton, Ross : > > On Thu, 17 Jan 2019 at 22:50, Ulf Samuelss

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

> 17 jan. 2019 kl. 22:05 skrev Richard Purdie > : > >> On Thu, 2019-01-17 at 19:15 +0100, Ulf Samuelsson wrote: >> From 864e49bedbdab480c5ada9588ce8f980f23919dd Mon Sep 17 00:00:00 >> 2001 >> From: Ulf Samuelsson >> Date: Thu, 17 Jan 2019 19:07:17 +01

[yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

From 864e49bedbdab480c5ada9588ce8f980f23919dd Mon Sep 17 00:00:00 2001 From: Ulf Samuelsson Date: Thu, 17 Jan 2019 19:07:17 +0100 Subject: [PATCH] bb.build.addtask: add simple check for circular dependency Signed-off-by: Ulf Samuelsson --- bitbake/lib/bb/build.py | 48

Re: [yocto] bitbake: DataSmart.expandWithRefs causing exception when handed "${@...}"

Den 2019-01-15 kl. 14:38, skrev Richard Purdie: On Sun, 2019-01-13 at 22:53 +0100, Ulf Samuelsson wrote: I am trying to add a new image class "SWU" in "sumo" for a "software update image". As a result: do_sdk_depends[depends] = '${@

[yocto] bitbake: DataSmart.expandWithRefs causing exception when handed "${@...}"

Refs needs to be extended to handle the case where the variable is a "call". This is blocking us from upgrading from pyro to sumo. Any ideas on a solution? BR Ulf Samuelsson -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Keeping and modifying Source code in Yocto

simpler than that of the externalsrc bbclass. No need for SRC_URI statements. We check out meta layers and the components using repo so the components are always located in $COMPONENTS_DIR. Been thinking of upstreaming this, but I am unsure about the interest. Best Regards, Ulf Samuelsson >

Re: [yocto] How handle files needing updates in read-only filesystem

etc. Once the symlink/bind mount is accessed, it should not eat up the CPU cycles, Kno Best Regards, Ulf Samuelsson > 14 juni 2018 kl. 01:02 skrev Andre McCurdy : > >> On Wed, Jun 13, 2018 at 9:28 AM, Ulf Samuelsson wrote: >> Thanks, is it more efficient than symlinking? >

Re: [yocto] How handle files needing updates in read-only filesystem

Thanks, is it more efficient than symlinking? Best Regards, Ulf Samuelsson > 13 juni 2018 kl. 15:20 skrev Anders Darander : > > * Ulf Samuelsson [180612 22:01]: > >> We want most of /etc to be read-only for security reasons, >> and the overlayfs will make the whole of

Re: [yocto] Image specific configuration files

recipe generating three variants in the same build. Don’t have the source in front of me so I can’t share the bbclass (right now at least) Best Regards, Ulf Samuelsson +46 722 427 437 > 1 juni 2018 kl. 12:40 skrev Alan Martinovic : > > Yes, much better phrasing: > > >

Re: [yocto] Adding kernel module to yocto core-image-base

There is an example in meta-skeleton/recipes-kernel Best Regards, Ulf Samuelsson > 12 juni 2018 kl. 09:33 skrev Iván Castell : > > Hello. > > First you need to reconfigure your kernel configuration (ncurses must be > properly installed in your host PC): > >

Re: [yocto] Issue when integrating different bsp-layers on a single bblayers.conf

ich is true only if a machine in the meta-rockchip layer is used. Best Regards, Ulf Samuelsson > 7 juni 2018 kl. 16:39 skrev Iván Castell : > > Hello forum. > > I am trying to integrate several BSP-layers for different platforms on a > single Yocto repository to build a Linux

Re: [yocto] Image specific configuration files

You can create three separate recipes that generate three different nginx configurations and include one if them in each image recipe. Best Regards, Ulf Samuelsson > 1 juni 2018 kl. 07:46 skrev Damien LEFEVRE : > > Hi, > > For the same MACHINE I create the following imag

Re: [yocto] Issue when integrating different bsp-layers on a single bblayers.conf

You can BBMASK away that bbappend when you are not building the rockchip machine. Best Regards, Ulf Samuelsson > 7 juni 2018 kl. 16:39 skrev Iván Castell : > > Hello forum. > > I am trying to integrate several BSP-layers for different platforms on a > single Yocto repositor

Re: [yocto] How handle files needing updates in read-only filesystem

. Symlinking to /persistent is fine, so the question is what an acceptable method is to have a simple way of ensuring that a certain file is converted to that symlink. Best Regards, Ulf Samuelsson +46 722 427 437 10 juni 2018 kl. 01:36 skrev Peter Kjellerstedt : >> -Original M

Re: [yocto] Fwd: image-mklibs.bbclass fails

Regards, Ulf > 29 maj 2018 kl. 21:43 skrev Khem Raj : > >> On Mon, May 28, 2018 at 2:10 AM, Ulf Samuelsson wrote: >> Checked out poky >> git checkout -b rocko origin/rocko >> export MACHINE=beaglebone >> . ./oe-init-build-env >> >> Added to local.

Re: [yocto] Generating license/manifest for a specific layer?

considering upstreaming. Best Regards, Ulf Samuelsson > 11 juni 2018 kl. 15:46 skrev Michael Habibi : > > Our use case is to capture the license files, manifest (package/version), and > download information only for packages we modify/add. We use our own layer to > modi

[yocto] How handle files needing updates in read-only filesystem

s would break any build which has a "funny" volatiles file. Otherwise a script called populate_persistent.sh could be created with such an extension. Comments? BR Ulf Samuelsson -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Image specific configuration files

do_install_append_class-release () { install -m 755 ${WORKDIR}/rcS.release ${D}${sysconfdir}/init.d/rcS } BBCLASSEXTEND = "production rnd release" == In your production image you add IMAGE_INSTALL_append = "busybox-production" Do something similar for

[yocto] Fwd: image-mklibs.bbclass fails

l/1.0-r0/mklibs/dest `cat /home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/mklibs/executables.list`' ... Looks like image-mklibs.bbclass has not been tested since the move to a local sysroot happened. BR U

[yocto] How to add a module to python-native

Need some advice on how to extend python-native with a python-2.7 module. I am planning to upload the result of cve-check to our JIRA server. I wrote a python application which reads the CVE manifest, downloads the contents of a JIRA project and if a CVE issue is not present in the database, it w

[yocto] [PATCH] hostname.sh: remove warning for bashism

The use of the environment variable HOSTNAME, triggers the checkbashisms script, so change HOSTNAME to LOCALHOST Signed-off-by: Ulf Samuelsson --- meta/recipes-core/initscripts/initscripts-1.0/hostname.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes

[yocto] [PATCH] hostname.sh: remove warning for bashism

The use of the environment variable HOSTNAME, triggers the checkbashisms script, so change HOSTNAME to LOCALHOST Signed-off-by: Ulf Samuelsson --- meta/recipes-core/initscripts/initscripts-1.0/hostname.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-core

Re: [yocto] busybox->coreutils: How replace single Busybox program with same from coreutils

On 2017-11-11 07:59, Ulf Samuelsson wrote: Adding a third party package to the rootfs, and some of their scripts will break due to the busybox version of certain applications do not support all the switches. Rather that rewriting those scripts (forcing me to maintain them) I would like to

[yocto] busybox->coreutils: How replace single Busybox program with same from coreutils

Any other ideas? Is overriding busybox with the "real" application documented somewhere? If not, maybe it should be. Overriding coreutils with busybox is easily found when googling. Best Regards Ulf Samuelsson -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] poky using native pkg_resources module

and email me the bug number so I can take care of it. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12148 BR Ulf Alejandro | aehs29 On 09/30/2017 01:31 PM, Ulf Samuelsson wrote: Den 2017-09-29 kl. 20:18, skrev Alejandro Hernandez: Hey Ulf, On 09/29/2017 04:05 AM, Ulf Samuelsson

Re: [yocto] poky using native pkg_resources module

Den 2017-09-29 kl. 20:18, skrev Alejandro Hernandez: Hey Ulf, On 09/29/2017 04:05 AM, Ulf Samuelsson wrote: It looks like the pkg_resource module is using the native installation I cloned poky early september, and could complete a build. When I clone poky today, the build fails. As

[yocto] RFC: autotooler: generation of "configure.ac" and "Makefile.am" using Kconfig

generate fairly easy. === A final step would clone a empty git tree, and populate it with all the files needed for a complete package. === Comments appreciated. Best Re

[yocto] poky using native pkg_resources module

. Summary: 1 task failed: /home/ulf/Kunder/eMagii/Disk/yocto-arm/poky-arm/build/../meta-emagii/recipes-images/images/emagii-image.bb:do_image_wic Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. Best Regards Ulf Samuelsson -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto