[yocto] bootchart2 OLDPATH not set in /sbin/bootchartd.bootchart2,

I been trying to use bootchart2 and have it daisy chain into the orginal /sbin/init But looks like the /sbin/bootchartd.bootchart2 attempts to restore the PATH from OLDPATH export PATH=$OLDPATH exec $init $* But OLDPATH was never set. The /sbin/init I have then has serious issues , It

Re: [yocto] read-only-rootfs causes systemd-tmpfiles-setup.service failure ( symlink(../run/lock, /var/lock) failed: Read-only file system)

This is what I have, $ cat etc/fstab # stock fstab - you probably want to override this with a machine specific one /dev/root/auto ro 1 0 proc /procproc defaults 0 0 devpts

[yocto] read-only-rootfs causes systemd-tmpfiles-setup.service failure ( symlink(../run/lock, /var/lock) failed: Read-only file system)

I am build an image with read-only-rootfs When enabled, during startup I get a [FAILED] Failed to start Create Volatile Files and Directories. See 'systemctl status systemd-tmpfiles-setup.service' for details. ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded:

Re: [yocto] morty populate_sdk_ext fails for recipes inherit bin_package

Thanks Ross, my TOOLCHAIN_TARGET_TASK_append = " hals hals-doc" does have the ‘space’, so that is not the issue. ( when I forgot it, got errors which had the ‘hal’ on the previous package, i.e gtesthal “, so it was apparent about the missing space. no real idea how to ‘debug’ the

Re: [yocto] morty populate_sdk_ext fails for recipes inherit bin_package

Hi Paul Thanks, I am new in this area, so could be miss-understanding some of these: What I would like to occur, when local.conf has: IMAGE_INSTALL_append = "hals" TOOLCHAIN_TARGET_TASK_append = "hals hals-doc" 1) image has the "hals" runtime 2)when I use -c populate_sdk and/or -c

Re: [yocto] morty populate_sdk_ext fails for recipes inherit bin_package

Appreciate your suggestions. The ipk's are there $ find tmp/deploy/ipk/ -name hals* tmp/deploy/ipk/cortexa9hf-neon/hals-tests_5.0.0-r0_cortexa9hf-neon.ipk tmp/deploy/ipk/cortexa9hf-neon/hals_5.0.0-r0_cortexa9hf-neon.ipk tmp/deploy/ipk/cortexa9hf-neon/hals-dev_5.0.0-r0_cortexa9hf-neon.ipk

Re: [yocto] morty populate_sdk_ext fails for recipes inherit bin_package

Hi 1) I had just successfully built an image with all the recipes ( hals, hals-doc) [and yes, there these are non-empty] 2) I had then successfully built image with -c populate_sdk 3) The bitbake image -c populate_sdk_ext is what is failing [ The above works with Krogoth, only on Morty am I

[yocto] morty, how to debug opkg issues with do_populate_sdk? (ipk based) Error 255 (recipes use bin_package)

I have some simple recipes which inherit bin_package Local has PACKAGE_CLASSES ?= "package_ipk" There are no issues with the krogoth release , can do -c populate_sdk and all is well with morty, same recipe, same command but the -c populate_sdk give me; ERROR: core-image-minimal-1.0-r0

Re: [yocto] busybox and images, how to change busybox based on image component added

Thanks for the pointer. I am new to the linux/Yocto area , so if there is example, would greatly help. When you say it 'replaces', is this a the 'name' level? connman is not the same name as udhdc My user desires to only have connman on the system (and it's daemon) and not have udhcp (and

[yocto] busybox and images, how to change busybox based on image component added

I am trying to remove the udhcp( client / server) components in busybox when I include 'connman' in my image. I have a busybox_%.bbappend which will SRC_URI_append = " file://no-uhdpc.cfg" no-uhdcpc.cfg CONFIG_UDHCPD=n CONFIG_UDHCPC=n Hitting serval issues: -) need to do a bitbake -c cleanall