**** BEGIN LOGGING AT Thu May 31 03:00:08 2018
May 31 06:38:37 <__MC__> Someone can help me to understand this error? https://pastebin.com/8dJLJPbG Thanks.
May 31 07:18:21 <JaMa> __MC__: which triggered exception OSError: [Errno 12] Cannot allocate memory
May 31 07:18:27 <JaMa> running out of memory?
May 31 07:28:22 <__MC__> JaMa: could be. I've tried many time, but now it is finished without problems. In the next compile I will monitor the ram usage and if necessary, I will pump up the ram of the vm. thanks.
May 31 08:08:52 <yocti> New news from stackoverflow: yocto sunxi machine name <https://stackoverflow.com/questions/50619578/yocto-sunxi-machine-name>
May 31 09:08:30 <__MC__> Ok, another question.. I'm trying to make an image with qt5 for imx28evk board. I get this error.. https://pastebin.com/tQLxCuBa I think that opengl-desktop is missing.. what recipe I have to add? Maybe this: qt5-opengles2-test?
May 31 09:21:26 <alkino> hi o/
May 31 09:21:34 <alkino> i'm trying to do a recipe for ldc (d compiler)
May 31 09:21:44 <alkino> last version need a d-compiler to build the d compiler
May 31 09:21:49 <alkino> what is the right way?
May 31 09:22:00 <alkino> 1) use local d compiler on the host
May 31 09:22:09 <alkino> 2) download an old d compiler and build it
May 31 09:22:18 <alkino> 3) download a pre-build d compiler
May 31 10:05:18 <abiasci> Hi all. I have a problem with a recipe (.bbappend) using SRC_URI_append_<machine>
May 31 10:05:40 <abiasci> Could someone help me ?
May 31 10:12:17 <mckoan> __MC__: try adding this to local.conf : DISTRO_FEATURES_remove = "x11 wayland"
May 31 10:12:30 <mckoan> abiasci: describe the problem
May 31 10:17:21 <abiasci> Yes ... I have a recipes (.bbappend) that will perform a SRC_URI_append_<machine>. I added in conf/machine/<machine>.conf MACHINEOVERRIDES tha name of my machine.
May 31 10:17:44 <abiasci> during the configure/build phase, the SRC_URI_append_<machine> is ignored
May 31 10:20:19 <abiasci> The .bbappend has also do_install_append_imx6ull_t11() but, it is ignored as well.
May 31 10:20:30 <abiasci> imx6ull_t11 is the name of my machine.
May 31 10:23:07 <mckoan> abiasci: you can't use a machine name nor a recipe name with underscore '_'
May 31 10:23:25 <mckoan> abiasci: replace with imx6ull-t11
May 31 10:34:40 <__MC__> mckoan: same error :(
May 31 10:36:18 <abiasci> OK .. does it works !! Thanks a lot.
May 31 12:32:12 <fberg> hello guys ! Does anybody know how to use correctly SRC_URI in order to have two different git repository at a different specific branch ? I've written this recipe https://pastebin.com/RTihGSjc but bitbake says that: pathspec 'rpi-4.9.y' did not match any file(s) known to git.
May 31 12:32:48 <fberg> Seems that git is checking out the second repository branch while in the first reporistory
May 31 12:32:58 <fberg> Does anybody have any idea ?
May 31 14:36:07 <armpit> bug triage
May 31 14:37:56 <moto-timo> what's call info for bug triage meeting? old bridge is silent
May 31 14:41:33 <moto-timo> https://www.yoctoproject.org/public-virtual-meetings/
May 31 16:06:33 <chainey> Poky is described as a reference system, to more or less demonstrate how the components can work together. However, I'm curious if some/many/most people are using Poky in production. I'm three days in to exploring the YP, and this has been unclear to me. Could anyone shed some light?
May 31 16:08:43 <kergoth> nearly everyone needs to customize heavily, whehter that's modifying an existing distro (bad) or creating their own (good)
May 31 16:12:04 <chainey> mm, so that establishes an ideal. In practice, would you say many are erring on the worse side? I ask because most public tutorials feature Poky, so it's difficult to discern.
May 31 16:14:43 <chainey> perhaps the learning curve goes something like: try Poky, modify Poky, create from scratch w/ Poky as a reference, monitor Poky for best practices. Is my guess kind of right there?
May 31 16:15:20 <JaMa> yes, this sounds right, but nowadays I would start with nodistro config which is quite reasonable as well
May 31 16:15:45 <chainey> Interesting. Ok.
May 31 16:16:55 <chainey> Thank you kergoth and JaMa.
May 31 16:18:39 <kergoth> I expect most tutorials are wanting to introduce and get the user to a successful build as quickly as possible rather than giving example setups closer to real world application
May 31 16:19:58 <chainey> That indeed seems to be the case.
May 31 16:54:10 <TimDH> Where should INITRAMFS_IMAGE be defined? In machine conf file it causes a “nothing provides” error. In my image recipe there are no errors, but the FIT image file is not rebuilt.
May 31 18:46:31 <khem> zeddii: around? we need another fix for kernel for gcc8 https://github.com/raspberrypi/linux/commit/854e55ad289ef8888e7991f0ada85d5846f5afb9
May 31 18:47:08 <khem> zeddii: I am using 4.15 of linux-yocto here and it fails to build with gcc8 for x86_64
May 31 19:02:35 <khem> zeddii: this one too https://github.com/torvalds/linux/commit/ad343a98e74e85aa91d844310e797f96fee6983b#diff-89b6591452f7b3e17de375ff48d012c8.patch
May 31 23:06:25 <fancer> kergoth: hello, man!
May 31 23:07:18 <fancer> As was promised I added a few changes to the meta-external-toolchain and posted them to my repo:
May 31 23:07:18 <fancer> https://github.com/fancer/meta-external-toolchain-integrate
May 31 23:07:45 <kergoth> hey, ah thanks. havent had a chance to mess with meta-external-toolchain recently, planning to take a look this weekedn. i need to look at it anyway since there's impact due to the removal of libnsl & rpc bits from glibc in oe-core
May 31 23:08:00 <fancer> The branch is named fancer-integrate.
May 31 23:08:49 <fancer> Ok.
May 31 23:09:20 <fancer> BTW are u finished with the commits authorship settings?
May 31 23:09:43 <fancer> * I mean the fancer-integrate branch of the repo.
May 31 23:10:18 <kergoth> no, pretty sure i still need to go back and adjust the authorship and add your signoff along with mine to the changes split out from your original commit
May 31 23:16:06 <fancer> I see, thanks. Even though we worked on it not that much time ago, I started to forget details. I do rememeber though when I finished working on my cross-canadian version of the external-toolchain it turned out you already did most of the work I did too. Today I just couldn't believe, that after split and merge my original work converted to two commits only.) Thanks for clarification.
May 31 23:17:29 <fancer> and sorry for being a bit picky in this matter.
May 31 23:18:30 <kergoth> no problem, sorry for the confusion. basically this entire branch is your changes, just broken up to be granular, gradually, it took awhile to go through. never got a chance to go back and finish it and correct the authorship. i expect i'll drop a few of the ct-ng-specifics and add a couple minor tweaks on top of it, but the core of it is your commit on your master-tp branch
May 31 23:19:52 <fancer> thanks. Ping me when you finished I'll test it out on my setup.
May 31 23:20:18 <kergoth> ugh, still need to update the readme and stuff too, still has sourcery references
May 31 23:24:22 <fancer> aha
May 31 23:26:06 <fancer> soon we'll open meta-bsp layer for this baby:
May 31 23:26:07 <fancer> https://en.wikipedia.org/wiki/Baikal_CPU
May 31 23:26:49 <fancer> Alas, it will work with our kernel/u-boot repos for now...
**** ENDING LOGGING AT Fri Jun 01 03:00:09 2018