**** BEGIN LOGGING AT Tue Feb 21 03:00:00 2017 Feb 21 09:02:24 Hi. A cmake based recipe generates a version.h which then goes to ./build. And then the build in ./git falls over. Is there a yocto way to deal with this ? Feb 21 09:03:45 cb_: sounds like out-of-tree building is broken, and you basically need B=${S} Feb 21 09:09:37 cb_: There's unfortunately no secret trick to fixing all compile problems, even in yocto Feb 21 09:12:08 LetoThe2nd thanks a million. That did the trick. Feb 21 09:12:17 cb_: :-) Feb 21 09:46:50 morning Feb 21 12:04:36 cb_: fwiw your build problem was a bug in the upstream cmakelists, so you should file a bug (or patch) Feb 21 12:20:42 rburton: ++ Feb 21 13:42:31 rburton: working on an update bomb :) Feb 21 13:43:01 the one holdout is openssl 1.1, it's gonna be a separate task tracked in bugzilla Feb 21 13:43:20 yeah saw that bug Feb 21 13:43:21 thanks Feb 21 15:34:16 Hi ! As anyone tried meta-qt5 on dora branch ? I've got a lot of errors, and I don't know what to thinks about it... Feb 21 15:34:49 Kakounet: Dora is very old Feb 21 15:35:00 nearly 3 years Feb 21 15:35:43 CTtpollard: I know, but I don't have the choice... Feb 21 15:37:26 CTtpollard: I'm working on that board : http://architechboards-hachiko.readthedocs.io/en/latest/create-sdk.html?highlight=dora They did a layer for the hachiko board for dora and then stopped it Feb 21 15:37:53 Now I want to deploy qt5 on it to be able to handle bluetooth with qt Feb 21 15:43:02 JaMa: Hi, I'm still not able to reproduce that WKS_FULL_PATH expansion error. Can you provide more details about your setup? Feb 21 15:43:06 Kakounet: taking a bsp and forwarding it is no black magic.... Feb 21 15:45:29 LetoThe2nd: I'm sorry I don't understand your message... You suggest that I put the bsp layer from dora to the current branch ? Feb 21 15:45:36 Kakounet: yep. Feb 21 15:46:51 LetoThe2nd: Ok, I can give it a try. Do you have some advise/help/way to start on that subject ? Feb 21 15:48:41 Kakounet: a BSP layer that is remotely proper in design should contain only things that relate to the specifc hardware - bootloader, kernel, maybe some additional drivers. those are things that should work almost the same on never releases of poky. looking at meta-hachiko, i personally would just slap it onto poky morty and try. Feb 21 15:51:48 LetoThe2nd: ok thanks, I will try to do that ! Feb 21 15:56:33 ed2: what details do you want, do you want me to send you tarball with the build directory? Feb 21 16:16:02 joshuagl: have you fixed the core-image-basic thing on the ab? Feb 21 16:16:33 rburton: not on the primary yet, was waiting for builds to finish and then may have forgotten Feb 21 16:16:47 ok :) Feb 21 16:17:11 although there's still a build running Feb 21 16:17:16 so I may forget again :-/ Feb 21 16:17:57 joshuagl: https://autobuilder.yoctoproject.org/main/builders/nightly-distrodata/builds/10? Feb 21 16:18:08 why has that taken > 11hrs? Feb 21 16:18:30 good question Feb 21 16:18:33 we should ask the ab maintainer Feb 21 16:19:52 pstree confirms they've all just hung Feb 21 16:21:24 appear to be hung in fcntl calls Feb 21 16:21:26 nfs blip? Feb 21 16:21:42 joshuagl: going to press Stop unless you want to dig further now? Feb 21 16:22:04 could be an NFS blip, we've seen similar things before Feb 21 16:22:16 sadly I don't think we have the right people around to dig into this now Feb 21 16:22:22 rburton: please press Stop Feb 21 16:25:03 rburton: is that selftest failure a known issue? Feb 21 16:25:52 argh i bet selftest hung too Feb 21 16:26:03 i thought i fixed selftest Feb 21 16:28:03 huh the kernel one is new Feb 21 16:36:03 rburton: two selftest builders running, should I Stop them? Feb 21 16:36:19 yes Feb 21 16:43:01 rburton: ab updated, are you going to run a build? Feb 21 16:43:28 yeah will when i'm off this call Feb 21 16:44:14 hello again Feb 21 16:45:02 I'm wondering where the best place it's to add a meta layer to bblayers.conf. in poky/meta-poky ? Feb 21 16:45:38 aatchison: huh? you add any layer you need in conf/bblayers.conf of your build directory. Feb 21 16:51:08 JaMa: your local.conf and bblayers.conf should be enough as a start. Feb 21 16:57:59 ok, thanks Feb 21 17:05:23 ed2: sent to ML Feb 21 17:05:54 JaMa: thanks Feb 21 17:34:18 Hrm... I think I've stumbled across a bug in Bitbake, is the OE-issues mailing list the right place to discuss that? Feb 21 17:35:47 themikenicholson: theres a bitbake list Feb 21 17:43:26 rburton: Thanks Feb 21 18:12:18 Does someone have a useful sstate expire script that they can share? Feb 21 18:14:31 sveinse: there is one in oe-core already Feb 21 18:14:46 sstate-cache-management.sh Feb 21 18:15:17 sveinse: oe-core has what jama said, which is complicated and does magic. alternatively, i just use find $SSTATE -type f -atime +60 -delete Feb 21 18:15:51 joshuagl: is the AB fixed now? Feb 21 19:09:59 Heyo. I'm writing a recipe that has a SRC_URI from github. For some reason the hash changes every time I run bitbake, and i'm not sure why Feb 21 19:27:14 aatchison: what is the SRC_URI? Feb 21 19:29:34 it's https://github.com/MycroftAI/mimic.git Feb 21 19:30:08 I just changed it to a release tar, and it's working... checking out master just gave me a different md5 each time Feb 21 19:31:17 aatchison: that'll be downloaded with wget, if you put it in src_uri as is. Feb 21 19:34:56 I added protocol=http, would that help? I tried git:// but that didn't resolve Feb 21 19:36:43 "didn't resolve" is not useful Feb 21 19:36:53 git:// is the only way it'll use git to fetch at all Feb 21 19:37:02 unless you think wget is going to get you a git repository, that's your option Feb 21 19:37:18 git:// + ;protocol= is how you get it to use ssh or http rather than the git:// protocol Feb 21 19:38:24 ahh, thank you Feb 21 19:45:16 Any good resources for bitbake development? Not recipes but hacking on bitbake source? Looking for an easy way to run and add to unit tests. Feb 21 19:47:28 I'm building yocto for qemuarm. It defaults to armel. How difficult is it to build for armhf instead? And will it still be possible to emulate with qemu? Feb 21 19:48:21 themikenicholson: there's bb-selftest Feb 21 20:00:56 Hey, how do I see why "packages could not be configured offline" iow, why they ended up in delayed_postinsts? I feel like I've looked throught this before. Some package install log somewhere, perhaps? Feb 21 20:00:59 nrossi: your glib patches don't apply to master. if you can rebase to ross/mut in poky-contrib then that would be great :) (need to go walk the dog now) Feb 21 20:01:11 jmesmon: rootfs log should have it in there somewhere Feb 21 20:04:42 "systemd.postinst returned 1, marking as unpacked only, configuration required on target. Feb 21 20:04:46 hrm Feb 21 20:05:32 and that's it: no other output around that notification: "Configuring system.\nsystemd.postinst returned 1, marking as unpacked only, configuration required on target. Feb 21 20:05:43 Configuring kbd." Feb 21 20:08:14 I am new with yocto Feb 21 20:08:22 can I please ask a question ? Feb 21 20:08:52 ? Feb 21 20:09:10 hello Feb 21 20:09:30 can I ask a question ? Feb 21 20:12:43 ranchu: no you cannot Feb 21 20:13:33 oh Feb 21 20:14:00 ranchu: ask let your question here, and someone may answer =p Feb 21 20:14:10 istarilucky: too late, he left :) Feb 21 20:14:21 hehehehe Feb 21 20:14:43 i was thinking you was joking about can and may =/ Feb 21 20:15:20 jmesmon: you need to inspect the postinst script, maybe add additional debugging to it to see why it doesn't complete successfully Feb 21 20:15:30 the script should be defined in the recipe Feb 21 20:16:34 istarilucky: no, I just thought it's ridiculous to ask a permission, and wanted to 'deny' it :) Feb 21 20:17:37 hi Feb 21 20:17:47 can I ask a question ? Feb 21 20:18:11 ranchu: asking to ask is considered bad form. You are encouraged simply to ask the question. Feb 21 20:18:31 Right....:) Feb 21 20:19:50 I am trying to deploy on ATOM board (congatec). I have found the following link https://git.congatec.com/x86/meta-congatec-x86/blob/dizzy/README So I guess it will be a good starting point, Right ? Feb 21 20:20:39 dizzy is old. I'd recommend looking for modern support for your board: https://wiki.yoctoproject.org/wiki/Releases Feb 21 20:20:51 But I will probably need to upgrade to RT PATCH , Is it just a matter of adding "PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" and calling bitbake again ? Feb 21 20:21:34 OK Feb 21 20:22:08 if your bsp support using the linux-yocto-rt kernel, and everything depends on the virtual/kernel instead of on some other linux kernel revision, yes, that should work. Feb 21 20:23:09 @jmesmon, Thanks. Whenever a chane is required, I just need to edit local.conf and call bitback again ? Feb 21 20:23:14 change Feb 21 20:23:41 ranchu: yes Feb 21 20:23:59 ranchu: if its a fairly standard atom then meta-intel may work Feb 21 20:25:08 OK, that's good info. yet, it's quite standard ATOM E8300. UBUNTU INSTALL HAVE NO ISSUES Feb 21 20:25:17 sorry for the capslock. mystake. Feb 21 20:25:32 then the latest meta-intel release is pretty much what you want Feb 21 20:25:59 OK, that's good information. many thanks for your assistance all !! Feb 21 20:28:54 I also have some deplyment question. In the readm, I see that deplyment is usuall by doing "dd" to usb. but how do you install to hdd (hard disk) Is it by just "dd" to HDD ? Feb 21 20:30:23 ranchu: you probably want to write an email to the address at the end of the README Feb 21 20:31:09 I can't see address in http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/about/ Feb 21 20:31:28 ranchu: https://git.congatec.com/x86/meta-congatec-x86/blob/dizzy/README Feb 21 20:33:12 I guess that if copying the image to usb start correctly when usb is configures as boot device, doesn't it make sense that dd to HDD device should also work (I haven't tried it yet, just asking) Feb 21 20:33:58 ranchu: also, why are you looking at dizzy branch? there are more recent branches in the same repo https://git.congatec.com/x86/meta-congatec-x86/branches Feb 21 20:34:14 so you can take krogoth and use that with yocto's krogoth release Feb 21 20:34:56 yes, I'll do that Feb 21 20:34:59 thank Feb 21 20:35:17 I wasn't aware of it... Feb 21 20:35:28 generally, if your board is congatec, then you should be talking to congatec people... Feb 21 20:36:47 Right, I'll try to... yet I see that in other readme it is mostly deployment to usb. So, I wander if "dd" to HDD should work too if I'll configure HDD as boot device/ Feb 21 20:37:18 how would we know? none of us here has this board, or know anything about it. this is a question for the company that makes the board. Feb 21 20:37:45 OK, I see. Thanks. Feb 21 20:38:42 Thanks a lot @kanavin Feb 21 20:46:31 rburton: AB is updated, yes Feb 21 21:12:32 I am trying to apply rt patch with yocto. I use instructions in https://community.nxp.com/thread/336568 . But I don't understand . It says "PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" If you are creating a new BSP which should use linux-yocto-rt by default, use the line above in the $MACHINE.conf in your BSP layer, and specify the following in a linux-yocto-rt bbappend recipe:". What is " linux-yocto-rt bbappend recipe" ? Feb 21 22:14:44 hello, when we call "bitbake " again, is it searching on all recipes/layers to see if something has changed and what need to be cokmpiled again ? Feb 21 22:16:12 yes, it looks for changes to the recipes. Feb 21 22:16:27 thanks jmesmon Feb 21 22:16:59 I am trying to apply rt patch with yocto. I use instructions in https://community.nxp.com/thread/336568 . But I don't understand . It says "PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" If you are creating a new BSP which should use linux-yocto-rt by default, use the line above in the $MACHINE.conf in your BSP layer, and specify the following in a linux-yocto-rt bbappend recipe:". What is " linux-yocto-rt bbappend recipe" ? Feb 21 22:17:49 instructions in https://github.com/openembedded/oe-core/tree/master/meta/recipes-rt Feb 21 22:19:07 ranchu: the dev manual may be useful for understanding some of the pieces that make up yocto: https://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#using-bbappend-files Feb 21 22:19:49 ok thanskl Feb 21 22:20:07 I can't comment on the correctness of that forum post, but I'd generally be cautious about trusting it. Feb 21 22:20:59 community.nxp.com tends to have a lot of folks working with old versions of yocto and doing somewhat questionable things. Feb 21 22:25:27 Has any of you experimented with vm.dirty_ratio and vm.dirty_background_ratio settings for yocto build servers? Feb 21 22:31:58 Ah, systemd.postinst was failing due to update-alternatives failing and (I'm guessing here because there is nothing in the log) update-alternatives was unable to update /sbin/runlevel because busybox dropped a script there (or at least, that is what the script says it is from). Or perhaps something else is dropping runlevel there. Sounds like it could be a workaround for post install using update-rc.d to work. Feb 21 22:32:05 when we remove package from recipe/layer, does it get remove from output/image too ? Feb 21 22:32:24 after bitbake Feb 21 22:32:59 ranchu: no. bitbake will complain that it can't build the image because it doesn't know that package name. Inclustion in the image is controlled by some image variables (IMAGE_INSTALL, etc) Feb 21 22:33:24 remove it from those variables, and a package will no longer be in the image. Feb 21 22:33:53 Right, understood Feb 21 22:42:47 ah yes, looks like the addition of runlevel was recent. khem: seems like busybox's runlevel stand-in needs to be speced as an alternative? I believe the rest of busybox-init may also be affected, but may have escaped notice due to already being symlinks to bb. Feb 21 23:58:29 Hi guys, I'm building my own yocto image and I'm using raspberrypi as a target Feb 21 23:58:57 I'd like to overwrite cmdline.txt file but I'm not able to do that Feb 21 23:59:25 what (or where) should I write my own code in order to do that ? **** ENDING LOGGING AT Wed Feb 22 03:00:01 2017