**** BEGIN LOGGING AT Fri Mar 23 03:00:04 2018 Mar 23 08:30:29 For the linux-yocto recipe, if I change some variable that kernel_do_deploy() depends on, would that trigger a recompilation(do_compile) of the kernel ? I thought bitbake could detect that, and only rerun the kernel_do_deploy() function Mar 23 12:44:51 Hello, I build my own distro on local machine with Arch. Not supported, but works without problems. Today I deleted the whole sstate and workdir and let the sstate to be loaded from mirror, which is built on a CentOS server. Everything went well, but then various tasks started to fail because {mv,ls,mkdir,..} could not find the libselinux.so.1 library. The library is not on my local machine, but it is on the server. Mar 23 12:45:41 So I checked where the binaries are taken from and they are taken from the recipe's recipe-sysroot-native directory. It seems as if this directory contains binaries from the server (got there through sstate), but not all required libraries. Mar 23 12:46:21 How shall I handle this? Mar 23 12:52:19 adam_trhon: sounds like you are building coreutils-native... that really shouldn't be needed, so find out what's depending upon that and disable the dependency Mar 23 12:52:42 adam_trhon: bitbake -g should produce some dependency graphs that you can grep to figure where that's coming in Mar 23 12:53:33 * bluelightning goes to get sleep Mar 23 13:14:31 I have dependency on coreutils-native directly in the recipe because I need to run cksum as a part of the build. I removed the dependency, deleted the workdir (because just after removing the dependency the problem persisted) and now the compilation finally runs. Mar 23 13:15:05 But after it finishes the build will fail again because now I won't have the cksum binary. What is the right way to add it, so that I avoid this problem? Mar 23 13:18:19 I use cksum in task that I append to PACKAGEBUILDPKGD Mar 23 13:18:34 use md5sum/shasum? Mar 23 13:19:01 add cksum to HOSTTOOLS, the problem is that we limit the commands on the host you can see in a build Mar 23 13:19:24 so congrats you found one which should probably be added, even if it is a binary that i've never even heard of in 20 years Mar 23 13:20:06 if its just a checksum you're after, sha*sum is already in the list and not trivially breakable Mar 23 14:22:04 rburton: Adding to HOSTTOOLS helped. I am not surprised that it is so outdated, it comes from the dark ages of our company :) But it's not a security feature, so I will keep it. Thank you! Mar 23 16:57:49 this build picks up the wrong version of a component when building an image Mar 23 16:58:04 but bitbake -e or bitbake -fc compile whatever picks up the right version Mar 23 16:58:21 how can I fix this Mar 23 17:33:44 or how to debug it Mar 23 21:24:11 heeen: What do you mean 'picks up the wrong version'? Are you specifying the version of the package? Mar 23 21:48:12 heeen: I believe you can either manually specify the version you want, or tell bitbake to use the latest version. SRCREV = "${AUTOREV}" will use the latest. PREFERRED_VERSION_packagename = "1.6.15" will use a particular version. Mar 23 21:49:10 heeen: I believe the SRCREV fragment would go in the recipe for the package. I think the PREFERRED_VERSION fragment goes in the image recipe. Mar 23 21:49:59 PREFERRED_* are global, not per recipe. config files only Mar 23 21:54:28 As in local.conf? Mar 23 21:58:04 whereever is most appropriate. local.conf, distro, whatever Mar 23 22:07:18 Thanks! **** ENDING LOGGING AT Sat Mar 24 03:00:01 2018