**** BEGIN LOGGING AT Tue Feb 26 02:59:57 2019 Feb 26 08:51:11 New news from stackoverflow: Mono Cross Platform AOT (Ahead Of Time) compiling Feb 26 09:51:54 is there a way to speed up the building of the cross tool chain i have a machine that has 16 cores but it seems that only one is building the cross toolchain Feb 26 10:58:28 rburton, maybe mesa is building more stuff with meson than previously? Feb 26 10:59:55 RP, I can't disagree with that, it does need more testing and feedback. I'd also like to enable the headless oe-selftest on the autobuilders. Feb 26 11:30:55 kanavin: same output, but maybe meson is doing more actual work. the build walltime is about 30% of with autotools though Feb 26 11:31:23 kanavin: fun py bug Feb 26 11:32:24 kanavin: if i change the ia tune to skylake, py3 fails to build because py native can't find the loader (insert confused face emoji) Feb 26 11:32:52 kanavin: had to disable qemu-usermode as it appears skylake+qemu hangs qemu-user Feb 26 11:33:06 just doing a test build now to identify if its qemu-user or skylake thats to blame Feb 26 11:39:09 Hi, I'm trying to get an external toolchain into yocto :) Feb 26 11:39:20 but its a toolchain generated by buildroot Feb 26 11:39:28 and I dont see any meta that has support for it Feb 26 11:39:45 so I tried setting tcmode myself, but apparently I can only set it to default :/ Feb 26 11:39:50 is there any way to fix this? Feb 26 11:40:27 when I google it I always get yocto vs buildroot articles Feb 26 11:46:56 i would guess you need to make your own recipes to build it Feb 26 11:47:12 but it must be really exotic to have no similar recipes already Feb 26 11:47:22 varjag: you're misunderstanding the question Feb 26 11:47:50 fenrig: i'd ask kergoth really nicely, i know he uses external toolchains more than many Feb 26 11:48:16 by which i mean: most people don't use external toolchains, and fewer people configure one :) Feb 26 11:53:36 kanavin: ok i think what's happening is that the py3 install is running nativepython but that is attempting to load the module .so from the build, which matches archtecture so that works *but* has instructions my machine can't handle Feb 26 11:54:09 #0 0x00007fc1080e3b10 in PyInit__heapq () at /usr/src/debug/python3/3.7.2-r0/Python-3.7.2/Modules/_heapqmodule.c:643 Feb 26 11:55:24 rburton, that's not supposed to happen :-/ Feb 26 11:55:28 no Feb 26 11:56:50 just throwing in some debugging bits now to find out where its happening Feb 26 12:01:43 kanavin: problem with merging py and py-native is that its harder to iterate on bugs in target py3 without rebuilding the world Feb 26 12:01:57 kanavin: i wouldn't go back to two recipes though :) Feb 26 12:02:02 #coffeebreaks Feb 26 12:02:10 I noticed that my image contains the `systemd-container` package. I don't think I need that. Can I somehow blacklist packages from being installed? At least to understand who tries to pull it in, `git grep -e -container` did not bring up anything interesting Feb 26 12:03:31 you can use bitbake myimage -g to generate dependency trees Feb 26 12:08:05 also why are we building python2 for target to build python3 Feb 26 12:08:14 * rburton glares Feb 26 12:08:24 rburton, tell me about it :-/ I went through a million such rebuilds Feb 26 12:10:14 * rburton glares at openssl Feb 26 12:13:57 rburton: Thanks for the reply, but I am not following you :( Subpackages don't have their own task so how would I see them in `bitbake -g`? Feb 26 12:14:23 $ grep systemd-container recipe-depends.dot pn-buildlist task-depends.dot Feb 26 12:14:23 $ Feb 26 12:16:21 u1106: yeah sorry brain distracted. :) if you're using opkg, you can grep the package indexes... Feb 26 12:19:16 so I guess I have write a couple of lines of shell script to extract my ipkgs. Or maybe just including opkg into a test image might be faster??? Feb 26 12:37:13 ah it was easier than expected, because I found a script on my disk that nearly worked... Feb 26 12:38:18 so `systemd` requires `systemd-container`. That's weird, first split off a subpackage but than require it during installation Feb 26 13:09:25 kergoth: Can I ask you really nicely how I should include an external binary toolchain made by buildroot Feb 26 13:09:47 kergoth: :) at the moment I'm looking at http://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb?h=thud Feb 26 13:18:27 kanavin: during do_install it runs 'python3.7 ../Python-3.7.2/setup.py build' Feb 26 13:47:21 hey! is there any painless way to bring python2 to thud? Feb 26 13:54:53 just install it? Feb 26 13:55:05 its in oe-core Feb 26 13:59:36 rburton: but not the libs Feb 26 13:59:48 yes, the libs Feb 26 14:00:13 literally impossible to build python2 without the standard library Feb 26 14:00:22 if you're not installing it, then that's the problem Feb 26 14:00:52 sorry, I've meant pathon packages Feb 26 14:01:23 you should try explaining what you're trying to do Feb 26 15:13:47 should I use devtool to edit the default.xml in the base repo? Feb 26 15:18:57 I retract my stupid question. :-D Feb 26 15:26:11 kergoth: still here, if you have a moment, let me know. thx Feb 26 15:27:21 fenrig: every external toolchain is a little different, with different tools and different files for the different packages. meta-external-toolchain tries to be as generic as possible to give the best possible starting point for creating your own layer based on it for use with your particular toolchain. see meta-sourcery for an example of a layer based on it that t weaks for a particular toolchain Feb 26 15:27:41 kergoth: ah so the link I referenced was okay? Feb 26 15:27:53 meta-linaro is a different layer for the linaro toolchain Feb 26 15:27:58 as i said, every toolchain is different Feb 26 15:28:35 yeah offcourse :) no problem with that. I was already assembling my own layer as we speak Feb 26 15:28:45 so kinda picked the right direction Feb 26 15:28:47 thx :) Feb 26 15:29:25 i'd recommend basing it on meta-external-toolchain myself, but i'm biased since i'm the maintainer. you have multiple options as s tarting points, each will require a certain amount of work to adapt to the particulars of the buildroot toolchain Feb 26 15:31:42 kergoth: ah great, I'm looking into it Feb 26 15:34:01 kergoth: is it right that its on git.yoctoproject? Feb 26 16:48:15 Hello all, I'm fairly new to the Yocto Project and am using a version built for the TI AM5728 chip. I'm having a lot of trouble trying to figure out how to change the console to UART5 from the current UART3 Feb 26 16:48:55 I've tried a lot of methods I've found on the TI forums, I've gotten it to work on UART5 with RTOS, but I need to do it for Linux as well Feb 26 16:52:56 It involves changing the pin-muxing, we are using UART5 on different pins than what was already setup in the build. My changes are not working and if I change stdout-path then it does not boot at all Feb 26 22:23:57 New news from stackoverflow: Yocto: LICENSE="CLOSED" Feb 26 23:24:09 New news from stackoverflow: How to add ldd utility to bitbake image Feb 27 00:43:26 khem: the libc distro feature patch blew up on the autobuilder: https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/267 Feb 27 02:04:37 RP:let me take a look Feb 27 02:08:08 RP: how is x11 getting removed from poky distro config Feb 27 02:27:38 RP: sent a v5, I should not have removed DISTRO_FEATURES_DEFAULT **** ENDING LOGGING AT Wed Feb 27 02:59:56 2019