**** BEGIN LOGGING AT Thu Jun 27 02:59:57 2019
Jun 27 07:18:55 <MarcWe> Hi, i have a weston(2.0) error saying   not tagged as supported input device event1  - not using input device '/dev/input/event1'
Jun 27 09:34:14 <LocutusOfBorg> hello guys, I'm tricked with a bad bug in yocto
Jun 27 09:34:15 <LocutusOfBorg> or me
Jun 27 09:34:17 <LocutusOfBorg> not sure
Jun 27 09:34:23 <LocutusOfBorg> I have a recipe called foo_git.bb
Jun 27 09:34:30 <LocutusOfBorg> but the RPM generated is called bar.rpm
Jun 27 09:34:35 <LocutusOfBorg> WTF?
Jun 27 09:34:44 <LocutusOfBorg> I indeed have the libbar installed on the system TBH
Jun 27 09:35:42 <LocutusOfBorg> and the only library installed on the system is libbar.so, the others are installed in a private location
Jun 27 09:35:44 <LocutusOfBorg> is that normal?
Jun 27 09:43:32 <rburton> the debian-renamer will rename a package that contains just a library to be the library name
Jun 27 09:43:52 <rburton> eg zlib.bb generates a libz.rpm
Jun 27 09:53:24 <LocutusOfBorg> seems legit, maybe I should just not run that renamer on my recipe
Jun 27 09:53:39 <bluelightning> there are a few ways of disabling that behaviour if you don't want it
Jun 27 09:54:14 <LocutusOfBorg> something like  runtime_mapping_rename?
Jun 27 09:54:18 <bluelightning> that ought to be in the FAQ but I seem to have missed it out
Jun 27 09:54:28 <bluelightning> have a look at meta/classes/debian.bbclass
Jun 27 09:54:58 <LocutusOfBorg> yes, this is where I was looking :)
Jun 27 09:55:30 <LocutusOfBorg> something like AUTO_LIBNAME_PKGS or DEBIAN_NOAUTONAME_
Jun 27 09:55:36 <bluelightning> right either would work
Jun 27 09:57:00 <LocutusOfBorg> of course moving the library worked like a charm, now I revert and see this autonaming
Jun 27 11:23:31 <kayterina[m]> TCLIBC = "baremetal"   option, what does it mean for the build process?
Jun 27 11:33:46 <RP> kayterina[m]: no C library so its a bare toolchain
**** BEGIN LOGGING AT Thu Jun 27 11:55:06 2019
Jun 27 11:59:28 <mardy> RP: oh, excellent! Thanks!
Jun 27 12:30:27 <tgoodwin> Does anyone have a recommendation on using either the autobuilder or autobuilder2?
Jun 27 12:32:48 <mckoan> tgoodwin: AB2 should be better, RP isn't it?
Jun 27 12:33:38 <tgoodwin> mckoan: I would think, but the wiki page guides you down the path to picking up the first generation and nothing on the autobuilder.yoctoproject.org site is helping me narrow it down.
Jun 27 12:36:58 <RP> tgoodwin: autobuilder2 for sure, autobilder is dead, buildbot eight is dead
Jun 27 12:37:14 <tgoodwin> RP: thanks!
Jun 27 12:37:39 <RP> tgoodwin: http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/commit/?id=1369545f9819537535e4ab6ebeb49e7b173a8366
Jun 27 12:37:49 <RP> tgoodwin: which wiki page are you referring to, we should fix that
Jun 27 12:38:10 <tgoodwin> RP: https://wiki.yoctoproject.org/wiki/The_Yocto_Autobuilder
Jun 27 12:38:36 <RP> tgoodwin: ah, hmm. We should fix that
Jun 27 12:39:22 <mckoan> RP: ;-)
Jun 27 12:39:25 <tgoodwin> Granted, I would see that it's deprecated once I follow that source repo link and opened the readme, but I was just kicking around for possible options.
Jun 27 12:42:09 <RP> tgoodwin: just fixed that page
Jun 27 12:42:10 <tgoodwin> and of course really gotten the hint if I tried to clone it ;-)
Jun 27 12:42:18 <RP> tgoodwin: at least its better anywah
Jun 27 12:43:37 <tgoodwin> :) thanks
Jun 27 12:44:52 <RP> tgoodwin: its easy to forget where pointers exist but that one is rather obvious! :)
Jun 27 12:45:39 <mckoan> page updated https://wiki.yoctoproject.org/wiki/The_Yocto_Autobuilder
Jun 27 12:47:23 <mckoan> thanks tgoodwin to poit it out and RP to clarify
Jun 27 12:47:24 <tgoodwin> We're hoping to use it to expose a baseline poky distro for some of the platforms our customers ask about (mostly Xilinx parts) as well as a yum repo of our packages so they can kick tires a bit sooner than running a build.
Jun 27 13:43:31 <mystictot> Hi, I'm using poky repository to build image.
Jun 27 13:44:34 <mystictot> when I run bitbake core-image-minimal i get this erro ERROR: Layer 'sota' depends on layer 'filesystems-layer', but this layer is not enabled in your configuration
Jun 27 13:45:20 <tgoodwin> mystictot: you need to add that layer to your bblayers.conf file.
Jun 27 13:45:21 <mystictot> I got this error on sumo and master branch and yocto-2.7
Jun 27 13:46:17 <tgoodwin> It looks like that's the meta-openembedded/meta-filesystems layer: https://github.com/openembedded/meta-openembedded/blob/master/meta-filesystems/conf/layer.conf#L8
Jun 27 13:46:27 <tgoodwin> Do you have that one in your environment?
Jun 27 13:50:01 <mystictot> tgoodwin: It was not there
Jun 27 13:50:23 <mystictot> I added it like this BBFILES ?= "filesystems-layer
Jun 27 13:50:33 <mystictot> Shouldn't it be there by default
Jun 27 13:50:48 <mystictot> I mean its not mentioned in official documentation
Jun 27 13:52:21 <tgoodwin> Rather than bbfiles, you would need to add the path to the layer into BBLAYERS (bblayers.conf file).
Jun 27 13:52:53 <tgoodwin> https://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#var-bb-BBLAYERS
Jun 27 14:03:11 <mystictot> tgoodwin: But i'm using poky, should i still need openembedded repo ?.
Jun 27 14:03:19 <zeddii> yup
Jun 27 14:10:45 <mystictot> zeddii: I mean when I use poky shouldn't it handle everything and this is not mentioned on quick start guide. https://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html
Jun 27 14:11:54 <zeddii> they layer you are building is one from the ecosystem. not poky. so no, it can’t possibly have all the layers that other layers from the ecosystem require.
Jun 27 14:12:41 <zeddii> if you are building one of the images mentioned in the quickstart guide, everything will be there.
Jun 27 14:19:56 <mystictot> zeddii: Got it, Thanks a lot for info.
Jun 27 14:46:40 <lukma> Dear all,
Jun 27 14:46:40 <lukma> I do have a strange problem :-)
Jun 27 14:47:21 <lukma> Is it possible to change the gcc-native? (The one which is called by some recipe)?
Jun 27 14:49:18 <lukma> In other words - is there any easy way to check if yocto uses the in-system binary ?
Jun 27 14:49:53 <rburton> lukma: we use host compiler for native
Jun 27 14:51:20 <lukma> rburton: And this is an issue for me
Jun 27 14:51:30 <lukma> My debian has 6.4 as gcc
Jun 27 14:51:48 <lukma> but I need at least 7.2 to get the pacakge working
Jun 27 14:52:06 <rburton> do you have gcc7.2 installed?
Jun 27 14:52:28 <lukma> I thought about a workaround to modify PATH of the termianl in which I run bitbaker
Jun 27 14:52:40 <rburton> horrible
Jun 27 14:52:52 <rburton> set BUILD_CC and friends, see bitbake.conf
Jun 27 14:53:24 <lukma> rburton: horrible solution :-) ? or the "horrible" problem :)
Jun 27 14:53:47 <rburton> your solution is horrible :)  BUILD_CC is the proper solution.
Jun 27 14:54:15 <lukma> rburton: That is why I do first ask :-)  before I "adjust" my production system
Jun 27 14:54:34 <lukma> Ok, I will look for that
Jun 27 14:54:38 <lukma> rburton: Thanks
Jun 27 15:01:11 <bluca> rebasing from sumo to thud, the do_populate_sdk fails to build as target-sdk-provides-dummy conflicts with bash, coreutils, coreutils-dev and a bunch of perl packages
Jun 27 15:01:39 <bluca> has anyone seen that? there was a thread on the same issue on the ML but it went nowhere: https://lists.yoctoproject.org/pipermail/yocto/2019-March/044486.html
Jun 27 15:03:00 <bluca> the commit id mentioned by the first answer is no longer in the repos, and there's no other context
Jun 27 15:25:28 <lukma> rburton: If I don't have the gcc-7/8, then could I use the toolchain produced with bitbake foo-image -c populate_sdk ?
Jun 27 15:25:28 <lukma> Would there be any issue with the "fixed" sysroot patch ?
Jun 27 15:25:47 <yocti> New news from stackoverflow: Yocto apache build: how to enable mod_cgid by default? <https://stackoverflow.com/questions/56793974/yocto-apache-build-how-to-enable-mod-cgid-by-default>
Jun 27 16:14:41 <rburton> lukma: no, but but you use the buildtools tarball we provide
Jun 27 16:16:25 <RP> rburton: that doesn't have gcc in it does it?
Jun 27 16:16:30 <rburton> does it not?
Jun 27 16:16:34 <rburton> maybe it should :)
Jun 27 16:22:00 <RP> rburton: we don't have a gcc nativesdk variant
Jun 27 16:22:07 <RP> we could have easily enough
Jun 27 16:25:57 <yocti> New news from stackoverflow: How can I reference/find the ${PV} of one recipe in another recipe in Yocto/Bitbake? <https://stackoverflow.com/questions/56794981/how-can-i-reference-find-the-pv-of-one-recipe-in-another-recipe-in-yocto-bitb>
Jun 27 16:37:56 <rburton> RP: can you look at ross/binconfig and check that i'm not doing anything really stupid so far
Jun 27 16:38:18 <rburton> still got the rewrite to dump on top of that but i'm trying to pick out the behavioural changes first
Jun 27 17:04:33 <nerdboy> moin
**** ENDING LOGGING AT Fri Jun 28 02:59:57 2019