**** BEGIN LOGGING AT Fri May 10 03:01:14 2019 May 10 05:11:41 what TOPDIR defined as May 10 06:27:12 good morning May 10 07:05:32 * alessioigor waves all May 10 07:05:43 Is there a way to generate a x86_64 image, few ARM images and, at the end, an image with the former x86_64 image and the SDKs installed of the latters'? May 10 07:12:49 alessioigor: all in a single shot ? May 10 07:14:37 mckoan: No I'm not so ambitious :-) May 10 07:30:09 alessioigor: I think you should be able to achieve that using https://www.yoctoproject.org/docs/2.8/dev-manual/dev-manual.html#dev-building-images-for-multiple-targets-using-multiple-configurations May 10 07:31:11 At least that provides you with some mechanism to build stuff for multiple machines, and make a recipe for one machine depend on certain tasks from a recipe for another machine. May 10 07:33:43 erbo: I'll give it a try. Thank you! May 10 08:32:37 Hello everyone May 10 08:37:09 There is a problem when I try to generate core-image-x11. When rootfs is generated, the following error occurs. Do you have any leads for me to debug this ? (https://pastebin.com/5ftX7MVQ) May 10 08:37:58 The MACHINE is imx6qdlsabresd.conf and the problematic package is xf86-video-imx-vivante. May 10 08:39:43 All files are untouched. I only modify imx6qdlsabresd to get u-boot from meta-dhcom instead of the meta-freescale (which is not deploying) May 10 09:45:53 RP, any hint about why webkit update was dropped? May 10 10:23:34 New news from stackoverflow: Files related to Audit daemon are not in rootfs May 10 12:15:00 which ML should I submit a patch for bitbake/lib/bb/fetch2/__init__.py to? oe-core? bitbake-devel? May 10 12:16:54 ernstp, bitbake-devel May 10 12:21:39 kroon: thanks May 10 13:39:44 . May 10 13:54:13 New news from stackoverflow: How to send a compiled file to sama5d27 board and execute it May 10 14:06:52 is there macro that describes the current location of where the yocto build dir is May 10 14:26:01 ${B} May 10 14:32:46 can yocto access the value of the home directory $HOME i.e. /home/user ? May 10 14:33:29 I would like to set the TMPDIR to /home/user/something May 10 14:34:28 the point is that the build system shouldn't just randomly take stuff off your filesystem May 10 14:34:36 everything should be specified in the recipes May 10 14:35:08 yocto is not that great at it but it's an ideal to strive for May 10 14:38:52 milloni: could you explain your point a bit more May 10 14:39:49 i was not interested in taking "off" but when bitbake is complete the results end up at a location relative to my home directory May 10 14:43:03 oh, then i misunderstood your point, my apologies May 10 14:46:00 no I didn't explain May 10 14:51:22 i'm trying to remove wpa-supplicant from my build, IMAGE_INSTALL_remove doesn't work, i think it's because connman is built with support for wifi May 10 14:51:36 how can i build connman with no wifi support May 10 14:52:33 i looked at https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivity/connman/connman.inc May 10 14:53:22 i added PACKAGECONFIG_remove_pn-connman = "wifi" to my image configuration but that didn't do it May 10 15:25:49 milloni: image config won't help, local.conf or a bbappend May 10 15:26:14 put it in the image configuration and the assignment is only visible to the image recipe, connman won't see the change May 10 15:26:35 so, sorry, which bbappend? May 10 15:26:51 a bbappend you write for connman May 10 15:26:57 or your local.conf or ideally your distro config May 10 15:27:20 my local.conf seems to be autogenerated... May 10 15:27:33 it's not checked into the git repo i'm looking at May 10 15:27:38 it's a bit of a strange build May 10 15:29:35 rburton: would it be something like recipes-connectivity/connman/connman_%.bbappend ? May 10 15:29:39 yes May 10 15:29:50 thanks, i'll try that May 10 15:34:30 rburton: will PACKAGECONFIG_remove_${PN} do (in the bbappend) instead of PACKAGECONFIG_remove_pn-connman? May 10 15:35:24 in a bbappend just PACKAGECONFIG_remove May 10 15:38:53 ok May 10 15:54:36 New news from stackoverflow: Cross-Compiling to ARM target hardware: getting errors : aarch64-linux-gnu-g++: error: unrecognized command line option ‘-msse4.2’ || Yocto Toaster only shows first rootfs built May 10 16:27:43 huh, https://tirkarthi.github.io/programming/2019/05/08/f-string-debugging.html May 10 17:41:45 kanavin_: lots of autobuilder failures I haven't had a chance to summarise May 10 17:46:02 will "broke" work ? May 10 18:25:02 New news from stackoverflow: How to send a compiled file to sama5d27 board and execute it? May 10 19:21:46 RP, armpit Maintenance complete. May 10 19:22:34 RP, Curious about starting a benchmark build. Should we use a-full or a-quick? And is the warrior branch the best for this? May 10 19:25:11 New news from stackoverflow: Upgrading (overriding) an entire recipe in a custom layer May 10 20:29:06 halstead, yes, warrior should be good May 10 20:29:08 thanks May 10 20:29:44 armpit, Do you know if quick or full is a better benchmark for comparing cluster performance? May 10 20:31:26 full hits all hosts for oe-selftest May 10 20:31:53 so I guess a-full May 10 20:33:13 unless you are thinking of buildperf? May 10 20:35:54 I'm thinking of overall build time. May 10 20:36:15 I'll invalidate sstate and run a-full on warrior. May 10 21:06:00 k **** ENDING LOGGING AT Sat May 11 02:59:57 2019