**** BEGIN LOGGING AT Fri Feb 09 03:00:02 2018
Feb 09 09:53:22 <Samoud> Hello !
Feb 09 09:54:01 <Samoud> How can I add the getconf command to my image ?
Feb 09 10:29:09 <mcfrisk> how strict is the kernel version requirement of poky? Can a new 4.14 based linux-libc-headers be used to bootstrap gcc and glibc compilations and still fall back to an older 4.1/4.4 or 4.9 kernel version for actual target?
Feb 09 10:49:10 <RP> mcfrisk: yes, that is fine
Feb 09 11:02:01 <mcfrisk> RP: thanks!
Feb 09 11:22:21 <jaeckel> I'm on the latest krogoth branch and I can't build because of the same error as reported here https://www.mail-archive.com/yocto@yoctoproject.org/msg31427.html (I'm not using the meta-udoo layer and none of my layers included seems to touch the db recipe) does someone know how to fix that?
Feb 09 11:22:22 <RP> rburton: https://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/1292/steps/RunConfig/logs/stdio ahhrgg :/
Feb 09 11:23:31 <rburton> DAMNIT
Feb 09 11:23:41 <rburton> we haven't seen that for months
Feb 09 11:24:33 <RP> rburton: indeed :(
Feb 09 11:40:16 <yocti> New news from stackoverflow: Yocto image : getconf not found <https://stackoverflow.com/questions/48704826/yocto-image-getconf-not-found>
Feb 09 12:23:04 <luneff> hey guys! is there a simple way to reserve a little more space for raspberry sdimg wic class? I need 500 more megs on rootfs, but it get almost no free space :-(
Feb 09 12:27:29 <luneff> hope IMAGE_ROOTFS_EXTRA_SPACE will work
Feb 09 12:50:32 <samoud> Hello everyeone
Feb 09 12:57:59 <rburton> luneff: that's exactly what its for
Feb 09 12:58:11 <rburton> samoud: answered your getconf thing on stackoverflow
Feb 09 12:58:33 <samoud> Hello @rburton I saw it
Feb 09 12:58:42 <samoud> but I get an error when trying to build it
Feb 09 12:59:11 <luneff> yeah, worked. also, I think that meta-raspberrypi sdclass needs xz -T 0 for image compression; better use all available cores
Feb 09 12:59:12 <rburton> you don't need to build it, its part of glibc so built already
Feb 09 12:59:19 <rburton> just add it to your image
Feb 09 13:00:32 <samoud> IMAGE_INSTALL_append += " glibc"
Feb 09 13:00:44 <samoud> it's what I did
Feb 09 13:00:44 <rburton> IMAGE_INSTALL_append = " glibc-utils"
Feb 09 13:00:48 <rburton> as i said, the package is called glibc-utils
Feb 09 13:10:00 <samoud> it's what I did
Feb 09 13:10:37 <samoud> But still get this error
Feb 09 13:10:40 <samoud> | make[1]: *** [all-bfd] Error 2 | make[1]: Leaving directory '/mnt/data/resin-wpe/base-image/build/tmp-glibc/work/x86_64-linux/binutils-native/2.29-r0/git/build.x86_64-linux.x86_64-linux' | Makefile:849: recipe for target 'all' failed | make: *** [all] Error 2 | ERROR: oe_runmake failed
Feb 09 13:11:19 <samoud> with bitbake
Feb 09 13:55:45 <parthi> Where will be sysroot files stored in yocto? I want to use it for my manual compilation.
Feb 09 14:10:48 <yocti> New news from stackoverflow: Add a module/library to meta-toolchain-qt5 sdk <https://stackoverflow.com/questions/48707520/add-a-module-library-to-meta-toolchain-qt5-sdk>
Feb 09 14:11:09 <rburton> samoud: how on earth did you build an image if binutils-native is failing to build?
Feb 09 14:18:22 <RP> rburton: binutils-native is only used for libbfd iirc
Feb 09 14:26:27 <samoud> what i'm missing ?
Feb 09 14:41:40 * fray notes apparently there was a cat on the keyboard somewhere over night
Feb 09 14:44:28 <RP> samoud: there is probably more of an error further back in that log.
Feb 09 15:01:18 * moto-timo lol @ fray
Feb 09 15:03:12 <kanavin> fray: there's cat protection software to help with that, but I can't remember off the top of my head if it's also easily available in common linux distros
Feb 09 15:03:53 <fray> The cat does not usually do that.. she doesn't come into my office when I'm not here..
Feb 09 15:04:07 <fray> my daughter is visiting with her dog, so I'm guessing that was the deviation
Feb 09 15:04:20 <kanavin> yeah, they tend to be interested in keyboards only when someone is typing on them
Feb 09 15:05:05 <fray> depending on her mood, she will often sit on my lap while I type.. at least for a while..
Feb 09 15:05:25 <fray> the other cat (that routinely comes into my office) just wants to be pet (on the ground) or snore while I'm on conferecne calls
Feb 09 15:05:47 <fray> he usually curls up to my dog who is also snoring.. and they make a nice racket while I'm trying to talk
Feb 09 15:06:32 <fray> (I've got 4 cats and 2 dogs..  daughter has 1 dog and one boyfriend....)
Feb 09 15:07:58 <kanavin> fray: https://www.youtube.com/watch?v=s13dLaTIHSg
Feb 09 15:08:13 <RP> fray: I'm now picturing the boyfriend in the dog basket :)
Feb 09 15:09:18 <fray> kanavin that looks like the cat that doesn't want to be picked up.. only he doesn't 'kneed' on the furnature (thank god)
Feb 09 15:09:32 <fray> RP, wouldn't be surprised if that happened and the dog got the bed
Feb 09 15:45:22 <xthunderheartx> I've been rebuilding/redeploying my sdk every time I add a package that I want to develop against.
Feb 09 15:45:37 <xthunderheartx> That seems way overkill
Feb 09 15:46:01 <xthunderheartx> Is there a simpler way to add libs/headers to the host sysroot?
Feb 09 15:46:31 <moto-timo> are you using eSDK or just normal SDK?
Feb 09 15:46:51 <xthunderheartx> The older one. SDK
Feb 09 15:47:41 <moto-timo> eSDK was created for this situation, although you would still be rebuilding it, but the deploy would be more like a package feed
Feb 09 15:48:14 <moto-timo> yes an eSDK is large, but the deltas should not be
Feb 09 15:49:02 <xthunderheartx> Well I've just been doing a bitbake -c populate_sdk etc. Is it just a matter of building a different target for the eSDK?
Feb 09 15:49:14 <xthunderheartx> I on morty
Feb 09 15:56:41 <moto-timo> Henry Bruce's talk from ELC 2017: https://www.youtube.com/watch?v=d3xanDJuXRA
Feb 09 15:57:06 <moto-timo> are you frozen on morty or can you update? major improvements in pyro
Feb 09 15:59:25 <xthunderheartx> Stuck with morty because of FIPS certification.  Well really it's tied to the kernel/openSSL/toolchain
Feb 09 15:59:38 <moto-timo> oh FIPS
Feb 09 15:59:40 <moto-timo> sorry
Feb 09 15:59:47 <xthunderheartx> LOL! Me too!
Feb 09 16:00:14 <moto-timo> trying to jog my memory on the command line, #bearwithme
Feb 09 16:00:19 <xthunderheartx> Thanx for the tip ... I looking into the eSDK now ...
Feb 09 16:00:35 <xthunderheartx> comes down to devtool right?
Feb 09 16:00:49 <moto-timo> sadly, I do not use eSDK daily and so I get rusty on this quickly
Feb 09 16:00:53 <moto-timo> more or less, yes
Feb 09 16:00:59 <xthunderheartx> Kool.
Feb 09 16:01:12 <moto-timo> the devtool in eSDK is slightly different than bitbake context, but similar concepts
Feb 09 16:03:55 <moto-timo> bitbake -c populate_sdk_ext
Feb 09 16:04:41 <moto-timo> so actually, the most important changes were in krogoth, so you are in good shape on morty
Feb 09 16:11:16 <xthunderheartx> Yeah buddy! Awesome. Thx again for the help.
Feb 09 16:24:31 <moto-timo> happy to help
Feb 09 16:25:00 <moto-timo> maybe write something on the YP wiki if you get a chance to explain what works for you
Feb 09 16:25:15 <moto-timo> or the mailing lists
Feb 09 16:27:40 <moto-timo> we need more real world stories to get out there
Feb 09 16:29:51 <hastake> hello
Feb 09 16:36:17 <hastake> i just started a small yocto project with layers from poky/openembedded and the board vendor, and when trying to build a image with no DISTRO_FEATURES and nearly no IMAGE_INSTALL (base-file, base-passwd, busybox, sysvinit), the build process still pull lots of stuff like X11 libs and alsa
Feb 09 16:37:02 <hastake> is it really required to build all these packages everytime?
Feb 09 16:37:38 <rburton> hastake: actually no DISTRO_FEATURES will refuse to build in glibc
Feb 09 16:37:54 <rburton> so you're probab;y using the default DISTRO_FEATURES,which includes x11 pulseaudio etc
Feb 09 16:38:53 <hastake> how can i check that?
Feb 09 16:39:11 <rburton> well, where and how did you set "no DISTRO_FEATURES"
Feb 09 16:39:15 <rburton> as there's a fully-featured default
Feb 09 16:39:17 <hastake> (i really have DISTRO_FEATURES="" in my bb target)
Feb 09 16:39:24 <rburton> oh in a recipe, that' won't work
Feb 09 16:39:37 <hastake> ahah ok
Feb 09 16:39:37 <rburton> it would be specific to the image and so everything else won't know
Feb 09 16:39:54 <rburton> don't set it to ="" because it will break so dramatically.
Feb 09 16:40:57 <rburton> distro/include/default-distrovars.inc is where the defaults are assigned.  if you want a really trimmed form just assign your own DISTRO_FEATURES using eg DISTRO_FEATURES_LIBC and anything else you want enabled
Feb 09 16:41:19 <yocti> New news from stackoverflow: Bitbake the latest Gstreamer in Yocto Morty <https://stackoverflow.com/questions/48298913/bitbake-the-latest-gstreamer-in-yocto-morty>
Feb 09 16:41:31 <rburton> (noting that anything in DISTRO_EFATURES_BACKFILL will magically appear unless you set DISTRO_FEATURES_BACKFILL_CONSIDERED)
Feb 09 16:42:39 <hastake> rburton: ok
Feb 09 16:43:35 <hastake> so how can i remove from the build steps the package that are not included in the image?
Feb 09 16:43:46 <rburton> that happens automatically
Feb 09 16:43:48 <rburton> it only builds what it needs
Feb 09 16:46:30 <hastake> what i don't understand is why generating a 80M image that sould only contains a kernel and some base scripts require 50G of space and more than one hour of build time
Feb 09 16:48:01 <hastake> in other words, how can someone can debug its dependancy graph to see which recipe pull what?
Feb 09 16:48:12 <kergoth> at the very least, it has to build a complete toolchain to be able to compile anything.
Feb 09 16:48:29 <kergoth> bitbake -g is what you want
Feb 09 16:49:04 <hastake> yeah, tried that
Feb 09 16:50:06 <hastake> my target is pulling 157 deps that are clearly not in the file itself, so i imaging that there is some kind of inheritance/templating going on?
Feb 09 16:50:56 <kergoth> every recipe has default deps unless you set INHIBIT_DEFAULT_DEPS, and possibly more beyond that depneding on what classes you inherit
Feb 09 16:51:52 <hastake> how can someone see what each file is doing actually pulling, implicitly or not?
Feb 09 16:52:18 <kergoth> again, see bitbake -g
Feb 09 16:52:24 <kergoth> and bitbake -e, for that matter
Feb 09 16:54:13 <hastake> excellent
Feb 09 16:54:33 <hastake> kergoth: thx, will analyze that
Feb 09 16:57:02 <kergoth> bitbake -e examines the metadata for either the global config or a given recipe, so you can examine variables like DEPENDS, whereas -g dumps mulutiple dependency graphs in .dot form
Feb 09 16:57:08 <kergoth> see also the recently added oe-depends-dot tool
Feb 09 17:01:17 <kergoth> RP: nicely done on runall, been looking forward to the 'all' variant tasks eventually going away :)
Feb 09 17:01:23 <kergoth> just never got around to messing iwth it
Feb 09 17:01:52 <RP> kergoth: thanks, I'm quite pleased to have rid of it as its horrendous to compute
Feb 09 17:03:17 <RP> kergoth: I'm hoping people enjoy the speedup :)
Feb 09 17:03:29 <kergoth> always do :)
Feb 09 17:16:29 <rburton> kergoth: got some all removals in mut
Feb 09 17:17:24 <rburton> hastake: normally because you forgot to disable something.  pick something which is "obviously" not used and follow it in the dot files to find out why, then find out what you can do to turn it off
Feb 09 19:11:53 <yocti> New news from stackoverflow: Building yocto for a Beaglebone green wireless [closed] <https://stackoverflow.com/questions/46245640/building-yocto-for-a-beaglebone-green-wireless>
Feb 09 19:26:34 <khem> rburton: so make patches cant be backported to 3.81 :( I contacted the author
Feb 09 19:26:46 <khem> but one of them which is small one can be
Feb 09 19:29:37 <xtron> is this right that the local.conf has the higher priority over a recipe configuration ?
Feb 09 19:32:33 <khem> xtron: local.conf is global metadata file you can still use ?= in it to assign something weakly and then use recipe metadata to define it specifically using = say a PACKAGECONFIG or something
Feb 09 19:34:03 <khem> rburton: in your meta-gplv2 setup can you backport just this one patch http://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/make/make/0002-glob-Do-not-assume-glibc-glob-internals.patch and see if it works with glibc 2.27
Feb 09 19:35:38 <xtron> khem: consider local.conf is adding a value in variable like DISTRO_FEATURES and some recipe is doing DISTRO_FEATURES_remove = "value", who will win?
Feb 09 19:36:11 <kergoth> _remove always wins, regardless of when or wher eit's defined
Feb 09 19:40:13 <khem> ah yes _remove
Feb 09 19:40:56 <xtron> kergoth: ok and it shouldn't appear in image build environment -e ?
Feb 09 20:25:05 <dex1983> Hi
Feb 09 20:26:36 <dex1983> Is it possible to build a Image with Docker Support on rock64 Board?
Feb 09 20:36:31 <moto-timo> see meta-virtualization layer for docker
Feb 09 20:36:44 <moto-timo> layers.openembedded.org
Feb 09 20:42:49 <dex1983> Ok
Feb 09 20:43:58 <fmeerkoetter> i am using a rocko based system for an i.mx6
Feb 09 20:44:08 <fmeerkoetter> i try to get the gcc address sanitizer working
Feb 09 20:44:31 <fmeerkoetter> I get /home/fmee/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/7.3.0/real-ld: cannot find libasan_preinit.o: No such file or directory
Feb 09 20:44:38 <fmeerkoetter> and other linker errors.
Feb 09 20:44:49 <fmeerkoetter> linker complains that it cant find -lasan
Feb 09 20:45:36 <fmeerkoetter> from searching around with google i am no longer sure if ASAN is supported on ARM/gcc
Feb 09 20:46:44 <fmeerkoetter> there are hints that ARM/gcc got ASAN support with GCC 4.9
Feb 09 21:05:50 <fmeerkoetter> i also find a gcc-sanitizer package at the layer index
Feb 09 21:06:09 <fmeerkoetter> not sure if i need to add this?
Feb 09 21:26:41 <dex1983> thanks with it I get docker support
Feb 09 21:30:25 <dex1983> ?
**** ENDING LOGGING AT Sat Feb 10 03:00:01 2018