**** BEGIN LOGGING AT Fri Feb 02 03:00:05 2018 Feb 02 07:11:04 When I build, I get: /libudev.so: No such file or directory Feb 02 07:11:09 What is missing? Feb 02 07:25:28 Hi, guys! Feb 02 07:28:35 I have packagegroup with set of RDEPENDs. How can i remove depend from another file? I tried DEPENDS_remove, PACKAGE_EXCLUDE, but it can't help. Feb 02 07:30:08 unfortunately, i don't have to edit packagegroup directly Feb 02 07:30:35 acrap: create a .bbappend for the recipe creating the packagegroup and use RDEPENDS__remove = "what to remove" Feb 02 07:31:20 i thought about it) i will try. Why doesn't it work from local.conf? Is it normal? Feb 02 07:35:44 You can probably do RDEPENDS__remove_pn- = "what to remove" Feb 02 07:35:57 from within local.conf Feb 02 07:36:10 I'm a bit unsure if I got the syntax correct there though Feb 02 07:36:20 looks like it works from local.conf like you mentioned before Feb 02 07:40:38 oh, i don't know why but now bitbake trying to build package from its(packet that i removed from build) dependency list. Feb 02 08:13:01 Oh it is just a mess. I did it. Packet was declared on plenty of packagegroups and recipes (as dependency). Thank you) Feb 02 08:26:04 Is there a way to specify which files should be copied/kept/deployed after a u-boot build? Feb 02 08:39:46 UBOOT_CONFIG[secure-boot] = "mx6var_som_sd_SECURE_BOOT_config,sdcard,u-boot-ivt.img" Feb 02 08:40:16 this made it compile, but I haven't found out what exactly I told it there :) Feb 02 09:55:25 How to configure u-boot with bitbake? Feb 02 10:01:13 learningc: basically, don't. just select the machine and config. make u-boot self-contained. Feb 02 10:08:13 New news from stackoverflow: Yocto Project usb sensor acces Feb 02 10:41:03 When I build u-boot myself I get more output files than I get in the yocto build directory, and I can't find from the recipes why. My ultimate goal is to get, keep and deploy SPL, SPL.log, u-boot-ivt.img and u-boot-ivt.img.log. Feb 02 10:41:10 help! :) Feb 02 11:08:58 tasslehoff: different make targets being called? Feb 02 11:37:52 RP: I've set UBOOT_MAKE_TARGET = "", but I'll check the compile log Feb 02 11:39:54 tasslehoff: right, I'd start comparing the steps in the log/run files with what you're doing Feb 02 11:41:35 RP: yeah. is there a way to specify the additional files I want to install/deploy, or should I write _append functions where needed? Feb 02 11:45:14 tasslehoff: usually appending to the functions Feb 02 12:38:40 New news from stackoverflow: install qchart module without qtcreator Feb 02 12:43:28 RP: don't merge the bitbake patch of mine yet I found some bugs in it Feb 02 13:03:33 Hello, does anyone know if it is possible to compile and use UDisks2 without polkit as a dependency? Feb 02 13:13:06 Hello Yocto community Feb 02 13:13:35 I have just installed rocko on my PC Feb 02 13:14:12 and successfully generated core-image-minimal for qemu Feb 02 13:14:59 now i am trying to add a recipe example of hello world to my metadat layer Feb 02 13:16:34 so far, so good :) Feb 02 13:17:07 but i am facing this issue: i586-poky-linux-gcc: command not found when trying to execute bitbake hello Feb 02 13:18:25 that first and foremost sounds like your recipe is broken. can you pastebin it somewhere? did you base it off the examples in the manual? Feb 02 13:19:01 yes indeed https://pastebin.com/3dBKQAkP Feb 02 13:20:28 ok. bitbake core-image-minimal did work well, and you are trying to bitbake hello in the exact same shell, right? Feb 02 13:21:22 and does it really say "command not found", or "file not found"? Feb 02 13:22:38 as you're following the documentation (which is very good, keep that practise up!) you seem to have overlooked thd S= line, see http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#new-recipe-single-c-file-package-hello-world Feb 02 13:27:43 ah, yes got it Feb 02 13:28:10 but new it is stuck in something else.... seems in the packaging stage Feb 02 13:28:12 see https://pastebin.com/afca8cMF Feb 02 13:32:43 adding explicit ldflags, as mentioned in: http://www.yoctoproject.org/docs/2.2.1/ref-manual/ref-manual.html#migration-2.2-default-linker-hash-style-changed Feb 02 13:33:31 i'm not super sure if its correct, and if yes, then probably we should fix documentation. Feb 02 13:37:51 nrossi: ok, thanks for letting me know. I'd queued but not tested it yet! Feb 02 13:38:51 New news from stackoverflow: Yocto, core-image package removal, which .bbappend? Feb 02 13:39:24 shall add *TARGET_CC_ARCH += "${LDFLAGS}"* in the do install section Feb 02 13:39:42 shall add *TARGET_CC_ARCH += "${LDFLAGS}"* in the do_install section Feb 02 13:39:46 distsys: nope, to the recipe itself Feb 02 13:39:55 ok Feb 02 13:42:01 now it's working without errors Feb 02 13:42:07 thanks Feb 02 13:42:12 \m/ Feb 02 13:43:06 ok, seems *bitbake hello* will just build the hello package, it won't add it to the core-minimal-image Feb 02 13:43:33 to do so, shall i re-invoke bitbake core-image-minimal Feb 02 13:43:39 RP: whats the general stance on the hello examples? shouldn't documentation also reflect the changeover to devtool Feb 02 13:44:37 but doubting if it will rebuild all the image packages again :( Feb 02 13:44:38 distsys: no, that is basically unrelated. next, create an image recipe. you can base it off core-image-minimal-dev for example, and just add hello to its IMAGE_INSTALL variable Feb 02 13:45:10 distsys: if you just kick off core-image-minimal again, it will neither rebuild everything, nor will it include your new recipe Feb 02 13:46:46 RP: hey, quick question i'm just running the bitbake-selftest to double check before sending a v3. I noticed that the fetch2.git modules expects bitbake/bin to be on the path. Is it normal to expect that or should it be changed to automatically use the known tool from bin/ like the test classes in test/fetch.py do for the same binary? Feb 02 13:47:52 ok, i can create a new image recipe for myself that inherits from core-image-minimal, but actually, i am just add IMAGE_INSTALL += "hello" to the core-image-minimal recipe itself Feb 02 13:49:06 distsys: while that is technically true that you can just modify whatever you got included with poky, it totally hinders reproductibility, updating etc. Feb 02 13:49:23 nrossi: that does sound like a bug. I probably half fixed that recently... Feb 02 13:49:39 LetoThe2nd: it probably should, yes Feb 02 13:49:57 what did kergoth say yesterday? no idea why people always try to avoid creating their own images, or something alike. Feb 02 13:50:00 RP: mhkay Feb 02 13:51:16 yes, LetoThe2nd, you're right Feb 02 13:51:20 :) Feb 02 13:52:59 RP: should i make a patch that fixes that in fetch2.git? Feb 02 13:57:22 nrossi: please, we shouldn't need to set PATH Feb 02 14:05:10 RP: sent, i consolidated the use from the test class aswell Feb 02 14:07:14 nrossi: thanks! Feb 02 15:03:08 Does anyone use IceCream distributed compiling? Feb 02 15:30:06 Anyone here admin the yocto bugzilla? The reset password seems broken. I type my username and get: Feb 02 15:30:22 "The e-mail address you entered (nathani) didn't pass our syntax checking ..." Feb 02 15:31:44 nathani_: maybe you need to enter email? :) Feb 02 15:31:49 Nevermind... it's fine, but the second message is a little misleading Feb 02 15:32:21 after i input my e-mail (incorrectly) it says: "There is no user named 'my@email.com'" Feb 02 15:33:21 user name and e-mail used interchangeably. Bugzilla's fault Feb 02 15:33:45 I think they are the same, essentially Feb 02 15:34:07 forgot I registered another e-mail for the bugzilla, due to that warning message about e-mails being public facing Feb 02 17:56:59 45 Feb 02 23:59:39 When I mark a package as "nostamp", what does that do? How can I observe these stamps? Feb 03 00:13:09 nostamp is a flag on a task, not a package. Feb 03 00:13:39 a stamp is created when a task completes, and is used to determine if it needs to be re-run in subsequent bitbake invocations. nostamp means the task will run every time Feb 03 00:17:20 kergoth: well my real problem is I have tasks dependencies set up like "a:a -> b:b -> c:c" Feb 03 00:17:38 Even though c:c is nostamp, it doesn't propagate up and rebuild b:b and a:a every time Feb 03 00:18:13 Wondering what stamp / sstate caching is going on, since it is confused and doing the wrong Feb 03 00:18:19 thing* Feb 03 00:18:56 Like, "why didn't you re-run b:b"? Is there some way to get a log, or to see *why* bitbake decided not to run something? Feb 03 00:24:07 use bitbake's debug arguments to add more detail to the logs Feb 03 02:09:30 What browser does Yocto offer? **** ENDING LOGGING AT Sat Feb 03 03:00:01 2018