**** BEGIN LOGGING AT Fri Feb 23 03:00:01 2018
Feb 23 06:42:43 <yocti> New news from stackoverflow: Is it possible to use Yocto Project to build an image for a Python back-end/C++(Qt5) front-end application? <https://stackoverflow.com/questions/48942330/is-it-possible-to-use-yocto-project-to-build-an-image-for-a-python-back-end-c>
**** ENDING LOGGING AT Fri Feb 23 10:01:44 2018

**** BEGIN LOGGING AT Fri Feb 23 10:01:45 2018
**** ENDING LOGGING AT Fri Feb 23 10:01:49 2018

**** BEGIN LOGGING AT Fri Feb 23 10:04:11 2018
Feb 23 10:22:39 <ChrysDaze> Hi everyone ! I have a little question. There is a "clean way" to modify a ".py" file into bitbake directory ? Because i would like to modify the git.py as i would like to change one of the command in the case of unpack. Do i just modify the file directly or there is a clean way into my meta to apply a patch ?
Feb 23 10:22:41 <ChrysDaze> Thanks.
Feb 23 10:45:31 <yocti> New news from stackoverflow: Why would a yocto patch fail under devtool but not during a normal build? <https://stackoverflow.com/questions/48945909/why-would-a-yocto-patch-fail-under-devtool-but-not-during-a-normal-build>
Feb 23 13:16:09 <ChrysDaze> No idea?
Feb 23 13:17:57 <welhm> ChrysDaz: is the py file part of bitbake or part of the target os
Feb 23 13:18:29 <welhm> ?
Feb 23 13:44:36 <ChrysDaze> @welhm : part of bitbake
Feb 23 14:24:00 <RP> ChrysDaze: we don't really offer facilities to patch bitbake itself, the hope is we can standardise on those pieces
Feb 23 14:25:52 <ChrysDaze> @RP : I use a version of bitbake that in git.py it use a old command of git. So the best I can do is just modify it?
Feb 23 14:44:47 <RP> ChrysDaze: yes, the pressure is there so we can fix these issues upstream
Feb 23 15:16:32 <ChrysDaze> @RP : No problem, thanks for answering.
Feb 23 15:28:24 <kergoth> absolute worst case you can monkeypatch a fetcher to fix a bug. *not* recommended, could easily break, but i've done it before when stuck due to frozen codebases and release timelines
Feb 23 15:28:35 * kergoth yawns
Feb 23 15:53:32 <eduardas_m> hello, what is the standard way of blacklisting a kernel driver module in Yocto? so that it is built and shipped, but not loaded by default
Feb 23 15:57:42 <eduardas_m> is it necessary to specify editing of /etc/modprobe.d/blacklist.conf by myself or is there a special variable for that?
Feb 23 15:58:06 <eduardas_m> if there is, I have not found it in the official documentation yet
Feb 23 16:13:45 * armpit need more coffee.. tried to apply a userland patch to the kernel
Feb 23 16:14:12 <Crofton|work> lolz
Feb 23 16:15:59 <majuk> So I have a system image put together and I am trying to get all my changes out of the build directory and into my custom layer. One thing I'm not getting is how and where to establish additional BBLAYERS that my build depends on so that I don't have to manually insert them to conf/bblayers.conf
Feb 23 16:16:23 <Crofton|work> bblayes.conf.sample
Feb 23 16:16:31 <ChrysDaze> @kergoth :)
Feb 23 16:16:39 <kergoth> can't do that without using your own templates (TEMPLATECONF), custom setup scripts, or at least wrap the stock ones to run your needed bitbake-layers add commands
Feb 23 16:16:40 <Crofton|work> and your own TEMPLATECONFDIR?
Feb 23 16:17:20 <majuk> Gotcha. Ok, that's what I was looking for in setup-environment but not finding. Thanks Crofton|work kergoth
Feb 23 16:47:23 <spierepf> Hello. My poky/pyro system is missing libgcc_s.so.1. Is that a configuration option of the libgcc package?
Feb 23 18:49:05 <spierepf> I am looking for some help with libgcc_s.so.1 It is missing from my image...
Feb 23 22:31:02 <kergoth> RP: huh, just noticed shutil.which() that was added in python 3.3. can accept a custom mode and PATH string.
Feb 23 22:32:00 <RP> kergoth: ah, nice. Can it give us history though? I think that was the last change we needed with ours...
Feb 23 22:32:24 <RP> kergoth: for parsing we need to know which files were considered, not just the final result :/
Feb 23 22:35:09 <kergoth> ah, probably not. haven't checked, though
Feb 24 00:12:28 <Guest7603> Hi, Im getting a whole bunch of moc issues during a build: | /scratch/jaewon/DAILYBUILD/build/tmp/work/aarch64-xilinx-linux/qtdeclarative/5.9.4+gitAUTOINC+317908e72a-r0/git/tests/benchmarks/qml/binding/tst_binding.cpp:175:10: fatal error: tst_binding.moc: No such file or directory |  #include "tst_binding.moc" |           ^~~~~~~~~~~~~~~~~ | compilation terminated. | make[4]: *** [.obj/tst_binding.o] Error 1 | make[4]: *** Waiting 
Feb 24 00:14:50 <Guest7603> the moc file it cant find is there when I check, and Im seeing similar issues for qtdeclarative, qtxmlpatterns, etc, any ideas?
Feb 24 02:49:54 <armpit> halstead, what me to wait for your test build to complete before launching a build ?
Feb 24 02:50:28 <halstead> armpit, Nah. I think we can kill the build in progress.
Feb 24 02:50:31 <halstead> One moment.
Feb 24 02:50:47 <armpit> k
**** ENDING LOGGING AT Sat Feb 24 03:00:00 2018