**** BEGIN LOGGING AT Fri Dec 21 03:00:02 2018
Dec 21 04:13:31 <khem> RP: here is a fix http://git.openembedded.org/openembedded-core-contrib/commit/?h=yoe/mut&id=cb277f4d57f927f8d03040a6a302098cbc296001
Dec 21 05:44:17 <yocti> New news from stackoverflow: Getting Build Error in Yocto Build system <https://stackoverflow.com/questions/53879420/getting-build-error-in-yocto-build-system>
Dec 21 07:32:57 <RP> khem: good find! :)
Dec 21 08:13:41 <kroon> bluelightning: Hi Paul. I'm wondering about buildhistory.bbclass. Sometimes I see unnecessary git diff churn in the "latest_srcrev" files, where the lines "# SRCREV_machine = ..." and "SRCREV_machine = ..." just moves around randomly(content is identical), which I'm guessing is because of how python iterates over dictionaries in memory. Any chance we can make that more deterministic ?
Dec 21 08:23:52 <RP> kroon: sounds like a missing sort() somewhere
Dec 21 08:24:54 <kroon> RP, yeah.. If I knew how to reproduce it I could try and implement some fix, but I'm not entirely sure how to do that
Dec 21 08:25:22 <kroon> I've seen if for linux-yocto recipe, at least
Dec 21 08:28:34 <kroon> Since it has multiple SRCREV_*
Dec 21 08:40:03 <ejoerns> Hi, when using rm_work image tasks (e.g. do_rootfs) seem to be rebuild unconditionally. I just noticed that rm_work removes configure.sstate files, etc. but I am not sure if this actually causes the rebuild or if something else in sstate handling is broken. Any ideas what could go wrong? I'm testing on thud btw.
Dec 21 08:46:45 <RP> kroon: find the piece of code writing those lines and it may be obvious
Dec 21 08:48:32 <kroon> RP, yeah, I think I know where it is, and I can reproduce it by rebuilding cross-localedef-native a couple of times
Dec 21 08:52:27 <RP> kroon: if you're unsure send an RFC patch and Paul/I can check
Dec 21 08:53:07 <kroon> RP, will do. buildhistory.bbclass line 899, "srcrevs.items()"
Dec 21 08:54:37 <RP> kroon: I'm about to go afk but that sounds right
Dec 21 08:54:58 <RP> ironically python 3.8 may go back to being sorted by default
Dec 21 08:55:16 <kroon> RP, really... geez.
Dec 21 09:07:07 <kroon> RP, patch sent to ml, seems to do the trick here
Dec 21 09:29:22 <ernstp> argh, still being hit by https://bugzilla.yoctoproject.org/show_bug.cgi?id=12107 every now and then...
Dec 21 09:29:22 <yocti> Bug 12107: normal, Medium, 2.7, JPEWhacker, NEW , useradd-staticids: groupadd: GID already exists
Dec 21 10:08:29 <Fedora19> Hello @all,
Dec 21 10:09:43 <Fedora19> In my project I added meta-nodejs layer to be able to have nodejs
Dec 21 10:10:26 <Fedora19> I ran the command bitbake -c addto_recipe_sysroot nodejs-native
Dec 21 10:10:59 <Fedora19> but bitbake wont compile nodejs
Dec 21 10:11:30 <Fedora19> and it stuck all of my bitbake commands, how can I remove nodesj-native from the sysroot recipe ?
Dec 21 10:11:31 <LetoThe2nd> Fedora19: meta-nodejs is massively outdated, we're having suport for it in meta-oe since a couple of releases now. so i'd suggest to use that
Dec 21 10:12:17 <LetoThe2nd> plus the command sounds pretty pointless, but i might be mistaken there.
Dec 21 10:12:19 <Fedora19> LetoThe2nd: I'm in Yocto Pyro BTW
Dec 21 10:13:18 <LetoThe2nd> Fedora19: here you go: http://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-devtools/nodejs?h=pyro
Dec 21 10:13:41 <LetoThe2nd> if you need something more recent i'd suggest to backport it in a custom layer
Dec 21 10:14:52 <Fedora19> Ok thanks, do you know any way to remove the nodejs-native recipe from sysroot-recipe ?
Dec 21 10:15:40 <Fedora19> I will now use the pyro integrated nodejs recipe ! ^^
Dec 21 10:16:17 <LetoThe2nd> why would one want to explicitly remove it?
Dec 21 10:19:14 <Fedora19> Because after I add it through meta-nodejs layer, and add it to the sysroot-recipe, bitbake stucks at nodejs compilation and fails everytime i ran bitbake command !
Dec 21 10:19:35 <LetoThe2nd> why do you add it to the sysroot recpe?
Dec 21 10:19:50 <LetoThe2nd> this sounds all very fishy. what are you ACTUALLY trying to do?
Dec 21 10:25:17 <Fedora19> All I wanted to do was to create recipe using recipetool for a web app built by nodejs and fetch from a gitlab repository. But recipetool fails because nodejs was not present in layers, so I get meta-nodejs layer.
Dec 21 10:26:23 <LetoThe2nd> ok. so. step #1: get rid off whatever you did. step #2: add the meta-oe layer to your build. step #3: try adding the recipe again.
Dec 21 10:28:55 <LetoThe2nd> whenever you start explicitly modifying things like the sysroots explicitly, thats an almost sure sign that you went wrong somewhere.
Dec 21 10:37:02 <Fedora19> Yes, I think I followed the wrong tutorial ! But thanks to you for the help
Dec 21 10:39:42 <rburton> Fedora19: just delete tmp and let bitbake rebuild.  if you want something in the sysroot for building, add it to DEPENDS.
Dec 21 10:44:44 <Fedora19> I get this error when I use recipetool to generate my recipe based on npm: "ERROR: npm required to process specified source, but npm is not available - you need to run bitbake -c addto_recipe_sysroot nodejs-native first"
Dec 21 10:45:36 <rburton> well there you go, haven't seen that for a long time
Dec 21 10:47:09 * LetoThe2nd thinks that recipetool is probably not the way to go here
Dec 21 10:47:44 <LetoThe2nd> rather proper recipe scripting, and will probably need DEPENDS="nodejs-native"
Dec 21 10:50:27 <rburton> well recipetool probably know its a npm recipe but needs node available now to probe it
Dec 21 10:53:21 <LetoThe2nd> yeah
Dec 21 10:57:37 <Fedora19> Ok, it seems to work using nodejs on meta-oe layer ! ^^
Dec 21 12:08:26 <ak77> bblayers resides in build/conf, so it should not be commited, but when `repo sync` brings new layers they should be added somehow.... can I include/require some commited file to add default layers ? (bblayers template is not sufficient solution, once you already have build dir)
Dec 21 13:15:40 <yocti> New news from stackoverflow: How to find which Yocto Project recipe populates a particular file on an image root filesystem <https://stackoverflow.com/questions/42258323/how-to-find-which-yocto-project-recipe-populates-a-particular-file-on-an-image-r>
Dec 21 13:30:19 <varjag> i'm trying to make an autotools based recipe/application build with libpulse
Dec 21 13:30:36 <varjag> however it doesn't find the header files on build stage
Dec 21 13:31:33 <varjag> the headers are there in sysroots_components dir of pulseaudio
Dec 21 13:33:13 <varjag> should i do something special in Makefile.am?
Dec 21 13:35:42 <varjag> or should pulseaudio bb be modified to stage include files somehow?
Dec 21 13:36:09 <varjag> there have to be other projects that link to libpulse, no
Dec 21 13:45:38 <rburton> varjag: did you depend on pulseaudio?
Dec 21 13:49:40 <varjag> oh.. you mean a dependency in my .bb?
Dec 21 13:50:39 <varjag> jesus
Dec 21 13:53:26 <varjag> i'm so dumb
Dec 21 13:53:31 <varjag> rburton: thank you!
Dec 21 15:08:32 <NeilS> hey, I'm doing a clean build of our Krogoth based system and this is specific to my machine but bitbake has been stuck on do_install for ca-certificates-native-20160104-r0 since last night
Dec 21 15:09:08 <NeilS> a bunch of us got new machines and everyones system bitbake build was fine. Mine always gets stuck on this one package.
Dec 21 15:26:04 <NeilS> is there a way I can see what is happening when do_install is running
Dec 21 15:26:16 <NeilS> -DDD only says do_install started
Dec 21 15:27:56 <neverpanic> NeilS: Look at log.do_install in ${WORKDIR}/temp
Dec 21 15:36:49 <NeilS> so it just seems stuck on Updating certificates in /home/user/code/yocto/ct_meta-boot2qt/build-controltech-var-som-mx6/tmp/work/x86_64-linux/ca-certificates-native/20160104-r0/image/home/user/code/yocto/ct_meta-boot2qt/build-controltech-var-som-mx6/tmp/sysroots/x86_64-linux/etc/ssl/certs...
Dec 21 15:36:58 <NeilS> that is the last line in the log
Dec 21 15:39:58 <NeilS> there's quite a bunch of files in there already.. weird feels like it's done but it isn't
Dec 21 16:17:19 <NeilS> anything else i can check?
Dec 21 16:46:24 <yocti> New news from stackoverflow: Poky-sumo : nothing provides kernel-module-hello... error <https://stackoverflow.com/questions/53888201/poky-sumo-nothing-provides-kernel-module-hello-error>
Dec 21 20:03:27 <xthunderheartx> Little help appreciated here. Created a recipe last spring for dbus-cxx.
Dec 21 20:03:45 <xthunderheartx> Got it working at the time on Morty
Dec 21 20:04:05 <xthunderheartx> But trying to build again with rocko fails in do config
Dec 21 20:04:46 <xthunderheartx> I can run the config and build natively on a linux host
Dec 21 20:05:21 <xthunderheartx> But bitbake fails to find two dependancies
Dec 21 20:05:56 <xthunderheartx> These dependancies exist (they were fetched)
Dec 21 20:06:21 <xthunderheartx> Though the don't look like they were ever configured
Dec 21 20:06:47 <xthunderheartx> Even though I have a DEPENDS line containing them.
Dec 21 20:07:32 <xthunderheartx> I thought that forced them to be built and installed in the sysroot first, before my recipe was configured.
Dec 21 20:09:35 <xthunderheartx> If I cd down into the working directory and call configure directly it fails saying the dependencies are missing.
Dec 21 20:11:57 <xthunderheartx> The from configure for the native build (which works) looks slightly different what I get when I invoke it in the yocto build environment, but pretty close.
Dec 21 20:12:21 <xthunderheartx> I've been pulling my hair out on this all day.
Dec 21 20:13:44 <xthunderheartx> First, is there a way to see what state a recipe is in after bitbake abends?
Dec 21 20:14:37 <xthunderheartx> Can one acertain if the recipe has completed do_configure' for instance
Dec 21 20:15:39 <xthunderheartx> Also, how does the configure script know what versions of a dependent to check for?
Dec 21 20:15:53 <xthunderheartx> Any help would be appreciated.
Dec 21 20:18:49 <xthunderheartx> OMG - that was so incoherant
Dec 21 22:05:07 <no_such_user> Heya, anyone doing Docker builds? Is there a standard CROPS image I can just pull for Ubuntu 12.04 / 10.04 for testing some geriatric builds or do I have to roll my own?
Dec 21 22:05:38 <no_such_user> i.e I cant find one via Docker Hub and have had a search and cant see one either
Dec 22 02:23:06 <khem> no_such_user: we use debian for Yoe distribution
Dec 22 02:23:19 <khem> https://github.com/YoeDistro/yoe-distro
Dec 22 02:27:32 <khem> no_such_user: we use debian, jessie and stretch
Dec 22 02:28:05 <khem> ubuntu 10.04 probably is out of bounds
**** ENDING LOGGING AT Sat Dec 22 03:00:02 2018