**** BEGIN LOGGING AT Wed Nov 15 03:00:01 2017 Nov 15 05:24:56 Should adding bluez5 to DISTRO_FEATURES_append enable the bluez5 package? Nov 15 06:18:18 yes Nov 15 08:18:24 Hi all Nov 15 08:21:58 New news from stackoverflow: How to generate libcurl.so.5 with curl 7.56.1 in Yocto? Nov 15 09:29:42 Which task is responsible for evaluating the SRC_URI to see if the source have changed? do_fetch or do_unpack? Nov 15 10:09:54 I am investigating how the DEPENDS and RDEPENDS variables work in conjunction with the package manager (opkg/ipk) and would like to now if it would soehow be possible to specify a depency package version range using those variables? Nov 15 10:12:15 Explicitly I would like the build system to fail if the package version is not found (which would otherwise make the configure step fail) Nov 15 10:13:29 and theoretically specify a (library) version range which I know to be ABI compatible allowing the ipk to be installed on systems where the exact version version I had at compile-time is not present but an ABI compatible version is Nov 15 10:16:39 deva: RDEPENDS can have a version range, see https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#var-RDEPENDS Nov 15 10:19:10 I am back with my license problem :D : I try to populate a custom license (for vim recipe imported to my layer from official meta-oe layer) but I have this warning "The license listed vim was not in the licenses collected for recipe vim" Nov 15 10:19:20 I added "LICENSE_PATH += "${LAYERDIR}/files/custom-licenses"" to meta-mylayer/conf/layer.conf Nov 15 10:19:27 I added the vim license file to meta-mylayer/files/custom-licenses Nov 15 10:19:41 and in meta-mylayer/repices-oe/vim/vim_8.0.0427.bb there is this line : LICENSE = "vim" Nov 15 10:19:54 Do you have any leads for me, please ? Nov 15 10:30:05 nrossi, Great :-) I just assumed they were similar and found nothing referring to versions in the DEPENDS description Nov 15 10:37:33 I want to define "DL_DIR" outside the "build dir", one way is to define the path in "conf/local.conf" in the build directory. I need more generic location where I can define "DL_DIR" once for all. Nov 15 10:47:34 MWelchUK: hey-o. Did you see my reply last night? Nov 15 10:47:55 joshuagl: Not yet, will scroll back :-) Nov 15 10:48:17 "MWelchUK: \o I added that so that we could implement things like: http://git.yoctoproject.org/clean/cgit.cgi/meta-swupd/tree/classes/swupd-image.bbclass#n572" Nov 15 10:49:18 the commit message and that example usage may be the sum total of docs, though :-/ Nov 15 10:49:48 ping Nov 15 10:50:31 xtron: "conf/local.conf" is the right place. And the only IMO Nov 15 10:50:35 one Nov 15 10:51:26 zzeroo: that way we have to re-define it in every new build directory Nov 15 10:52:09 joshuagl: I've given implementing a test a go, initially I based it from the always failing python example in the commit message. It was consistently running and failing, but now struggling to work out how to get it to re-run after a successful build - I thought cleanall on the image would work, but it doesn't seem to. Nov 15 10:52:12 zzeroo: that is may be not most efficient way Nov 15 10:52:32 yes, but why not just use one build dir. You can reuse is >< Nov 15 10:54:06 joshuagl: https://pastebin.com/YYCNmpvC Nov 15 10:54:13 zzeroo: hmm Nov 15 10:54:18 (Which I think should always fail...) Nov 15 10:55:18 xtron: Why do you use so much build dirs. That this is a problem I mean, whats your use case? Nov 15 10:57:23 xtron: You could add a `sed` command to the `oe-init-build-env` script you source to create the build dir. It's just a bash script Nov 15 10:58:11 zzeroo: I just want a consolidated download directory Nov 15 10:58:46 zzeroo: i case I want to make a seperate build dir, I can do efficiently Nov 15 11:03:15 xtron: To be honest I do not care much about my download directory. Poky is doing very well for me. Nov 15 11:03:44 with one build dir for all my projects :) Nov 15 11:05:22 zzeroo: yeah, it is good in most cases, Nov 15 11:10:53 xtron: you can share the download directory between all your builds. i must have 20 build dirs here all sharing the same sstate and dldir Nov 15 11:11:09 MWelchUK: sorry, packing for travel and don't really have time to dig in. The task runs after do_rootfs so you need to have the checksum change on that task before it'll re-run. You can always bitbake my-awsome-image:do_image_qa -f Nov 15 11:11:13 rburton: meson patchset on the list, so do send me build failures :) Nov 15 11:11:20 oh i will ;) Nov 15 11:11:32 are they in a branch against master? Nov 15 11:11:40 I also resent a couple of earlier patches with minor fixes Nov 15 11:11:42 rburton: yes Nov 15 11:11:55 will fire that on the ab now then Nov 15 11:11:58 Thanks joshuagl. Safe travelling. Nov 15 11:12:13 rburton: where we can define "DL_DIR" other than "conf/local.conf" so it is available to all build dirs... Nov 15 11:20:24 xtron: either set it to the same path in every local.conf, or create a site.conf which sets it and either copy that into every build dir, or put it in a layer and add that layer to every build dir. Nov 15 11:20:54 or if your custom distro can assume the environment then you can assign in the local.conf.sample to the right path Nov 15 11:21:06 or just don't create new build directories all the time and reuse Nov 15 11:38:30 hello, is this the right sort of place to ask about what is covered by yocto/openembedded training? Nov 15 11:38:46 kanavin: https://autobuilder.yocto.io/tgrid Nov 15 11:39:30 danf1: who is giving the training? might be better to approach them directly Nov 15 11:40:59 rburton: i see. well, that is true, i guess i was hoping there might be someone here who as done some and could offer some insight from an outcomes point of view Nov 15 11:41:24 well depends on who is giving this yocto training you speak of Nov 15 11:44:26 i'm interested in getting the range of experiences rather than particular trainers. talking to trainers gets their perspective which is not always the most honest. Nov 15 11:44:49 so if anyone has had any good yocto training i'm interested in hearing from them, whichever provider Nov 15 11:45:01 ah so you're looking for recommendations for a trainer, instead of feedback on a specific trainer Nov 15 11:45:12 kanavin: no-x11 just failed in the meson branch Nov 15 11:46:05 rburton: yes, i'm not too fussed who gives the training, except that it would be good for them to have been recommended Nov 15 12:19:54 when package is deployed (for example it has content in /etc and /lib) , does it means that all its files are independent from other image file, or are there common files with other package ? Nov 15 12:37:27 when package is deployed (for example it has content in /etc and /lib) , does it means that all its files are independent from other image file, or are there common files with other package ? Nov 15 12:38:18 I mean, copying the files to rootfs should be good, and won't override existing files. Right ? Nov 15 12:38:48 ranran: this is decided by the package manager in use Nov 15 12:38:50 ranran: if two packages try to install the same files to the image, you get a cofllict error and the image cration aborts. Nov 15 12:39:25 LetoThe2nd: if the files have exactly same content, then rpm has no problem with that and will make the file owned by both packages :) Nov 15 12:40:02 kanavin: thank $DEITY that my life works out wonderfully without rpm :) Nov 15 12:41:01 hi, when I have some recipe which will build native version and would like to have this binary included in SDk Nov 15 12:41:25 it's enough to BBCLASS_EXTEND = "nativesdk"? Nov 15 12:41:30 I tried but it doesn't work Nov 15 12:43:46 open-nandra: no _ in the variable Nov 15 12:43:59 also just doing that doesnt put it in the SDK Nov 15 12:44:36 rburton: yes sorry it was typo + ok what else I need to recipe to have it present in sdk? Nov 15 12:45:28 http://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-adding-individual-packages Nov 15 12:46:47 hi all Nov 15 12:46:53 rburton: oh stupid me, thanks for link Nov 15 12:47:13 is there a need for some special magic in order to add glibc-utils to an image? Nov 15 12:47:30 i used IMAGE_INSTALL_append="glibc-utils" Nov 15 12:47:33 LetoThe2nd, I understand. so in "normal" way it is not supposed to happen. Thanks Nov 15 12:47:50 and i searched for "locale" in the manifest file Nov 15 12:47:58 and it is not present Nov 15 12:51:57 hi, Nov 15 12:52:03 im very new to yocto Nov 15 12:52:13 started learning it 3 days ago Nov 15 12:52:30 I have a dragonboard 410c Nov 15 12:52:41 and compiled it's yocto Nov 15 12:52:54 now i do the https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles Nov 15 12:53:29 question, how can I see that the bbexample package really got into my image ? Nov 15 12:54:34 @dafna: in the tmp/deploy/images/boardname there is a .manifest file Nov 15 12:54:43 search for your binary there Nov 15 12:55:11 like grep bbexample *.manifest Nov 15 12:55:25 you should have it there Nov 15 12:58:03 ok, it's not there actually Nov 15 12:58:44 I added oe-rpb/layers/meta-example/recipes-core/images/rpb-minimal-image.bbappend Nov 15 12:58:58 Hello! Nov 15 12:59:00 with "IMAGE_INSTALL += " bbexample"" Nov 15 12:59:21 rburton: I've added it to variable written in manual but I get following: rdepends upon non-existent task do_package_write_ipk in virtual:native:myrecipe.bb Nov 15 12:59:32 as it's native it's not doing ipk Nov 15 13:00:23 how to get rid o: Poky (Yocto Project Reference Distro) ... dev/tty1 on boot? Nov 15 13:01:06 open-nandra: does your recipe explicitly inherit native? Nov 15 13:01:07 what do you mean? Nov 15 13:01:18 rburton: yes Nov 15 13:01:30 @dafna: well ... an other idea is to extract the resulted rootfs image and see if the program is there. You will see the directory structure as on the board itself, but if not present in .manifest file then almost sure it is not available on the rootfs also Nov 15 13:02:10 @dafna: other then that, i don't know Nov 15 13:03:05 open-nandra: then that will be forcing the recipe to be a native recipe. remove that, rename file to foo_version.bb, add native to bbclassextend, and fix up the recipe so that it can work in target/native/nativesdk modes Nov 15 13:05:32 Klopilot: thats DISTRO_NAME, change that or just edit /etc/issue (in basefiles)if you want it to say something totally different Nov 15 13:06:13 rburton: ok but if I want to recipe build only on host machine and not target, tehn I need to define inherit native Nov 15 13:07:42 rburton: ok, but i would like to get rid of all of this text on the framebuffer, it seems its waiting for a login on tty1, how to stop this? Nov 15 13:09:26 rburton: otherwise it's failing as it's not compilabe for target Nov 15 13:18:54 editing /etc/issue works, but after that there is a string: MACHINE_ARCH login: ! Any ideas to stop this? Nov 15 13:44:25 @Costin1 Nov 15 13:44:44 @Costin1 hi , was able to add bbexample-rt to the rootfs Nov 15 13:45:40 it also works when loaded to the board, is there a way to run something like dry-run, so it creates only the manifast Nov 15 13:45:44 so to save time ? Nov 15 13:46:50 RP, hi is this good to merge to pyro? http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144283.html Nov 15 13:46:51 thanks Nov 15 13:50:37 Hi all Nov 15 13:51:02 Is there a yocto command to force a recipe to compile from the beginning without losing local changes Nov 15 13:51:38 I have a recipe that uses a git repo, I made local changes to the source of that local repo clone, and I'd like to compile again Nov 15 13:52:26 MajorGrub: use bitbake -f Nov 15 13:52:40 xtron: no need to for -c compile ? Nov 15 13:52:45 no need for* Nov 15 13:53:11 MajorGrub: bitbake help is your friend Nov 15 13:53:44 xtron: hmm kay Nov 15 13:55:47 MajorGrub: usually one would do a checkout outside the build/work directory and use externalsrc for the development time Nov 15 13:56:57 MajorGrub: here you go: http://www.yoctoproject.org/docs/2.4/dev-manual/dev-manual.html#building-software-from-an-external-source Nov 15 13:57:33 MajorGrub: then you also don't need any tricks to bitbake, and no fear that the changes might be lost Nov 15 14:01:00 Is there no one to help me with my license warnings, please ? Nov 15 14:06:48 tront_: merging the patches doesn't really help, its easier to have straight backports. You need to talk to the stable branch maintainer really (armin) about testing them next Nov 15 14:07:36 I did it like that because the second commit was a change on the first one Nov 15 14:07:57 didn't see much point to willingly include a commit which was prone to be changed Nov 15 14:08:20 armpit, can you take a look at that patch for the pyro branch, please? Nov 15 14:09:07 RP, if I just add the 2 commits, would it be easier for you to get them in? Nov 15 14:22:33 tront_: it needs to be tested. Currently we're in a mess with testing. See the last weekly status report Nov 15 14:23:17 k Nov 15 14:46:09 hello. If I want to use the java and javac provided by openjdk in meta-java layer, should I change the PREFERRED_PROVIDERS of what meta-java readme suggests? Nov 15 14:47:11 but recipes of openjdk to not PROVIDE any virtual/java or virtual/javac Nov 15 14:59:00 something like PREFERRED_PROVIDER_java2-runtime = "openjdk-8-jre" ? Nov 15 15:01:16 nayfe: ty for the point. I will try to use it. Nov 15 15:02:13 Tamis: i looked the README, in fact providers are in recipe-core, and depends on openjdk, it should work as described Nov 15 15:05:52 nayfe: not it does not work as it is. when I try to use javac, javac command points to the compiler installed by ecj-bootstrap-native and the java command points to the VM installed by cacao-native Nov 15 15:07:09 nayfe: it seems to be as it is stated here: https://lists.yoctoproject.org/pipermail/yocto/2016-March/029260.html Nov 15 15:07:38 tamis: indeed, but those javac from cacao/ecj are taken from openjdk, am i wrong ? Nov 15 15:08:39 nayfe: I think not. Because openjdk is not even compiled in my system with those settings Nov 15 15:09:07 in fact i use meta-oracle-java, maybe other ppl can answer :) Nov 15 15:10:58 nayfe: the build works fine with meta-oracle-java? because I had also a problem with that with xerces-j Nov 15 15:11:23 which arch ? Nov 15 15:11:52 x86_64. I means for native builds Nov 15 15:16:51 maybe post your config files/recipes to pastebin? Nov 15 15:23:18 New news from stackoverflow: yocto change a recipe source from remote source to git Nov 15 15:32:56 * paulg_ eyes the yocti bot with suspicion Nov 15 15:53:21 My image contains python2.7 and python3.5, anyway to know which package adds python2.7 ? Nov 15 15:53:23 New news from stackoverflow: Yocto imx6 runlevel Nov 15 15:53:23 hey, with the Yocto Rocko update, udev is being installed on the rootfs even though the configs have been changed to use mdev. With Pyro the same config installed mdev, but with Rocko udev forcefully gets installed along with mdev. Has anyone else faced this issue? Nov 15 15:58:11 nayfe: boot it and try removing it with the package manager :) what release of yocto are you using? Nov 15 15:58:27 rocko Nov 15 15:59:08 that's indeed a good suggestion :p Nov 15 15:59:21 if you can boot it, thats definitely a fast way ;) Nov 15 15:59:38 i'd use bitbake myimage -g -u taskexp Nov 15 15:59:45 and see what is pulling in python Nov 15 16:02:44 I'm working on embedded firmware so there is no package manager, I'm on the latets stable Yocto Rocko Nov 15 16:02:48 latest* Nov 15 16:04:10 I was using VIRTUAL-RUNTIME_dev_manager = "busybox-mdev" in Pyro and it would remove all udev traces for me, but with Rocko both udev & mdev get installed Nov 15 16:08:45 rburton> woah didnt know about taskexp, thanks! Nov 15 16:09:21 I'm unable to see udev using taskexp, I wonder how does it end up on the rootfs each time Nov 15 16:09:45 ssingh: rburton was talking to me, sorry Nov 15 16:10:11 ssingh: you logged just after my question Nov 15 16:11:03 no worries Nov 15 16:43:43 Hi there, I am running a rocko and master OpenSSH server and tried connecting, the client errors with "ssh_dispatch_run_fatal: Connection to 192.168.10.171 port 22: incorrect signature" Nov 15 16:44:40 Anybody seen that? Tried ArchLinux (OpenSSH OpenSSH_7.6p1) and Fedora client (OpenSSH_7.5p1) Nov 15 16:51:02 no, never seen that. fwiw the autobuilder ssh's into virtual machines running rocko/master/etc many times a day from a variety of host distros Nov 15 17:03:22 rburton: hm, interesting. Are all images using OpenSSH (or dropbear)? Nov 15 17:03:44 i'd imagine mostly openssh Nov 15 17:17:15 Hmm, should create a utility function to getVar/expand a variable/value with some other variables altered to something else just for that expansion. just d.createCopy(), setVar() the changed vars, then expand/getvar with those altered values. i.e. getvar_altered('libdir', baselib='foo') Nov 15 17:41:07 Hi Stefan, had problem with openssh on rocko, i switched to dropbear for now Nov 15 17:46:43 i think it's because openssh depends on openssl10 instead of openssl in 7.5 version Nov 15 17:48:47 oops he left Nov 15 18:11:28 rburton, Can I restart the controller between builds to add fedora27? Nov 15 18:14:32 rburton, We are going to skip updates this Friday since we did them yesterday and we need longer uptimes to hit memory frag bugs. Nov 15 18:16:18 halstead: sure. i'm doing my best to load the builders ;) Nov 15 18:17:26 rburton, Thanks. I'll give you an extra builder running 4.13.12 to worry about. ;) Nov 15 19:09:51 is it possible to have Yocto recipes use the git repo files instead of repo.git? Nov 15 19:10:51 using repo.git required me to make commits to build my changes, it is a lot of overhead while debugging Nov 15 19:20:54 "git repo files"? Nov 15 19:21:06 no idea what you're talking about there Nov 15 19:23:55 I mean to say that I want my recipe to access the git folder and not look for the .git file Nov 15 19:24:23 it first looks for the .git, then extracts it into downloads, then works off of the files there Nov 15 19:24:47 I want it to directly work off of the repo folder Nov 15 19:24:53 ssingh: use a file:// url instead of a git:// url ? Nov 15 19:25:41 can I use file:// for files located outside the Yocto directory? Nov 15 19:36:40 if you want to bypass DL_DIR, i.e. for active development, you should just use devtool modify or externalrsc directly Nov 15 20:09:18 RP, looks like rburton is offline. I've finished the controller changes so we can start more builds. Nov 15 20:15:07 When creating an sdcard image , how yocto knows the memory size to give for the image. I mean, it knows the size of all files in rootfs, but it is not the same size as the image, Right ? Nov 15 20:17:54 ranran: IMAGE_ROOTFS_SIZE helps with IMAGE_OVERHEAD_FACTOR and IMAGE_ROOTFS_EXTRA_SPACE Nov 15 20:19:19 ranran: and if i remember correctly, it adds 100Mb when package-management feature is set Nov 15 20:21:06 nayfe, thanks ! Nov 15 20:23:13 ranran: yw, to resume if you want a fixed size you can set IMAGE_ROOTFS_SIZE="X" and IMAGE_OVERHEAD_FACTOR="1.0 " Nov 15 20:25:08 nayfe, is the "dd" size the same as partition size, I mean if in dd we give 2GBytes, and we then format it with ext4, does it mean that it is same as partition in size of 2GBytes ? Nov 15 20:27:13 i'm not sure to understand the question Nov 15 20:27:19 you can then do something like dd if=image.ext4 of=/dev/mmcblk0p1 bs=1M Nov 15 20:27:48 you can have a partition bigger to image Nov 15 20:27:52 than Nov 15 20:31:50 nayfe, I'll ask it differently, and in respect to yocto's IMAGE_ROOTFS_EXTRA_SPACE : How much space should be given between rootfs size vs image size ? Nov 15 20:33:01 ranran: you mean how many free space you should add ? Nov 15 20:33:09 yes. Nov 15 20:33:55 I check the size of rootfs and it's 1Gbytes , is it that 100MByte good enough ? How should I know the size to add ? Nov 15 20:34:14 ranran: difficult to say, it depends on image type and usage Nov 15 20:35:33 yes , I see. But if the space is for example 100MByte, it means that rootfs can be added with more then 100MBytes, with additional files. Right ? Nov 15 20:36:04 it can be added with files, up to the space we've given it. Right ? Nov 15 20:37:11 ranran: that's it if you put IMAGE_ROOTFS_EXTRA_SPACE="(100mbyte calculation)" you will have 100mb free (plus 100mb if you put package-management feature) Nov 15 20:37:59 Thanks, naife Nov 15 20:38:03 ranran: maybe if you use wic to create your image, you can use it to customize layout Nov 15 20:38:04 nayfe Nov 15 21:40:23 Hey guys....does anyone have a link to a recipe for a non-busybox version of 'dd' and/or 'truncate'? I have had a heck of a time tracking them down. Nov 15 21:41:09 JimH: that would be coreutils surely? Nov 15 21:44:40 bluelightening: I know that 'dd' is included already, but a member of my dev team is looking for the 'full' (i.e., non-busybox) version. I haven't tracked down either that or 'truncate' Nov 15 21:44:53 JimH: It's in coreutils Nov 15 21:45:26 busybox reimplements most of the coreutils commands; if you want the 'original' thing that's what you need to install Nov 15 21:48:03 neverpanic: if the busybox version is the one in coreutils, then I need to track down the recipe for the 'original' ('original recipe' just sounds waaaay too KFC) Nov 15 21:48:35 JimH: busybox and coreutils are different implementations of the same commands. Busybox is the stripped down version, coreutils is the full one. Nov 15 21:48:51 Ah..../facepalm Nov 15 21:48:54 So 'if the busybox version is the one in coreutils' doesn't make a lot of sense Nov 15 21:49:24 Ok, my bad then. I'm still pretty new to yocto, trying to get up to speed Nov 15 21:49:32 No problem, it's not obvious Nov 15 21:51:19 * bluelightning adds a FAQ question Nov 15 21:52:43 neverpanic: I was assuming that 'dd' would have been in the mix somewhere; I was able to find 'vim' and 'lsof' pretty easily, so I was assuming that other utilities should be there as well. I just couldn't find what I was looking for on OpenEmbedded (or anywhere else) Nov 15 22:03:20 https://wiki.yoctoproject.org/wiki/Technical_FAQ#How_do_I_get_.22full.22_versions_of_typical_shell_commands.3F Nov 15 22:04:33 Thanks for the answers. Greatly appreciated. Nov 15 22:05:57 Hey! Is it ok to ask a question here? I've created and set up a location for additional licenses, but for "LIC_FILES_CHKSUM", the file is located at the top of the project under /files. Is there a variable to allow me to point to this directory within a recipe? Nov 15 22:06:47 LAYERDIR isn't available within a recipe... Thank you so much for the help, and if this question shouldn't be asked here, let me know!! Nov 15 22:07:31 The whole point of LIC_FILES_CHKSUM is to use a file form the source tree that mentions the license that applies so that you'll notice when you update a package and the license changes Nov 15 22:07:42 That being said, you can use ${LAYERDIR} in there, AFAIR Nov 15 22:10:28 LAYERDIR isn't valid outside of layer.conf Nov 15 22:10:57 The project in question does not include a license, unfortunately. It's also a unique one that most likely will not be changed. As bluelightning said, I cannot access LAYERDIR from my recipe. Nov 15 22:11:33 Huntereb: no license statement at all? not even in a source header or README? Nov 15 22:12:34 The project in question is a font distributed in the form of a ZIP file, the license is stated on the webpage it is updated from. Nov 15 22:13:08 HOWEVER, if one knows of a font project for emojis being hosted through git with a proper license, I'd love to see it! Nov 15 22:13:46 what I would do in that case is, take a copy of the text from the website, stick it in a file next to your recipe, add a file:// reference to it in SRC_URI and then add that to LIC_FILES_CHKSUM Nov 15 22:15:18 bluelightning if that's all that can be done, then that's what I'll do I suppose. I was trying to avoid that sort of thing. However, I might just look for another project to use instead of this one. Nov 15 22:16:59 Huntereb: google turned up this: https://graphicdesign.stackexchange.com/questions/31625/are-there-any-free-emoji-fonts Nov 15 22:17:22 I suspect most won't include a bundled license statement, I guess that's typical of fonts Nov 15 22:18:37 bluelightning However, the ones linked do specifically state a common license. These might do! Nov 15 22:18:53 I'm saying "however" a lot, hmmm. I'm going to make note of that and stop. Nov 15 22:21:16 Hi all, Nov 15 22:21:17 I do have a problem with building rootfs image (tar.gz) Nov 15 22:21:31 I simply added IMAGE_INSTALL += mtd-utils Nov 15 22:22:15 and all utilities (including ubi) are installed in mtd-utils/2.0.0-r0/image/usr/sbin Nov 15 22:22:26 all binaries are also present in package subdir Nov 15 22:22:42 but when I build "image" Nov 15 22:23:04 which inherits only "core-image" Nov 15 22:23:25 only not ubi binaries are installed in rootfs Nov 15 22:23:59 and this is between bitbake -c cleansstate my-image && bitbake my-image Nov 15 22:24:41 bitbake -e or bitbake -v -DDD didn't give any results for e.g. nanddump or sbindir or /usr/sbin Nov 15 22:24:49 pure magic :) Nov 15 22:34:54 lukma: those are split out to a separate mtd-utils-ubifs package, so you need to include that instead / as well Nov 15 22:35:46 lukma: you can use either oe-pkgdata-util list-pkg-files -p mtd-utils , or just look under packages-split in the work directory for the recipe to find that sort of thing out Nov 15 22:36:52 bluelightning: Why they are splitted? Nov 15 22:37:22 lukma: in the general case, mainly to save space for those that don't need them Nov 15 22:37:53 So probably we have "base" and then splitted ones? Nov 15 22:38:24 yes, typically Nov 15 22:39:04 I've looked into the mtd-utils.bb file Nov 15 22:39:32 and there was a line PACKAGES =+ "mtd-utils-jffs2 mtd-utils-ubifs mtd-utils-misc" Nov 15 22:39:53 What is the connection between this line and doing the split ? Nov 15 22:41:14 And where it is decided which packages from split finally land in the rootfs? Nov 15 22:43:34 A.... ok Nov 15 22:43:39 Correct me if I'm wrong Nov 15 22:44:03 it would be the FILES_ lines that tell it what to put in each package Nov 15 22:44:43 the PACKAGES =+ "mtd-utils-jffs2 mtd-utils-ubifs mtd-utils says " lets divide mtd-utils on several packages:" - which are built Nov 15 22:45:10 and then user puts those packages (mtd-utils-ubifs) to packagegroup recipe for inclusion? Nov 15 22:46:04 Ok, now it works Nov 15 22:46:06 :) Nov 15 22:54:46 New news from stackoverflow: raspberry pi wifi 0 does not start automatically [closed] **** ENDING LOGGING AT Thu Nov 16 03:00:01 2017