**** BEGIN LOGGING AT Wed Jul 18 03:00:02 2018 Jul 18 04:15:34 New news from stackoverflow: How do I generate a toolchain for Windows using Yocto? Jul 18 06:11:13 RP & rburton: I'm sorry but BuildCompleted is not helping in my case, I tried that already. Because this will be triggered only if I add this handler on the recipe itself, then this specific recipes must complete its execution to trigger the event handler. But my case is different, I'm looking for something more generic, on the overall bitbake session, whatever recipe was executed, a more generic trigger. Is there any? Jul 18 06:12:00 shatrix_: it's not recipe-specific, you would enable it from a class and then use INHERIT += to enable the class globally Jul 18 06:13:00 u1106_: I like this workaround, but still I'm searching for something more generic, even without building the whole image, that works with any bitbake session, executing any recipe, and a function to be triggered at the end of the bitbake session. I even thought about patching the bitbake script itself! Jul 18 06:14:06 shatrix: BuildCompleted is exactly that event Jul 18 06:31:44 shatrix: as a matter of fact I don't call bitbake here, but my own bitbake-wrapper.sh, which does a couple of housekeeping things before and after the build. I can also use it in development work when I just run a single task. Maybe that could have been achieved using BuildStarted and BuildCompleted, too. But I have never had any problems with my wrapper. Jul 18 14:30:31 when doing a "bitbake swupdate-image" i am getting: ERROR: swupdate-image-1.0-r0 do_rootfs: libconfig not found in the feeds (imx6ul_var_dart armv7ahf-neon-mx6ul armv7at2hf-neon-mx6ul armv7at2hf-neon armv7ahf-neon armv7at2hf-vfp armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp noarch any all) in /Storage/swupdate-test/sources/poky/build-hw-test-image/tmp/deploy/rpm. Jul 18 14:32:59 i don't understsand the error - can someone please elaborate? Jul 18 14:36:24 why is do_rootfs LOOKING for a package, shouldn't it be GENERATING them? Jul 18 14:36:42 rpm can't find the package that it was told would exist Jul 18 14:36:54 find out what should have built it, and figure out why it doesn't exist Jul 18 14:37:44 thats rpm trying to find a package its being told to install Jul 18 14:38:59 rburton: i think i'm following you. the do_rootfs is trying to create the rootfs and it needs the defconfig.rpm to do so and can't find it Jul 18 15:01:30 rburton: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ross/binutils&id=23c3c730571b26e95df9276ea97ad77f2aa977b4 is missing the patch itself :) Jul 18 15:16:08 rburton: here is the recipe for swupdate-image. it clearly has the libonfig package specified in the "IMAGE_INSTALL" list. i don't understand why bitbake would not have generated them. https://paste.fedoraproject.org/paste/FukkBXbmMVXB4WuIMvKK-g Jul 18 15:16:34 s/them/it/ Jul 18 15:18:13 bitbake libconfig, see if anything happens. see if the file does exist in deploy. Jul 18 15:18:19 note another strange thing: when i rerun the exact same bitbake command, i.e., "bitbake swupdate-image", i get the same message for some of the other packages, e.g., "busybox" and "mtd-utils", seemingly randomly. Jul 18 15:18:41 ok Jul 18 15:23:22 interesting. the initial "bitbake libconfig" did not generate any rpms. i then ran "bitbake libconfig -c cleansstate" followed by, again, "bitbake libconfig" and it did generate libconfig-blah.rpms under deploy Jul 18 15:32:09 ok, so i did a "rm -fR sstate-cache", then a "bitbake swupdate-image". i am still getting these "not in feeds" errors for the various packages initially, but if i go back a do a "bitbake -c cleansstate" followed by a "bitbake ", things work Jul 18 15:32:21 why would i have to do this? Jul 18 15:47:20 sounds like it thinks something else is providing libconfig Jul 18 15:48:36 and you're forcing the situation by forcing a build of the right bits Jul 18 15:49:09 RP: is there a way to ask bitbake what recipes provide a specific name? Jul 18 15:49:28 i wonder if there's a packages-dynamic glob going wrong Jul 18 15:55:43 Hi, I'm trying to build the `core-image-full-cmdline` receipe and getting the following error: Jul 18 15:55:44 * check_data_file_clashes: Package systemd wants to install file /home/tpreston/muos/build/tmp/work/jetson_tx2-poky-linux/core-image-full-cmdline/1.0-r0/rootfs/etc/localtime Jul 18 15:55:44 But that file is already provided by package * tzdata ing file. Jul 18 15:55:44 I've tried building a dependency graph to find out where the conflicting packages are but at 28k lines dot is taking a while... Where can I find conflicting packages providing tzdata. Jul 18 16:06:40 tpreston: well its right, they do have the same file Jul 18 16:08:27 i wonder if thats a systemd config thing Jul 18 16:08:32 anyway INSTALL_TIMEZONE_FILE=0 might solve it Jul 18 16:18:00 New news from stackoverflow: Error build fortran under Yocto Jul 18 16:33:27 rburton: if a recipe has an IMAGE_INSTALL list, how could it possibly not know that it must build those packages inot the package feeds? Jul 18 16:33:40 yates: becayse another package may claim to build libconfig Jul 18 16:33:43 but not actually Jul 18 16:35:38 you mean another recipe? Jul 18 16:35:59 ..another recipe may claim to build libonfig? Jul 18 16:37:26 if things are operating normally, is there an actual libconfig.bb that specifies how to build the libconfig-blah.rpm? Jul 18 16:39:35 ah, maybe not? Jul 18 16:39:41 "do_package_write_* tasks"... Jul 18 16:41:32 yates: yes libconfig is part of meta-oe Jul 18 17:07:12 RP: what's the point of hostperl-runtime-native? Jul 18 17:14:00 * yates is listening to a song that reminds him of yocto, "It Don't Come Easy" ... Jul 18 17:21:22 is there a way to ask bitbake what recipes provide a specific name? Jul 18 17:29:07 Is there a means to make a machine or image definition depend upon a package that only outputs to the deploy directory? I'm looking for an example somewhere. Jul 18 17:55:14 Hello, does someone know an easy way to build openjdk-8 to aarch64 on yocto 2.3? Jul 18 17:55:40 Tried using the master branch from meta-java, but i get a parse error Jul 18 18:08:56 YP 2.3 would be the branch Pyro.. if there is no pyro branch for meta-java, then you will have work to do Jul 18 18:09:32 Is Marek Vasut here by chance? Jul 18 18:12:34 There is a pyro branch in meta-java repo, but it doesnt support aarch64. master branch does support, but it is not as simple as just checking out to it and building. Jul 18 18:13:16 I know I may have to backport it to pyro, but I don' t even know how to start Jul 18 18:39:40 rburton: how can i find this issue? i am flailing. Jul 18 18:41:11 i am totally stuck. Jul 18 18:45:36 here is the entire output: https://paste.fedoraproject.org/paste/EKUFQk~ilbfzzcTUCamTbw Jul 18 19:05:46 yates: are you building from poky master or pyro? mtd-utils_git.bb@master inherits update-alternatives which might somehow interfere https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/mtd/mtd-utils_git.bb?h=master Jul 18 19:16:55 lindblandro: i'm using morty Jul 18 19:18:47 i don't think it has anything to do with mtd-utils. i'm getting the same error on almost all the packages specified in the IMAGE_INSTALL list Jul 18 19:19:49 everytime i run "bitbake swupdate-image" it lists a different package as "not found in the feeds..." Jul 18 19:20:16 do other images build correctly? is it isolated to swupdate-image? Jul 18 19:23:43 kergoth: did you mean "images" or should i try other non-image recipes as well? Jul 18 19:24:11 non-image recipes wouldn't tell us anything, since the problem is isolated to rootfs creation with IMAGE_INSTALL Jul 18 19:26:14 is there a generic image i can try? our main image is hosed now because these swupdate mods are not yet complete Jul 18 19:28:27 yates: Try core-image-minimal ? Jul 18 19:30:02 hmm same probloem there: https://paste.fedoraproject.org/paste/Oxcc72ePBiRjpsWp9yGxsg Jul 18 19:31:04 yates: Lookls like you package feeds might be messed up Jul 18 19:32:42 should i just blow away this whole project folder and recreate a new one? Jul 18 19:33:26 yates: It's probably the easiest.... make sure you keep your sstate though Jul 18 19:33:42 It *is* possible to make it regenerate the package feed.... but I don't remember how Jul 18 19:34:04 If you keep your sstate cache and rebuild from it, your build should go pretty quick Jul 18 19:34:08 what, to save time? No thanks - i'd rather start with a clean slate than taking the chance of tainting the new project Jul 18 19:34:22 saving sstate will be fine... Jul 18 19:34:27 *should* Jul 18 20:45:50 the fresh project build worked Jul 18 20:45:56 i guess i hosed something Jul 18 20:46:00 somewhow.. Jul 18 20:46:15 thanks guys (gals?) for your help **** ENDING LOGGING AT Thu Jul 19 03:00:02 2018