Thursday, 2015-10-01

*** behanw_ <behanw_!~behanw@2001:470:b26c:0:590b:8246:b5f2:3dcd> has joined #yocto00:02
*** SoylentYellow <SoylentYellow!> has quit IRC00:13
*** Snert_ <Snert_!> has quit IRC00:21
*** Snert_ <Snert_!> has joined #yocto00:22
*** benjamirc <benjamirc!besquive@nat/intel/x-ewxvumpvnxofxwdl> has quit IRC00:23
*** dreyna4529 <dreyna4529!~dreyna@> has quit IRC00:39
*** dreyna4529 <dreyna4529!~dreyna@> has joined #yocto00:39
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto01:07
*** sameo <sameo!~samuel@> has quit IRC01:12
aj_cIs it possible to perform a .incappend as a .bbappend ?01:13
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC01:24
*** mtetreault <mtetreault!> has joined #yocto01:32
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto01:33
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC01:34
*** ryansturmer <ryansturmer!> has joined #yocto01:35
ryansturmerHey folks01:35
ryansturmerI am new to yocto and am trying to patch a recipe for the intel edison.01:35
ryansturmerI am abusing yocto in a way, by building it on archlinux, which is not approved01:36
ryansturmerand the newest GCC won't build ncurses01:36
ryansturmer, although there is a patch, whcih I can apply01:36
mtetreaultI'm having issue building glic2 when running debian 8.2. the error seems to come from libc_pic.os' failed01:37
ryansturmerso my question is, how do I patch a recipe01:37
ryansturmerI can create a layer, right?  And include a bbappend file that points to a patch, if I understand01:37
ryansturmerIf anyone has link to step by step guidance on this, I would be appreciative - I've been looking at the developers guide, and am a little lost.01:38
mtetreaultryansturmer: hi!01:38
mtetreaultryansturmer:  I gues you already when through this doc,
mtetreaultryansturmer: Otherwise, yeah you should be able to create a layer and then create a bbappend file to patch your recipe.01:39
*** ryansturmer <ryansturmer!> has quit IRC01:40
mtetreaultryansturmer: Keep in mind, if you create a new layer you need to includes it in your bblayer file01:40
clopezany easy way/command to print the enabled DISTRO_FEATURES?01:41
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto01:44
*** ryansturmer <ryansturmer!> has joined #yocto01:51
ryansturmerSo the distribution for the intel edison seems to be basically a couple of custom layers, plus a makefile and some scripts that they include to make things a little easier on folks01:59
ryansturmerso in order to create my custom layer, I've made a meta-mylayer directory02:01
ryansturmerwith a conf/layer.conf02:02
ryansturmerand a recipes-core/ncurses02:02
ryansturmerwith the ncurses core containing a ncurses_5.9.bbappend file02:03
ryansturmerand in the main image configuration, I've added the meta-mylayer layer02:03
*** dasabhi <dasabhi!> has quit IRC02:03
mtetreaultryansturmer: What's your questions exactly.02:04
ryansturmerWell my first question is, do those steps sound sane for ading a layer?02:04
ryansturmernext question would be:02:04
ryansturmerFILESEXTRAPATHS_prepend := "${THISDIR}/files:"02:05
ryansturmerSRC_URI += "file://work_around_changed_output_of_GNU_cpp_5.x.patch"02:05
ryansturmerthat's the contents of my bbappend file, does that look on the right track?02:05
mtetreaultI'll start with your second question first. your bb append file seems goos.02:06
mtetreaultFor you first question. I'm not sure what's the difference between the standards yocto release and the edion branch. I would have to verify.02:07
ryansturmer(implied: I have a 'files' directory in my layer that contains the referenced files)02:07
ryansturmerdoes the folder structure of my layer seem sane?02:07
mtetreaulthem, gimme a sec.02:08
mtetreaultI'm not sure to understand the layout of your layer but basicly02:12
mtetreaultyou would normally have in your layer a conf/layers.conf file which kind of dictate where to look for bbappend file02:12
mtetreaultSo let's say you want to bbappend the ncurse recipe. In your layer you would have the following my-layer/recipes-core/ncurse/ncurse_version.bbappend02:13
mtetreaultand your patch could be in the folder named files02:14
mtetreaultmake sense?02:14
ebolton@clopez - try "bitbake -e <image_name> > env.txt"02:31
eboltonthen grep that output file for "DISTRO_FEATURES"02:32
eboltonyou'll have to sift through some garbage, but you should see a section that shows all the operations performed on DISTRO_FEATURES with the final value02:33
ebolton$DISTRO_FEATURES [5 operations]02:33
ebolton#   set? /home/ebolton/yocto/poky/meta-yocto/conf/distro/poky.conf:2002:33
ebolton#   set? /home/ebolton/yocto/poky/meta/conf/distro/include/
ebolton#   set /home/ebolton/yocto/poky/meta/conf/documentation.conf:13902:33
ebolton#     [doc] "The features enabled for the distribution."02:33
ebolton#   set? /home/ebolton/yocto/poky/meta/conf/bitbake.conf:71402:33
ebolton#     ""02:33
ebolton#   append [features_backfill]02:33
ebolton#     " sysvinit"02:33
ebolton# pre-expansion value:02:33
kergothdo not spam the channel.02:33
eboltonsomething like that02:33
kergothuse a pastebin02:33
kergothaj_c: no, you can only append a recipe file, and the append filename is based on the recipe filename. can't append arbitrary files, not .inc, not .conf, not bbclasses02:34
ryansturmerOk well, that's essentially what I have @mtetreault02:42
*** halstead is now known as halstead_02:42
mtetreaultkergoth: Yocto fails building glibc when I'm building with -j 8 but the build succeed when I build glibc alone and then continue building my image. Any idea how I could pin point the issue to patch this and submit a patch to the community?02:42
*** halstead_ is now known as halstead__02:42
*** halstead__ is now known as halstead02:42
mtetreault@ryansturmer: does your patch work?02:42
ryansturmerwell, no02:42
*** staylor <staylor!~staylor@> has joined #yocto02:43
mtetreault@ryansturmer: you should be able to validate if your patch make it to the temp folder. build/tmp/work/(platform)/ncurses/version/02:44
*** ryansturmer <ryansturmer!> has quit IRC02:45
*** halstead is now known as hlstd02:45
*** hlstd is now known as halstead02:45
*** nobu <nobu!~nobu@> has quit IRC02:45
clopezebolton: I ended putting this on a recipe from the image02:51
clopezpython __anonymous() {02:51
clopez  bb.fatal ("DISTRO_FEATURES: %s" %d.getVar('DISTRO_FEATURES', True) )02:51
clopezthat would print the features, a bit hacky.. but not sure if your way is easier02:51
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC02:51
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto02:51
*** mtetreault <mtetreault!> has quit IRC02:52
clopezi wish there were a simpler/standard/non-hacky way of getting this info02:52
kergoththe whole point of bitbake -e is to examine the value of variables02:54
kergoththat's its purpose02:54
*** stwcx <stwcx!> has joined #yocto02:55
*** mtetreault <mtetreault!> has joined #yocto02:56
clopezkergoth: that would be true if you are a machine.. but i'm an human, so i find a bit difficult to parse thousands of lines just to get the value of a variable. I just want to get the value of that variable printed to stdout02:58
*** ryansturmer <ryansturmer!> has joined #yocto02:58
ryansturmerDoes the order in which I add my layer to the IMAGE_INSTALL matter?03:02
ryansturmerAnd 2) Directory-wise, where should my layer's folder be in order to be picked up by the build03:03
ryansturmerI get a03:03
ryansturmerERROR: Nothing RPROVIDES 'meta-mylayer' (but /home/ryansturmer/projects/fering/shopbot/edison/edison-src/meta-intel-edison/meta-intel-edison-distro/recipes-core/images/ RDEPENDS on or otherwise requires it)03:03
kergothIMAGE_INSTALL is a variable that lists binary package names to be installed in your rootfs03:05
kergothputting a layer name there doesn't make much esnse03:06
kergothwhere your layer is doesn't matter as long as it's been added to BBLAYERS in conf/bblayers.conf in your build directory03:06
*** Guest83387 <Guest83387!~quassel@> has quit IRC03:06
*** Jackie <Jackie!~quassel@> has joined #yocto03:06
*** Jackie is now known as Guest9211403:07
ryansturmerah so I'm putting things in the wrong place then03:08
mtetreault@ryansturmer: Aaah that's what you meant by, you put your layer in your image!03:09
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC03:14
*** staylor <staylor!~staylor@> has quit IRC03:15
ryansturmerSo the configuration file that's created in conf/bblayers.conf03:21
ryansturmerhow is that generated?  I mean, that's created by oe-init-build-environment03:22
ryansturmerbut where does the list of layers that go into the build come from?03:22
ryansturmeroooh ooh!03:25
ryansturmerit took it!03:25
ryansturmerbuilding, seems to have absorbed the patch.03:25
ryansturmerYeah it was bailing really early on with the ncurses fail, but seems to have got clear of it.03:28
mtetreault@ryansturmer: you can validate if your patch got applied by looking at the build/tmp/work directory to see the resulting source code03:28
ryansturmerI will do that when (if) this build either completes or fails03:30
mtetreaultOhh, I thought you were done compiling!03:30
ryansturmerNo, the compile failed very early previously03:30
*** staylor <staylor!~staylor@> has joined #yocto03:33
kergothalso you can use bitbake -e <reicpename> to examine the variables and make sure they're set the way you expect them to be set03:38
ryansturmerHere's a question03:40
ryansturmerso a layer is a collection of recipes and metadata03:40
ryansturmerso the layer that defines my intel edison image defines a bunch of recipes for packages to be installed03:41
ryansturmercan another layer specify that one of those recipes NOT be installed03:41
ryansturmercan i override the installation directive of that layer the same way I can modify a recipe with a patch?03:41
kergothlayers don't specify 'installation directives'. generally bsp layers don't do anything to your image at all. adding a layer to your config doesn't magically add its packages to your images, unless they bbappend specific images to alter their IMAGE_INSTALL03:43
ryansturmerwhere does the IMAGE_INSTALL originate then?03:44
kergothI don't understand the question.03:44
kergothit's a variable defined in the image recipe03:44
ryansturmerAnd the image recipe is a part of a layer, correct?03:45
kergoth*you* choose whether to build the image recipe03:45
kergothin your bitbake command03:45
kergothit won't build itself03:45
kergothbut yes, all recipes are part of a layer, that's what a layer is03:45
ryansturmerRight, so my build configuration specifies a list of layers03:46
ryansturmerand in those layers are recipes03:46
ryansturmersome of those recipes are for packages that land in my distribution, ultimately03:46
kergothincluding a layer only makes those recipes available to you to build. nothing is forcing you to build those things, and just adding the layer to your build will not make the recipes they provide build.03:46
kergothif you don't want them built, don't build them.03:47
ryansturmerBut when you build, you build an image03:47
ryansturmerand that image is defined by an image recipe?03:47
kergothan image is just another recipe. if you don't like its contents, either make your own image in your own layer, or append it like you would any other recipe03:48
ryansturmerSo my question is, if I am customizing an image that's defined in a layer03:48
ryansturmerlet's say I've got a distribution like the intel edison, where an image recipe has been defined with a bunch of packages selected (in the image recipe) by appending to IMAGE_INSTALL03:49
kergothIMAGE_INSTALL is just another variable. you can add to it or remove from it in a bbappen dthe same way you would any variable03:49
ryansturmerah ok!03:49
ryansturmerso another layer, defined by me, could strip things out of that IMAGE_INSTALL03:49
kergothremoval can be done either with oe_filter_out (grep the layers for examples) or _remove (i.e. IMAGE_INSTALL_remove = "thing-you-want-removed")03:49
ryansturmerok cool03:50
kergothas it could with any variable in any recipe, yes, generally that's true03:50
ryansturmerthat's it, thanks.  Sorry round about way of getting there.03:50
ryansturmerI'm still learning all the terms03:50
ryansturmerthe documentation is good, but there's SO much03:50
kergothnp, just needed to get on the same page on what was being asked03:50
* kergoth nods03:50
mtetreault@kergoth: Do you know what's the difference between the edison branch and the normals YP branches?03:51
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto03:51
kergothnaming confusion. the intel edison board and the yocto 1.1 edison release are entirely different things03:54
kergoththe edison branch is the stable branch from that old release03:54
mtetreaultooohh! I see that totally confused me out..!03:54
kergothyeah, you're not alone there, others have been confused by that. the release name existed a long time ago, the board is more recent04:00
mtetreaultHaha, I feel better now ;)04:02
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto04:09
mtetreault@kergoth. I got an error building glibc when I'm using -j 8.  So I have to explicitly call bitbake glibc and then I can build my whole image. I'm somehow clueless on where to start looking for the issue. Do you have any recommandation?04:12
kergothfirst, make sure it still happens with master, if you're on a stable or release branch.04:12
kergothbeyond that, probably a race in its buildsystem, how you fix those dependss04:13
*** ryansturmer <ryansturmer!> has quit IRC04:15
mtetreaultdependss? You mean like RDEPENDS, DEPENDS ?04:16
kergothno, i'm saying it depends.04:16
kergothcase by case situation04:16
kergoththere's no quick answer04:16
mtetreaultOhhh okay!04:16
*** ebolton <ebolton!~ebolton@> has quit IRC04:20
*** mtetreault <mtetreault!> has quit IRC04:32
*** [Sno] <[Sno]!> has quit IRC04:40
*** cbzx <cbzx!> has quit IRC04:45
*** staylor <staylor!~staylor@> has quit IRC04:53
*** Jefro <Jefro!> has joined #yocto05:09
*** sudipj <sudipj!~sudipj@> has joined #yocto05:28
*** _taw_ <_taw_!> has joined #yocto05:30
*** _taw_ <_taw_!> has quit IRC05:35
*** Jefro1 <Jefro1!> has joined #yocto05:39
*** Jefro <Jefro!> has quit IRC05:43
*** hamis <hamis!~irfan@> has joined #yocto05:43
*** ebolton <ebolton!> has joined #yocto05:48
*** pohly <pohly!> has joined #yocto05:48
*** frsc <frsc!> has joined #yocto05:53
*** ionte <ionte!> has quit IRC06:00
*** marek__ <marek__!> has joined #yocto06:05
*** [Sno] <[Sno]!> has joined #yocto06:05
*** dreyna4529 <dreyna4529!~dreyna@> has quit IRC06:11
-YoctoAutoBuilder- build #493 of nightly-arm-lsb is complete: Failure [failed Running Sanity Tests] Build details are at
*** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has joined #yocto06:23
*** tobiash <tobiash!> has quit IRC06:26
*** TobSnyder <TobSnyder!> has joined #yocto06:27
*** tobiash <tobiash!> has joined #yocto06:33
*** _taw_ <_taw_!> has joined #yocto06:42
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto06:46
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:49
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto06:54
*** jbrianceau_away is now known as jbrianceau06:55
*** mimeakadug <mimeakadug!6a337518@gateway/web/freenode/ip.> has joined #yocto06:56
*** jku <jku!jku@nat/intel/x-hmbsqzbdbijsdhfu> has joined #yocto07:00
*** jku <jku!jku@nat/intel/x-hmbsqzbdbijsdhfu> has quit IRC07:10
*** jku <jku!jku@nat/intel/x-kjxcucrngwtpvmxp> has joined #yocto07:11
*** egavinc <egavinc!> has quit IRC07:12
*** egavinc <egavinc!> has joined #yocto07:17
*** TobSnyder1 <TobSnyder1!> has joined #yocto07:22
*** TobSnyder <TobSnyder!> has quit IRC07:24
*** sameo <sameo!~samuel@> has joined #yocto07:38
*** mckoan|away is now known as mckoan07:39
mckoangood morning07:39
*** Biliogadafr <Biliogadafr!> has joined #yocto07:42
*** florian <florian!> has joined #yocto07:48
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:48
bluelightningmorning all07:53
*** aime-Pierre <aime-Pierre!> has joined #yocto07:55
*** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC08:00
*** behanw_ <behanw_!~behanw@2001:470:b26c:0:590b:8246:b5f2:3dcd> has quit IRC08:01
*** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto08:04
*** maxin <maxin!~maxin@2001:998:22:0:b19e:ea71:e51c:8455> has joined #yocto08:11
*** behanw_ <behanw_!~behanw@2001:470:b26c:0:590b:8246:b5f2:3dcd> has joined #yocto08:13
*** sjolley1 <sjolley1!~sjolley@> has joined #yocto08:22
*** sjolley <sjolley!~sjolley@> has quit IRC08:22
*** locutus__ is now known as LocutusOfBorg108:34
*** jonathanmaw <jonathanmaw!> has joined #yocto08:36
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-damlzsmmarrlgrbj> has joined #yocto08:43
*** TobSnyder <TobSnyder!> has joined #yocto08:45
*** TobSnyder1 <TobSnyder1!> has quit IRC08:46
*** rburton <rburton!> has joined #yocto08:59
*** ][Sno][ <][Sno][!> has joined #yocto09:01
*** [Sno] <[Sno]!> has quit IRC09:04
*** belen <belen!Adium@nat/intel/x-nfqujvjthpdoqcjh> has joined #yocto09:08
*** rburton <rburton!> has quit IRC09:09
*** sjolley1 <sjolley1!~sjolley@> has quit IRC09:13
*** rburton <rburton!> has joined #yocto09:15
*** rburton1 <rburton1!> has joined #yocto09:27
*** rburton <rburton!> has quit IRC09:29
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC09:41
*** phantoxeD <phantoxeD!> has joined #yocto09:47
*** psnsilva <psnsilva!> has quit IRC09:51
*** psnsilva <psnsilva!> has joined #yocto09:51
*** phantoneD <phantoneD!> has quit IRC09:51
*** aime-Pierre <aime-Pierre!> has quit IRC09:57
*** aime-Pierre <aime-Pierre!~Thunderbi@> has joined #yocto09:57
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-damlzsmmarrlgrbj> has left #yocto10:47
*** Guest92114 <Guest92114!~quassel@> has quit IRC10:58
*** Jackie_huang <Jackie_huang!~quassel@> has joined #yocto11:00
*** hamis <hamis!~irfan@> has quit IRC11:04
*** JaMa <JaMa!> has joined #yocto11:09
*** hamis <hamis!~irfan@> has joined #yocto11:10
*** roric <roric!> has joined #yocto11:12
*** roric <roric!> has quit IRC11:27
*** jjmb <jjmb!> has quit IRC11:29
*** deception <deception!~deception@unaffiliated/deception> has quit IRC11:36
*** deception <deception!~deception@unaffiliated/deception> has joined #yocto11:38
*** sjolley <sjolley!~sjolley@> has joined #yocto11:43
*** tsramos <tsramos!tsramos@nat/intel/x-fjxlxiptwqofuuhj> has joined #yocto11:44
*** sjolley <sjolley!~sjolley@> has quit IRC11:47
*** lpax <lpax!~lpax@> has joined #yocto11:48
*** lpax <lpax!~lpax@unaffiliated/lpax> has joined #yocto11:48
*** sjolley <sjolley!~sjolley@> has joined #yocto11:51
*** lpax <lpax!~lpax@unaffiliated/lpax> has quit IRC11:54
*** hamis <hamis!~irfan@> has quit IRC12:02
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto12:02
*** dreyna4529 <dreyna4529!~dreyna@> has joined #yocto12:07
*** dreyna4529 <dreyna4529!~dreyna@> has quit IRC12:12
*** ryansturmer <ryansturmer!> has joined #yocto12:14
ryansturmeryeah, I didn't know aboutthe branch, that's confusing12:14
ryansturmerthe edison board release is basically the BSP for the intel edison, packaged up with some build scripts12:15
*** dmoseley <dmoseley!> has quit IRC12:18
*** dreyna4529 <dreyna4529!~dreyna@> has joined #yocto12:20
*** lpax <lpax!~lpax@unaffiliated/lpax> has joined #yocto12:28
*** davis <davis!> has quit IRC12:31
*** lpax <lpax!~lpax@unaffiliated/lpax> has quit IRC12:34
clopezafter building a core-image-sato for x86 and running "runqemu qemux86" I get a Xserver with no OpenGL support at all, i have added opengl to distro-features when building12:40
clopezany idea of how to enable opengl support with runqemu?12:41
clopezit seems is not building the vmware kernel driver, but the uvesafb one12:41
clopez(i mean vmwgfx driver)12:42
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto12:48
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto12:53
rburton1qemux86 doesn't support GL12:54
*** mimeakadug <mimeakadug!6a337518@gateway/web/freenode/ip.> has quit IRC12:54
rburton1(presently, patches welcome)12:54
*** ryansturmer <ryansturmer!> has quit IRC12:56
clopezit supports it via gallium/llvmpipe12:59
*** lamego <lamego!~jose@> has joined #yocto13:04
*** hugovs <hugovs!~hugo@> has joined #yocto13:07
*** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has left #yocto13:10
*** IvanSB <IvanSB!> has joined #yocto13:11
*** ryansturmer <ryansturmer!> has joined #yocto13:12
ryansturmerFurther question:13:15
ryansturmerI am doing a build, and one of my recipes has failed.  I have found a patch for it, and wish to apply it,13:15
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC13:17
ryansturmerI have a custom layer, and I've successfully patched other recipes13:17
*** dlan <dlan!~dennis@> has joined #yocto13:17
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto13:17
ryansturmerBut this one (binutils) is complaining at me13:17
ryansturmerooh maybe I've fixed it13:19
*** kscherer <kscherer!~kscherer@> has quit IRC13:21
*** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has joined #yocto13:28
ryansturmerI'm just not sure what to call my bbappend to ensure that it's applied to the recipe I want13:31
ryansturmerI can do bitbake-layers show-recipes and see my recipe names13:31
ryansturmerERROR: No recipes available for:13:34
ryansturmer  /home/ryansturmer/projects/edison/edison-src/meta-mylayer/recipes-devtools/binutils/binutils.bbappend13:34
JaMaadd _<version> or _% (wildchar)13:35
ryansturmerso binutils_%.bbappend ?13:36
JaMayes if you're using recent OE and you want to apply it for all versions of binutils13:36
JaMaedison maybe is too old to support % in filenames13:36
ryansturmerno, seems to have an effect13:37
ryansturmeralthough i mis-named my patch file13:37
ryansturmerand I'm off to the races again!13:38
bluelightningJaMa: I suspect this is for edison the board as opposed to edison the ancient branch ;)13:38
JaMabluelightning: :) ah13:38
ryansturmerman that's confusing13:39
ryansturmerI mean, we all love naming our projects after famous scientists13:39
ryansturmerhell my cat's name is edison13:39
ryansturmerbut we should probably diversify13:39
JaMait would be enough to say which release you're using :)13:39
JaMainstead of me guessing from bbappend path :)13:40
bluelightningwell, in our case the branch/release was named after a character from Day of the Tentacle, and came some years before Edison the board, but yeah ;)13:40
ryansturmerDay of the tentacle!13:42
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-pavktbxxmjczybti> has joined #yocto13:46
ryansturmerOh i am most certainly familiar13:47
ryansturmerand now I want to go play monkey island13:47
ryansturmerso thanks for that.13:47
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC13:53
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC13:56
belen"as they attempt to stop the evil Purple Tentacle—a sentient, disembodied tentacle—from taking over the world" :D14:01
bluelightningbelen: don't knock it, it's a classic :D14:02
belenbluelightning: I wasn't. I just really like the idea of a disembodied, sentient tentacle taking over the world ...14:03
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC14:05
*** roric <roric!> has joined #yocto14:09
*** madisox <madisox!> has joined #yocto14:12
RPbelen: I liked the idea too :D14:14
][Sno][to rebase our local patches for submitting them I rebased all my repo's to master and rebuilt14:15
*** ryansturmer <ryansturmer!> has quit IRC14:16
][Sno][with the gcc5 in master neither my kirkwood (guruplug) nor my imx6 boot's any more14:16
][Sno][any hint how to dig?14:16
*** ryansturmer <ryansturmer!> has joined #yocto14:16
belenRP: but I would like the tentacle to win and take over the world ;)14:16
*** roric <roric!> has quit IRC14:17
RP][Sno][: I know there were some arm kernel gcc5 issues. You could check the linux-yocto branches and see how it was fixed there14:20
RPbelen: that does have a certain appeal :)14:20
][Sno][RP: is something similar known to uboot?14:20
RP][Sno][: I don't know14:20
*** ryansturmer <ryansturmer!> has quit IRC14:22
*** ryansturmer <ryansturmer!> has joined #yocto14:22
][Sno][RP: git logs saying you were directly involved ^^14:22
*** marek__ <marek__!> has quit IRC14:24
*** ryansturmer <ryansturmer!> has quit IRC14:24
*** IvanSB <IvanSB!> has quit IRC14:25
*** alimon <alimon!~alimon@> has joined #yocto14:25
RP][Sno][: how many patches do the git logs say I deal with a month out of interest? I don't remember any specifics of that14:27
*** jku <jku!jku@nat/intel/x-kjxcucrngwtpvmxp> has quit IRC14:27
*** ryansturmer <ryansturmer!> has joined #yocto14:32
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto14:38
*** frsc <frsc!> has quit IRC14:41
][Sno][RP: seems to be a bit wild - cause the patches are across lot's of repos14:44
][Sno][is there an easy way to choose another compiler version for the meantime?14:44
][Sno][yocto ref manual didn't find for "gccversion' or 'gcc version'14:45
JaMa][Sno][: try git grep GCCVERSION14:46
JaMa][Sno][: there is still 4.8 and 4.9 version as explained in RP's commit "tcmode-default: Set gcc 5.2 as the default"14:47
][Sno][cool, thanks14:47
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto14:47
*** nileshkokane <nileshkokane!uid116340@gateway/web/> has joined #yocto14:48
Crofton|work][Sno][, search the kernel commit log for gcc5 and llvm commits14:53
Crofton|workthat's how I solved an older kernel/gcc5 compile issues14:53
][Sno][Crofton|work: compiles are fine, it doesn't boot :/14:54
ryansturmergcc 5 issues are annoying!14:55
JaMaall new stuff is nice but sometimes annoying14:55
ryansturmerIf I go edit a .bb file in my poky directory - I should just be able to re-run the build right?  I don't have to do a "clean" or anything like that?14:55
][Sno][the only one I found related to my issue was 3c1245d162ccb55de1af42bcf3dbf690457bf9e4 in yocto-4.1kernel14:56
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-pavktbxxmjczybti> has left #yocto14:58
aj_c kergoth: then if add another in another layer it will overwrite the first one?14:59
*** aj_c <aj_c!~Alex_Joya@> has quit IRC15:03
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:07
ryansturmerContinuing with my build15:14
ryansturmerI have a recipe that fails: subversion15:14
ryansturmerso if I bitbake my-image - it takes awhile, but ultimately bombs on the subversion recipe in the do_configure step15:14
ryansturmerif I bitbake subversion, though15:14
ryansturmerit seems to build just fine15:14
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto15:16
*** ryansturmer <ryansturmer!> has quit IRC15:16
*** ryansturmer <ryansturmer!> has joined #yocto15:18
*** aj_c <aj_c!~Alex_Joya@> has joined #yocto15:21
ryansturmerShould there be a difference like that?15:25
*** staylor <staylor!> has joined #yocto15:26
JaMaryansturmer: are you running both builds in the same directory?15:30
ryansturmerI'm in the directory that contains /poky and /build15:30
JaMaIIRC last time I've seen similar strange issue when subversion build was failing to regexp replace something in build directory which contained "-D" string15:30
JaMaor something like that15:30
frayodd ball question, does anyone know if qemuarm64 SHOULD let me run arm32 (armv7) binaries?15:31
ryansturmerI source poky/oe-init-build-env15:31
ryansturmerand then bitbake my-image15:31
ryansturmerbitbake subversion15:31
frayI'm trying to figure out if it's a qemu limitation, kernel configuration problem, or something is broken15:31
JaMaisn't it failing in subversion-native or something like that?15:31
rburton1ryansturmer: pastebin with the log in would help15:32
JaMaif you build your image after building subversion, then it shouldn't even try to rebuild subversion15:32
*** staylor <staylor!> has quit IRC15:35
ryansturmergetting logs15:37
*** afxez0r <afxez0r!afxez0r@nat/intel/x-okpbkwdauywgumhv> has joined #yocto15:37
ryansturmerThat's the result of bitbake edison-image15:38
ryansturmerthere's subversion and there's subversion-native15:39
ryansturmer(like you said)15:40
ryansturmerNot sure I understand the difference15:42
ryansturmerit looks like they're using the same source directory and .bb file15:43
*** _taw_ <_taw_!> has quit IRC15:44
*** hanthings <hanthings!> has joined #yocto15:47
ryansturmerI had set CPPFLAGS but not BUILD_CPPFLAGS15:47
ryansturmerso building in the native context was broken15:48
*** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has left #yocto15:53
JaMa1:1, crystal ball rocks today15:54
*** mckoan is now known as mckoan|away15:56
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC15:59
*** nerdboy <nerdboy!> has joined #yocto16:00
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:01
*** aj_c <aj_c!~Alex_Joya@> has quit IRC16:05
*** belen <belen!Adium@nat/intel/x-nfqujvjthpdoqcjh> has quit IRC16:05
*** belen2 <belen2!Adium@nat/intel/x-lbgbopvpjjgnczdu> has joined #yocto16:05
*** ryansturmer <ryansturmer!> has quit IRC16:08
*** maxin1 <maxin1!~maxin@> has joined #yocto16:09
*** maxin <maxin!~maxin@2001:998:22:0:b19e:ea71:e51c:8455> has quit IRC16:11
*** maxin1 <maxin1!~maxin@> has quit IRC16:13
*** aj_c <aj_c!Alex_Joya@nat/intel/x-erhmkmsbxexqzizg> has joined #yocto16:15
*** aj_c <aj_c!Alex_Joya@nat/intel/x-erhmkmsbxexqzizg> has quit IRC16:20
*** ebolton_ <ebolton_!> has joined #yocto16:21
*** ebolton <ebolton!> has quit IRC16:23
*** aj_c <aj_c!Alex_Joya@nat/intel/x-fajxnbqurwatawgg> has joined #yocto16:24
*** dreyna4529 <dreyna4529!~dreyna@> has quit IRC16:24
aj_ccan I overwrite a from other layer?16:24
*** dreyna4529 <dreyna4529!~dreyna@> has joined #yocto16:25
kergothaj_c: yes, if it's in the exact same path relative to the root of the layer, and if your layer is listed in BBLAYERS before the other.16:25
*** ebolton_ <ebolton_!> has quit IRC16:26
*** berton <berton!~fabio@> has joined #yocto16:27
*** aime-Pierre <aime-Pierre!~Thunderbi@> has quit IRC16:30
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC16:36
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:37
*** sameo <sameo!~samuel@> has quit IRC16:40
*** jonathanmaw <jonathanmaw!> has quit IRC16:41
kergothI think there's a real need for PACKAGECONFIG_BACKFILL16:46
*** belen2 <belen2!Adium@nat/intel/x-lbgbopvpjjgnczdu> has quit IRC16:46
fraykergoth, I just noticed somewhere along the line the "IMAGE_GEN_DEBUGFS = '1'" broke..16:46
frayit's generating the debugfs.. but it never packages it16:46
fray(creates teh tarball)16:46
kergothhuh, that's not good, hadn't noticed16:47
frayya.. I have no idea how the tarball is generated any longer except something to do with image.py16:47
*** ebolton <ebolton!~ebolton@> has joined #yocto16:48
frayI can't even find in the commit where the image part of it is.. so it's possible it got dropped in a rebase and was somehow missed16:49
*** behanw_ <behanw_!~behanw@2001:470:b26c:0:590b:8246:b5f2:3dcd> has quit IRC16:49
fraycommit is: 1a6ed48c65f922c66b005aa966d7ee4878ee95e316:50
fraybut that is missing the bit that tarballs it up.. :P16:50
*** ebolton <ebolton!~ebolton@> has quit IRC16:51
kergothit's all IMAGE_NAME based, presumably you could call into oe.image with a different IMAGE_NAME and hardcoded IMAGE_FSTYPES?16:51
frayhopefully I still have an old copy in my poky-contrib16:51
fraythat was my suspicion.. but the problem is I don't have a clue how that part is put together anymore16:52
fraythat is the original patch... but I don't know if the first part even applies.. :P16:53
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:53
*** alimon <alimon!~alimon@> has quit IRC16:54
frayya.. I just verified that first hunk seems to be missing.. :P  I'm going to bring it back and test it.. argh.. can't believe this got missed in prior testing16:55
*** jbrianceau is now known as jbrianceau_away16:55
kergothis there an oe-selftest unit test for debugfs? if not, should probably fix that :)16:56
frayI highly doubt it.. this code was written before oe-selftest.. :P16:57
kergothi really need to do better at testing all the combinations of the bits i add to the mel local.conf.sample16:57
*** alimon <alimon!alimon@nat/intel/x-nczagifuujdjqphj> has joined #yocto17:00
*** raykinsella78 <raykinsella78!~rkinsell@> has joined #yocto17:01
*** sa2ajj <sa2ajj!~quassel@> has joined #yocto17:03
fraykergoth forward porting the old code worked.. :P  only issue is it's a bunch of small changes.. and we're not past branch point ARGH!17:04
frayI think I tracked down the issue.. the version that was merged came from Khem..  and didn't have the image bits in it..17:05
frayand since we (WR) carry our own version.. we ontinued to have the missing image bits and didn't notice in our regular testing it wasn't in oe-core17:06
*** dmoseley <dmoseley!> has joined #yocto17:06
*** cbzx <cbzx!> has joined #yocto17:08
*** aj_c <aj_c!Alex_Joya@nat/intel/x-fajxnbqurwatawgg> has quit IRC17:11
*** ryansturmer <ryansturmer!> has joined #yocto17:13
*** SoylentYellow <SoylentYellow!> has joined #yocto17:19
*** ntl <ntl!> has quit IRC17:21
*** cbzx <cbzx!> has quit IRC17:23
*** TobSnyder <TobSnyder!> has quit IRC17:31
kergothfray: this was a regression, i'd think it'd be appropriate to go in this release, though others might not agree.. also richard did just branch, so we are past the branch point, just the branch and master were probably intended to stay in sync a little longer :)17:32
kergothtotally unrelated, but <3
frayI'm trying to condense down my patch.. :P17:33
kergothemail notifications of new releases for any github repositories you have starred or watched17:33
* kergoth nods17:33
frayI should have somethign testable shortly17:33
*** raykinsella78 <raykinsella78!~rkinsell@> has left #yocto17:34
kergoth looks interesting, wonder how it compares to our setup17:36
*** stwcx <stwcx!> has quit IRC17:38
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC17:44
ryansturmerQA Issue: hostapd-daemon: The compile log indicates that host include and/or library paths were used.17:59
ryansturmerWhat does that mean?18:01
*** clsulliv <clsulliv!~clsulliv@> has joined #yocto18:02
JaMaryansturmer: look to log.do_compile18:02
JaMaand search for grep -e 'CROSS COMPILE Badness:' -e 'is unsafe for cross-compilation'18:03
ryansturmerwell dang how'd that happen :P18:03
ryansturmerit's looking at my host libnl3 library18:04
*** SoylentYellow <SoylentYellow!> has quit IRC18:04
JaMaryansturmer: check configure script what black magic is hard coded there18:04
JaMaryansturmer: the same check is also executed against log.do_install and config.log18:05
*** Crofton <Crofton!> has quit IRC18:05
*** Crofton|work <Crofton|work!> has quit IRC18:05
ryansturmerfound it18:05
ryansturmeryou guys are the best, btw18:05
ryansturmerI've been nothing but noisy today and everyone has been so helpful18:06
*** Biliogadafr <Biliogadafr!> has quit IRC18:13
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:16
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has joined #yocto18:16
*** Crofton <Crofton!~balister@> has joined #yocto18:18
*** Crofton|work <Crofton|work!~balister@> has joined #yocto18:18
*** SoylentYellow <SoylentYellow!> has joined #yocto18:18
ryansturmerSome time ago, I ran across some docs that described a patch workflow for doing OE builds18:20
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has quit IRC18:20
ryansturmerwhere you would build, fail, then go into the source, tinker around, and then rebuild, and at the end, somehow generate a patch recipe automatically18:20
ryansturmerdid I dream that?18:20
*** noisebleed <noisebleed!~quassel@> has joined #yocto18:21
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has joined #yocto18:21
kergothdevtool can facilitate that18:26
ryansturmerthat is the keyword i needed!18:27
ryansturmerthank you, found the docs18:27
fraykergoth -- fix for the debugfs image gen is on the list..18:28
][Sno][RP, otavio & co: meta-java and prereq patches sent via copy&paste format-patch (also for perl and meta-cpan prereqs)18:29
fraysee header, comment and suggest a better way.. I don't like the duplicate code..18:29
][Sno][hope that helps18:29
fraybut this is what I could get working quickly.. (it's cleaner then the 'backport' version I started with for sure)18:29
frayalso, I'd love for you (or someone else) to suggest the right setting in the oeqa to make sure this starts getting built/tested.. ;)18:29
*** nighty-_ <nighty-_!> has joined #yocto18:30
*** stwcx <stwcx!~stwcx@> has joined #yocto18:31
JaMa][Sno][: in addition to comments I've already sent, meta-oe patches belong to openembedded-devel ML, read README files in toplevel directory18:32
*** challinan <challinan!> has quit IRC18:32
][Sno][Yet Another Mailing List to Join :(18:33
*** challinan <challinan!> has joined #yocto18:33
*** pohly <pohly!> has quit IRC18:36
*** tsramos <tsramos!tsramos@nat/intel/x-fjxlxiptwqofuuhj> has quit IRC18:38
*** tsramos <tsramos!tsramos@nat/intel/x-pshdkmwojwysnkem> has joined #yocto18:38
*** SoylentYellow <SoylentYellow!> has quit IRC18:41
*** _taw_ <_taw_!> has joined #yocto18:43
ryansturmerThis is a silly question probably, but should i have devtool as a part of the normal environment created by init-oe-environment script?18:43
*** SoylentYellow <SoylentYellow!> has joined #yocto18:44
][Sno][JaMa: I don't see any comment in my inbox - do you refer a comment from past?18:46
*** dshwang_ <dshwang_!~dshwang@> has quit IRC18:48
kergothryansturmer: yes. it's in poky/scripts or oe-core/scripts along with recipetool and others, and that should be in your PATH after sourcing the setup script. unless your'e on an old release before they were added, they should be there afaik18:48
*** dshwang <dshwang!~dshwang@> has joined #yocto18:49
][Sno][JaMa: thanks, I sent poky patches to poky@, because I've seen a lot there ...18:50
][Sno][JaMa: but I can re-gen the patches and send again to oe-devel@ tomorrow, no problem18:51
JaMaa lot?
JaMathere are only few patches for meta-yocto-bsps there18:51
JaMain whole September18:51
ryansturmerI guess it makes sense that intel would use an older release18:51
][Sno][I didn't clean up my inbox for a long time :(18:52
ryansturmerbut it looks like this scripts directory doesn't contain devtool18:52
][Sno][was very busy getting openjdk working on arm5 ;)18:52
][Sno][sorry for noise18:52
ryansturmerlooks like 1.7.2 poky18:57
bluelightningryansturmer: unfortunately that's one release behind the first where devtool was implemented18:57
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC19:03
*** nileshkokane <nileshkokane!uid116340@gateway/web/> has quit IRC19:03
*** stwcx <stwcx!~stwcx@> has quit IRC19:04
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC19:04
*** ][Sno][ <][Sno][!> has quit IRC19:05
*** Zyend <Zyend!5878ac20@gateway/web/freenode/ip.> has joined #yocto19:09
*** acidfu <acidfu!~nib@> has quit IRC19:13
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto19:13
Zyendhello, anybody who could help me out with a compile error (while building a RaspberryPi image) ?19:16
*** stwcx <stwcx!~stwcx@> has joined #yocto19:20
*** ntl <ntl!> has joined #yocto19:22
*** jchonig <jchonig!> has joined #yocto19:25
ryansturmerWhat's the trouble @Zyend19:25
Zyend@ryan: I'm a newbie in Yocto, I tried to build a tutorial wtih raspberrypi2 and Qt5. The  build failed while compiling libssh with the following error: "error: ISO C does not support '__FUNCTION__' predefined identifier [-Wpedantic] "19:31
ZyendAnd honnestly, i don't know how to get rid of this error within Yocto19:32
ryansturmerWhat host are you using to do your build?19:39
Zyenddebian 7.919:40
ryansturmerand what yocto version/19:40
*** sjolley <sjolley!~sjolley@> has quit IRC19:40
Zyendfido 1.819:42
*** _taw_ <_taw_!> has quit IRC19:42
ryansturmercheck the do_compile log for that package and check for more detail about what's calling the failure19:45
ryansturmerIs deb 7.9 one of the "approved" build environments?  What is your gcc version (gcc --version)19:47
ryansturmerI have run into a lot of errors with newer gcc versions, because of changes in how the compiler interprets warning flags (such as -Wpedantic)19:48
*** rburton <rburton!> has joined #yocto19:48
ryansturmerWhen you run into these, you're pretty much looking at patching the source, or updating the build configuration to suppress warnings that are bubbling up as fatal19:48
ryansturmerIf you're using gcc 5 or newer, it looks like this is a known thing:
*** rburton1 <rburton1!> has quit IRC19:49
*** berton <berton!~fabio@> has quit IRC19:50
Zyendgcc version is gcc version 4.7.2 (Debian 4.7.2-5)19:54
ZyendIt looks like all warnings end up with errors19:54
*** ryansturmer <ryansturmer!> has quit IRC19:55
*** ryansturmer <ryansturmer!> has joined #yocto19:56
ryansturmerOne thing you can do is modify CFLAGS and CPPFLAGS in your local.conf19:58
ryansturmerthat will change things for all builds though19:59
Zyendthe local.conf in the build-xxx/conf/ ?19:59
ryansturmerwhich is not ideal19:59
Zyendhow would you modify these flags in the local.conf ? I mean, the syntax ?20:00
*** JaMa <JaMa!> has quit IRC20:03
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto20:07
*** sjolley <sjolley!sjolley@nat/intel/x-pgmfroaeuxacawop> has joined #yocto20:14
*** ccaione <ccaione!~ccaione@unaffiliated/ccaione> has quit IRC20:15
*** SoylentYellow <SoylentYellow!> has quit IRC20:15
*** ryansturmer <ryansturmer!> has quit IRC20:18
*** pidge <pidge!~pidge@2a02:8084:0:3000:31d1:2cf6:b99e:8e4c> has quit IRC20:19
*** ryansturmer <ryansturmer!> has joined #yocto20:22
*** [Sno] <[Sno]!> has joined #yocto20:23
*** stwcx <stwcx!~stwcx@> has quit IRC20:29
*** SoylentYellow <SoylentYellow!> has joined #yocto20:30
*** hanthings <hanthings!> has quit IRC20:33
*** pidge <pidge!~pidge@2a02:8084:0:3000:94cf:7fca:39b6:1318> has joined #yocto20:39
*** stwcx <stwcx!~stwcx@> has joined #yocto20:42
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:42
*** ccaione <ccaione!~ccaione@unaffiliated/ccaione> has joined #yocto20:46
*** ryansturmer <ryansturmer!> has quit IRC20:50
*** pidge <pidge!~pidge@2a02:8084:0:3000:94cf:7fca:39b6:1318> has quit IRC20:51
*** Zyend <Zyend!5878ac20@gateway/web/freenode/ip.> has quit IRC21:10
sandsmarkhow can I control what is installed in the sysroot where a package is built?21:16
kergoththat question doesn't really make a lot of sense. what do you mean by 'where a package is built'?21:17
*** Guest99735 <Guest99735!> has quit IRC21:19
sandsmarkwell, qt is built in a sysroot of sorts? and that sysroot includes gles3 headers for some weird reason21:19
sandsmarkwhich aren't included in the sysroot in the sdk, so building anything with the sdk fails21:19
kergothno, nothing is built "in a sysroot". there's a shared sysroot in the tmpdir which is used to build everything21:19
sandsmark(because the qt version in the sdk expects that header)21:19
kergothif you need something in it, add whatever that something is to your DEPENDS21:20
sandsmarkwell, I'd rather not have it there21:20
kergothhave what where?21:20
sandsmarkthe gles3 headers21:20
sandsmarkI only use gles221:20
kergothif your build is automatically changing behavior based on the existence of a header, then your build is broken21:20
kergothand needs to be fixed to explicitly disable/enable its dependencies21:20
sandsmarktell that to qt :)21:20
sandsmarkthe qt configure script is stupid21:21
kergoththe qt configure script has tons of arguments you can use to eanble/disable functionality, much like autoconf can21:21
kergothmost likely you're just not passing the ones you need21:21
sandsmarknot really21:21
sandsmarknot for gles, anyways21:21
sandsmarkif you tell it to use gles2, it will use gles3 if it finds the header21:21
kergoththen you'll need to patch it to add arguments to control that behavior, most likely21:22
kergothwe don't use per-recipe sysroots, so you can never guarantee what will or won't be available21:23
sandsmarkindeed, but that's what I was hoping to avoid21:23
kergoththat said, why is gles3 being built in your setup if you don't want it?21:23
kergothtrack down the dep21:23
sandsmarkbecause mesa builds it if I want gles221:23
sandsmarkor, "builds" it, it's just a header21:23
sandsmarkok, might be easier to just install the gles3-header...21:24
*** Hauke <Hauke!~Hauke@2001:41d0:8:b27b::4> has joined #yocto21:25
sandsmarkkergoth: thanks anyhow :)21:29
sandsmarkthings make a bit more sense now21:29
*** Hauke is now known as Hauke121:29
kergothnp. for what its worth, we intend to eventually get per-recipe sysroots to avoid this sort of hting and make the builds more deterministic (sysroot would only include bits from what you depend on), but it's not even scheduled, it's an 'eventually' item21:29
*** Hauke1 is now known as hauke221:29
*** hauke2 is now known as Hauke_away21:31
sandsmarkwell, it would be nice, but I guess it has some overhead, and is pretty complex to get right21:31
*** Hauke_away is now known as Hauke21:31
kergothyeah. ideally it'd use symlink trees or copy-on-write or something, otherwise constructing them would slow down the builds quite a bit. could cache based on what goes into it, but still21:32
sandsmarkhmm, yeah21:32
kergothin the metadata, we do have access to the info about whta a task's dependencies are. autotools.bbclass copies all the .m4 files from the deps into a local dir to avoid races and whatnot. would likely use that same info in a new task that runs before do_configure to prep the recipe's sysroot, would just need to work out the details21:34
*** ntl <ntl!> has quit IRC21:35
*** ntl <ntl!> has joined #yocto21:42
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC21:52
*** rburton <rburton!> has quit IRC21:56
*** rburton <rburton!> has joined #yocto21:56
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC21:56
*** Hauke <Hauke!~Hauke@2001:41d0:8:b27b::4> has quit IRC21:57
*** fmeerkoetter <fmeerkoetter!> has quit IRC22:01
*** bfederau <bfederau!> has quit IRC22:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** lamego <lamego!~jose@> has quit IRC22:01
*** dmoseley <dmoseley!> has quit IRC22:14
*** Hauke <Hauke!> has joined #yocto22:15
*** rburton <rburton!> has quit IRC22:15
RPwe're certainly closer to being able to make it work that we ever have been before22:21
*** tsramos <tsramos!tsramos@nat/intel/x-pshdkmwojwysnkem> has quit IRC22:22
*** ryansturmer <ryansturmer!> has joined #yocto22:24
*** dreyna4529 <dreyna4529!~dreyna@> has quit IRC22:25
*** clsulliv <clsulliv!~clsulliv@> has quit IRC22:30
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto22:37
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC22:42
*** clsulliv <clsulliv!~clsulliv@> has joined #yocto22:45
*** ryansturmer <ryansturmer!> has quit IRC22:48
*** realBigfoot <realBigfoot!~realBigfo@> has quit IRC22:49
*** realBigfoot <realBigfoot!~realBigfo@> has joined #yocto22:51
*** afxez0r <afxez0r!afxez0r@nat/intel/x-okpbkwdauywgumhv> has quit IRC22:52
*** seebs_ <seebs_!> has joined #yocto22:58
*** seebs <seebs!> has quit IRC22:58
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC23:09
*** afxez0r <afxez0r!afxez0r@nat/intel/x-qpnilyzwgzxntyso> has joined #yocto23:12
*** stwcx <stwcx!~stwcx@> has quit IRC23:15
*** aehs29 <aehs29!~aehernan@> has quit IRC23:15
*** tingleby_ <tingleby_!> has quit IRC23:22
*** nighty-_ <nighty-_!> has quit IRC23:27
*** sjolley <sjolley!sjolley@nat/intel/x-pgmfroaeuxacawop> has quit IRC23:28
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto23:35
*** madisox <madisox!> has quit IRC23:37
*** jjmb <jjmb!> has joined #yocto23:39
*** Jackie_huang <Jackie_huang!~quassel@> has quit IRC23:39
*** jjmb1 <jjmb1!~jjmb@2601:46:c601:4490:8916:67bb:3825:d26d> has joined #yocto23:40
*** Jackie_huang <Jackie_huang!~quassel@> has joined #yocto23:41
*** jjmb <jjmb!> has quit IRC23:43
*** KvH_ <KvH_!> has joined #yocto23:49
*** KvH <KvH!> has quit IRC23:52
*** ryansturmer <ryansturmer!> has joined #yocto23:55

Generated by 2.11.0 by Marius Gedminas - find it at!