**** BEGIN LOGGING AT Mon Apr 02 03:00:03 2018 Apr 02 05:25:28 Where is the configuration file stored in Yocto. So I can check whether the bootloader is either grub or uboot Apr 02 05:33:10 I am getting the following error: ERROR: Nothing PROVIDES 'u-boot-fw-utils' (but /home/jamal/Yocto/poky/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb DEPENDS on or otherwise requires it) When I compile for Intel Board, all the repos are master branch Apr 02 05:38:14 New news from stackoverflow: Is there any .config file in Yocto similar to buildroot Apr 02 08:30:55 what parameter defines the arrangement of layers in conf/bblayers.conf ?? for example a layer should be parsed after oe-core layer, but it is place before oe-core in BBLAYERS. I tried to make it dependent on "core" but arrangement of layers is same Apr 02 10:09:00 New news from stackoverflow: Steps for using swupdate in Yocto Project Apr 02 12:01:02 Are there instructions for using https://github.com/schnitzeltony/meta-qt5-extra somewhere? Apr 02 12:01:07 I get qmake errors Apr 02 12:39:52 hello :) Apr 02 12:40:30 is there a way to get commit hash of the package but not parsing the package recipe? Apr 02 13:31:21 zloy: that question doesn't really make sense I'm afraid Apr 02 14:59:54 RP, rocko-next fyi, those sec passed build over the weekend Apr 02 15:01:53 * armpit sign.. what it is the point in backporting and running builds when stuff just ends up in *-next Apr 02 15:03:31 * armpit lots of wasted time Apr 02 15:13:13 "alright--looks like everything's set up. i'll just set off this build and it'll finish over the weekend" i come back on monday: 2 errors Build time: 00:00:13 Apr 02 15:35:34 RP, what should I make my pull request from pyro or pyro-next? Apr 02 15:55:40 armpit: is pyro-next ready to merge? Apr 02 15:56:13 armpit: you didn't waste time as those patches needed testing. We now know they work Apr 02 15:56:37 armpit: I just put them there so they didn't get forgotten as a reminder to me that they needed testing Apr 02 16:04:42 yes stable/pyro-next can be merged. it was rebased against pyro-next Apr 02 16:05:09 so its the last 4 commits Apr 02 16:05:52 armpit: rocko is ok too? Apr 02 16:06:02 yes Apr 02 16:06:15 both ran clean this weekend Apr 02 16:06:30 armpit: great, that helps a lot, thanks! Apr 02 16:07:31 armpit: just saw the email, thanks! Apr 02 16:08:40 armpit: any further idea what was up with morty? Apr 02 16:11:50 no.. I am integrating the "fixup" changes into the appropriate backport and testing to see which one is causing the issue. Apr 02 16:12:38 I just remembered morty is "smart" based Apr 02 16:12:57 armpit: right, this is the challenge, making this work under smart :( Apr 02 16:18:59 how can i make a recipe to drop 3rd party binary files on the rfs and make it ignore all qa checks and dependancy related checks Apr 02 16:30:45 * armpit cool 4.16 is out, 4.15 should be out soon Apr 02 16:31:31 * armpit time to move my kernels Apr 02 16:34:55 rozachar: a good place to start: https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries Apr 02 16:45:26 rozachar: and you can use INHIBIT_DEFAULT_DEPS for the latter part of your question: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-INHIBIT_DEFAULT_DEPS Apr 02 17:52:33 armpit: 4.16 is released on 1/4 be careful :) Apr 02 17:57:16 I would also expect 4.16 to have many more easter eggs that usual Apr 02 18:07:34 gcc is becoming more like my mom https://developers.redhat.com/blog/2018/03/15/gcc-8-usability-improvements/ Apr 02 18:08:24 which is good. I think AI/ML should be next step for compilers, where they can autocorrect the intention of developers in code on fly Apr 02 18:09:10 we might only need one liner DWIM ( Do what I mean ) Apr 02 18:11:10 ~:) Apr 02 18:12:00 khem: nice Apr 02 18:20:43 * armpit why is it when I see the pkg lowpan I think of "Big trouble in Little China movie??" Apr 02 19:02:04 laplante_, thanks - I also needed to add SKIP_FILEDEPS_ and EXCLUDE_FROM_SHLIBS , but it now seems to work Apr 02 20:12:01 khem: cool Apr 02 21:21:06 hello Apr 02 21:22:22 i am trying to execute some bitbake thing in the google container builder. unfortunately after the setup-env, the cmd "bitbake " output "ERROR: Unable to start bitbake server" and stop Apr 02 21:22:49 it works localy. by any chance, does someone know something about this? Apr 02 21:30:16 even with bitbake -DD there is not more error msg Apr 02 21:35:42 hastake: maybe a missing host package? Apr 02 21:35:56 https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#packages Apr 02 21:52:35 clsulliv: unfortunalty no, i checked that the package are installed in the building image Apr 02 21:53:16 it seems to be generated by that https://github.com/openembedded/bitbake/blob/master/lib/bb/server/process.py#L404 line Apr 02 21:54:18 what are the network requirements of this bitbake server? Apr 02 22:12:09 seebs: good news, pseudo master is looking much happier in a test build. Not completed yet but looking good Apr 02 22:12:55 seebs: thanks! :) Apr 02 22:30:32 how do i go about eliminating this error? Apr 02 22:30:39 . /home/user/poky/_toaster_clones/_https___git.yoctoproject.org_git_meta-freescale_rocko/recipes-graphics/wayland/weston_2.0.0.bbappend Apr 02 22:30:48 i have no idea what wayland or weston are Apr 02 22:31:15 i need to give it something, but i don't know how to go about getting what it's looking for Apr 02 22:32:05 is there a way to remove whatever feature it's trying to make so the error will go away? Apr 02 22:34:22 AbleBacon: wayland is a DISRTO_FEATURE IIRC Apr 02 22:34:35 AbleBacon: you may remove it but idk if its actually what you want Apr 02 22:34:48 AbleBacon: what was the actual error that was shown Apr 02 22:35:05 oh, i'm using toaster so that's all i could see of it Apr 02 22:35:51 AbleBacon: Im sure theres a way to see that on toaster I just dont remember Apr 02 22:36:25 well, i did the "DISTRO_remove" thing or whatever it was so it's gone now Apr 02 23:21:19 something called "quilt" is just kicking my ass... ugh Apr 02 23:21:25 killing every build no matter what i try Apr 02 23:22:23 yay, glad it's working better. Apr 02 23:22:53 i think the path code may be slightly cleaner/faster now, in general. **** ENDING LOGGING AT Tue Apr 03 03:00:01 2018