Wednesday, 2015-06-03

*** imphil <imphil!~philipp@2001:a60:111b:5001:fc1a:204b:cc86:fe86> has quit IRC00:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:20
*** manuel_ <manuel_!> has quit IRC00:25
*** psidhu <psidhu!> has joined #yocto00:34
*** paulg_ <paulg_!> has joined #yocto00:36
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC00:39
*** Jefro <Jefro!> has quit IRC00:42
*** Jefro <Jefro!> has joined #yocto00:42
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has quit IRC00:43
*** paulg_ <paulg_!> has quit IRC00:52
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC00:56
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has joined #yocto00:57
*** vmeson <vmeson!> has joined #yocto01:15
*** vmeson <vmeson!> has quit IRC01:16
*** paulg_ <paulg_!> has joined #yocto01:17
*** vmeson <vmeson!> has joined #yocto01:30
*** vmeson <vmeson!> has quit IRC01:32
*** vmeson <vmeson!> has joined #yocto01:45
-YoctoAutoBuilder- build #313 of nightly-deb is complete: Failure [failed Running Sanity Tests_1] Build details are at
*** ntl <ntl!> has quit IRC01:52
*** ntl <ntl!> has joined #yocto01:53
*** Jefro <Jefro!> has quit IRC02:05
*** paulg_ <paulg_!> has quit IRC02:24
*** [Sno] <[Sno]!> has joined #yocto02:25
*** ][Sno][ <][Sno][!> has quit IRC02:25
*** vmrod25 <vmrod25!~vmrod25@> has left #yocto02:40
*** staylor <staylor!> has joined #yocto02:53
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC02:57
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto02:57
*** redengin <redengin!> has joined #yocto03:02
*** redengin <redengin!> has left #yocto03:04
*** redengin <redengin!> has joined #yocto03:06
*** dvhart_ <dvhart_!dvhart@nat/intel/session> has joined #yocto03:11
*** dvhart_ <dvhart_!dvhart@nat/intel/session> has quit IRC03:11
*** dvhart_ <dvhart_!dvhart@nat/intel/x-miczggowktlgrbby> has joined #yocto03:11
*** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has quit IRC03:27
*** Jefro <Jefro!> has joined #yocto03:32
*** akhandav <akhandav!~arun@> has quit IRC03:37
*** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has joined #yocto03:39
*** manuel_ <manuel_!> has joined #yocto03:50
*** akhandav <akhandav!~arun@> has joined #yocto03:51
*** irontia <irontia!d4178ac2@gateway/web/freenode/ip.> has quit IRC03:53
*** dvhart_ <dvhart_!dvhart@nat/intel/x-miczggowktlgrbby> has quit IRC04:02
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto04:03
-YoctoAutoBuilder- build #324 of nightly-multilib is complete: Success [build successful] Build details are at
*** staylor <staylor!> has quit IRC04:24
[w00t]Hi, I'm crafting a recipe for a project depending on protobuf.. As I'm building the project it complains that it does not include the header files. From what I can see the header files are present in the -dev rpm package, how do I make them available in my project upon building it?04:46
[w00t]I've added protobuf to the DEPEND parameter04:46
redengin[w00t], have you tried changing the dependency to protobuf-dev?04:48
redenginnot sure if you need both protobuf and protobuf-dev04:49
[w00t]redengin: Yes, it complains that nothing provides protobuf-dev04:50
[w00t]redengin: when using both protobuf and protobuf-dev as well as only protobuf-dev04:51
redenginwhich protobuf recipe are you using?04:51
[w00t]2.5.0 from meta-virtualization/recipes-container/criu04:52
[w00t]Could I potentially add the include files in an bbappend file?04:54
*** dvhart_ <dvhart_!~dvhart@> has quit IRC04:55
redengin[w00t], it looks like that recipe is hacking on the pkg-config files to try and add the headers and libraries04:55
redenginsorry, but I'm kinda busy right now to turn my attention to debugging it.  It doesn't expose a protobuf-dev so that is out04:57
[w00t]redengin: Ok, thanks04:58
redengin[w00t], my suggestion would be to edit the recipe and drop all the pkg-config hackery, and do the necessary copies in the do_install05:01
[w00t]redengin: Ok, it seems like the hackery is only related to the ptest though05:03
[w00t]redengin: I'll try to fix it..05:03
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC05:03
redengin[w00t], ah, true05:03
-YoctoAutoBuilder- build #314 of nightly-arm-lsb is complete: Success [build successful] Build details are at
*** AndersD <AndersD!> has joined #yocto05:16
*** hamis <hamis!~irfan@> has joined #yocto05:27
*** LocutusOfBorg1 <LocutusOfBorg1!> has quit IRC05:28
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto05:35
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto05:41
*** MDR_ <MDR_!> has joined #yocto06:03
*** LocutusOfBorg1 <LocutusOfBorg1!> has quit IRC06:03
*** wadim_ <wadim_!> has joined #yocto06:04
*** DanielAdolfsson <DanielAdolfsson!> has joined #yocto06:05
*** dvhart_ <dvhart_!dvhart@nat/intel/x-xhltlmjkkpnhmoti> has joined #yocto06:06
*** grma <grma!> has joined #yocto06:17
*** Jefro <Jefro!> has quit IRC06:21
*** [w00t] <[w00t]!88a32c66@gateway/web/cgi-irc/> has quit IRC06:28
*** Jefro <Jefro!> has joined #yocto06:32
*** irontia <irontia!d4178ac2@gateway/web/freenode/ip.> has joined #yocto06:32
*** frsc <frsc!> has joined #yocto06:33
irontiaGood morning folks.06:33
*** Jefro <Jefro!> has quit IRC06:33
irontiaIs there a methodology to have a repository created by yocto builds? Perferably i want to manage a standard debian repository.06:35
redenginirontia, what do you mean?  as in you want to store all the generated rpms separate from the image?06:36
*** tmpsantos <tmpsantos!> has joined #yocto06:38
*** hitlin37 <hitlin37!uid16371@gateway/web/> has joined #yocto06:49
LetoThe2ndirontia: it's possible to create a package feed out of an openembedded build, but my google-fu is too weak at the moment to find proper instructions. maybe look at what the angstrom project does, as they basically do exactly that.06:50
*** mcrapet <mcrapet!5a500f41@gateway/web/freenode/ip.> has quit IRC06:50
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has joined #yocto06:51
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto06:55
*** jbrianceau_away is now known as jbrianceau06:55
*** pohly <pohly!> has joined #yocto06:57
*** mckoan|away is now known as mckoan07:01
mckoangood morning07:01
irontiathanks LetoThe2nd07:01
irontiaredengin: I want to build an distribution. From my past experiences that means to have a webserver providing a package repository so the targets can install packages and update...07:03
*** stiandre <stiandre!~stiandre@> has joined #yocto07:03
irontiaI want to be able to add and update packages to that repository also from the build system. And it should not always build everything. Packages that didn't change should not be rebuild. I don't feel i have the full yocto-understanding to fullfill this. I will look at package feeds first.07:04
redenginirontia, the only way I know of is to create an image based on a distro that uses all the recipes and then you'd have a set of rpm's that you could host07:04
LetoThe2ndirontia: to go nitpicking, you don't want to create a distribution (that is what poky, respectively its distro.conf does). you probably want to create a package repository, preferrable reachably through some webservice, for the distribution that you already have/are creating anyways.07:05
LetoThe2ndirontia: so your buzzwords are not "distribution" or such, but rather "package repository" or "package feed"07:06
*** diego_r <diego_r!> has joined #yocto07:07
irontiaRight, i would fork poky or parts of it as a basis for distribution. And part of that is a need for package management / package repository management.07:07
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto07:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:08
LetoThe2ndirontia: you're still mixing it up a bit. you can instantly get package management in a poky build by IMAGE_FEATURES += "package_management"07:09
redenginirontia, I think LetoThe2nd is referring to how distro is used inside yocto/bitbake, its more of a customization level to put things together, rather than a giant library07:09
irontiaI guess i found someone describing my needs:
LetoThe2ndirontia: so you're really looking just for a way to crate a proper download feed. the "distribution" and "package management" part are all already finished07:10
LetoThe2ndredengin: people just seem to be constantly confusing "distribution" and "package repository server somewhere on the web"07:11
redenginLetoThe2nd, it kinda makes sense, it'd be a cool feature if you could build a package repository to support an image07:12
LetoThe2ndredengin: because the latter is just a means of comfortably handing out the former, but its *not* part of it or necessary07:12
*** LocutusOfBorg1 <LocutusOfBorg1!> has quit IRC07:12
LetoThe2ndwe've had proper distributions with package managers and all that on floppies and cdrom for years.07:12
*** jku <jku!jku@nat/intel/x-idcyspwsgrkmxaaf> has joined #yocto07:13
LetoThe2ndso clearly some online means cannot be an integral part of the term "distribution"07:13
redenginLetoThe2nd, I'm not disagreeing, I'm just thinking a bitbake "repository.recipe" would be  a cool feature  (i.e. generate a full set of packages not specific to an image)07:14
LetoThe2ndredengin: and yes, of course its useful, "cool" and certainly possible to have an online paackage repository to support an OE created image. but to get there, its first crucial to get the terminology sorted out, because otherwise everybody just says "distribution".07:15
redenginbut it'd still have all the distro/machine/etc customizations specific for an image07:15
LetoThe2ndredengin: and its been done before, i repeat: just look at what the angstrom project does. its opkg and not rpm as irontia asked for, but basically its exactly that. an OE build that feeds an online package repository.07:16
redenginLetoThe2nd, sorry, I missed the part about the angstrom project07:18
LetoThe2ndredengin: np, thats why i repeated it :)07:19
bluelightningmorning all07:27
* LetoThe2nd mourns all, too.07:27
LetoThe2ndbut hey, long weekend ahead!07:28
*** roric <roric!~roric@> has joined #yocto07:37
erbororic: morning07:38
*** varibull <varibull!> has quit IRC07:38
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC07:42
*** roric <roric!~roric@> has quit IRC07:43
*** TobSnyder <TobSnyder!> has joined #yocto07:52
*** rburton <rburton!> has joined #yocto07:52
*** [w00t] <[w00t]!88a32c66@gateway/web/cgi-irc/> has joined #yocto08:01
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto08:06
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto08:06
*** sameo <sameo!~samuel@> has joined #yocto08:09
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto08:09
*** bluelightning_ <bluelightning_!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto08:11
*** bluelightning_ <bluelightning_!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC08:11
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:11
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC08:12
*** jimBaxter <jimBaxter!> has joined #yocto08:13
*** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC08:19
*** LocutusOfBorg1 <LocutusOfBorg1!> has quit IRC08:21
*** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto08:21
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto08:22
[w00t]Is there someplace where the bitbake build process is clearly specified..? In particular I'm interested in how dependencies are pulled in when building a package08:32
*** bluelightning_ is now known as bluelightning08:33
bluelightning[w00t]: do you mean build-time dependencies or runtime dependencies?08:33
*** loggerbox <loggerbox!todor@nat/intel/x-gftrudyocxrmnzly> has quit IRC08:35
[w00t]bluelightning: build-time08:36
bluelightningI don't know that we have documentation that covers this specifically (or at least I can't immediately find it)08:38
bluelightningultimately bitbake deals with almost everything it needs to actually carry out in the form of tasks, and thus dependencies end up being dependencies between tasks08:39
[w00t]bluelightning: ok, thanks08:40
bluelightningif recipe 'a' has DEPENDS = "b" that translates to recipe a's do_configure task depending on recipe b's do_populate_sysroot task08:40
*** ant_work <ant_work!> has joined #yocto08:41
bluelightningthere are other subtleties (and a few explicit task dependencies declared within the metadata) but DEPENDS is how most of the dependencies are expressed08:41
*** rburton <rburton!> has quit IRC08:41
*** tmcguire_ <tmcguire_!~tmcguire@> has quit IRC08:43
redenginbluelightning, I think its best to go off the most recent docs, since the legacy code has a lot of alternative ways to get it done08:44
hitlin37hi, i'm thikning of trying buildbot for build/release management stuff. since yocto uses it, i thought if someone could share their expereince using it.08:44
hitlin37i'm newbie to build bot, so wanted to know if its not too big to setup or try.08:45
redenginhitlin37, what are you trying to do?08:45
hitlin37we have some private project that has different parts that needs to be build.08:46
hitlin37suhc as OS and other software components08:46
bluelightningredengin: sure, I'm simplifying... I can go into more details in response to specific questions ;)08:46
hitlin37so, sommething that could make the job easier to make a release08:46
LetoThe2ndhitlin37: can't share too much, just: we use jenkins, and it works(TM)08:47
hitlin37and easier to share the releases method with other developers in the team, so that anyone could commit and make a release08:47
hitlin37ah, thanks LetoThe2nd08:48
hitlin37i have heard jetkins, it looks good08:48
LetoThe2ndhitlin37: in the end, its just a git repo watcher and trigger that runs our project specific build scripts08:48
LetoThe2nd(at least for us)08:48
*** rburton1 <rburton1!> has joined #yocto08:48
hitlin37right now, i run these scripts manually :)08:49
hitlin37but its good to have some systems08:49
LetoThe2ndthen stores some 'artifacts' away, and starts over08:49
redenginhitlin37, what kind of scripts?08:49
hitlin37so that other people can do it in easier way.08:49
hitlin37redengin: its like build script that do bunch of stuff and creates an os image08:49
LetoThe2ndreminds me, our new build server should arrive very soon ;)08:50
redenginhitlin37, I've done a lot of build management, usually when ppl say scripts, the build system is full of incongruent variations08:50
hitlin37or packages software from bunch of libraries08:50
hitlin37redengin: yes, you are very true08:51
hitlin37the script will fail on other people machine08:51
redenginmy advice is to map out what you want the ideal build for everything to do, and then figure out how to incrementally refactor the current stuff08:51
LetoThe2ndredengin: depends, it can also mean: there is aproper automation script that just needs the target and credentials08:51
hitlin37that's why i need a build management on some server08:51
redengina build engine isn't going to magically do it08:51
LetoThe2ndredengin: ++08:52
LetoThe2ndfirst step is always, make your build reproductible, take out magic that you need to do manually or that works only on your box08:52
LetoThe2ndafter that, you can add some automation to trigger that and take the outcome08:53
redenginI'd even posit that you should be able to build your build system from a script, then you know it's consistent08:53
LetoThe2ndredengin: you could even add a script that creates a script to script the creation of your build script!08:54
*** belen <belen!Adium@nat/intel/x-vdltmkprlbqiyeyz> has joined #yocto08:54
LetoThe2ndwhat we have right now here needs only python and the prerequisites stated in the yocto quick start. then everything from checking out, through getting the right commits/branch and setting conf/*.conf etc is fully automated08:56
redenginLetoThe2nd, I believe the singularity lies in creating the build system, so all attempts to go further backwards lead to the big bang08:56
LetoThe2ndredengin: i like big bangs! corben dallas to the rescue!08:56
*** roric <roric!~roric@> has joined #yocto09:13
*** JaMa <JaMa!> has joined #yocto09:15
*** manuel_ <manuel_!> has joined #yocto09:21
*** belen1 <belen1!~Adium@> has joined #yocto09:51
*** aswin <aswin!~aswin@> has joined #yocto09:52
*** belen <belen!Adium@nat/intel/x-vdltmkprlbqiyeyz> has quit IRC09:53
*** nighty^ <nighty^!> has joined #yocto09:55
*** naedanger <naedanger!> has joined #yocto10:01
*** aswin <aswin!~aswin@> has quit IRC10:10
*** ddom <ddom!> has joined #yocto10:15
*** Rootert <Rootert!> has quit IRC10:15
*** RagBal <RagBal!> has quit IRC10:15
hitlin37thanks LetoThe2nd and redengin . i like the part "figure out how to incrementally refactor the current stuff"10:18
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto10:20
*** frsc <frsc!> has quit IRC10:25
*** frsc <frsc!> has joined #yocto10:25
*** frsc <frsc!> has quit IRC10:30
*** frsc <frsc!> has joined #yocto10:30
*** aswin <aswin!~aswin@> has joined #yocto10:30
*** RagBal <RagBal!> has joined #yocto10:38
*** Rootert <Rootert!> has joined #yocto10:39
*** araldit <araldit!> has joined #yocto10:49
aralditanyone can explain how I get to have the x86_64-arago-linux-g++ compiler understand the -fuse-ld=gold command?10:50
*** belen1 <belen1!~Adium@> has quit IRC10:51
*** timsche <timsche!> has joined #yocto10:52
*** araldit <araldit!> has quit IRC10:56
*** AndersD <AndersD!> has quit IRC10:58
*** ueni_ <ueni_!~ueni@> has joined #yocto11:01
*** ueni <ueni!~ueni@> has quit IRC11:01
*** ueni_ is now known as ueni11:01
*** manuel_ <manuel_!> has quit IRC11:04
*** manuel_ <manuel_!> has joined #yocto11:10
*** araldit <araldit!> has joined #yocto11:12
*** manuel_ <manuel_!> has quit IRC11:12
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has quit IRC11:20
*** aswin <aswin!~aswin@> has quit IRC11:24
*** belen <belen!Adium@nat/intel/x-vwttgpfngaiacprf> has joined #yocto11:31
*** manuel_ <manuel_!> has joined #yocto11:33
*** tmcguire <tmcguire!~tmcguire@> has joined #yocto11:44
*** ][Sno][ <][Sno][!> has joined #yocto11:55
*** [Sno] <[Sno]!> has quit IRC11:56
*** vmeson <vmeson!> has quit IRC12:02
*** araldit <araldit!> has left #yocto12:02
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto12:09
*** florian_kc is now known as florian12:10
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto12:14
*** alimon <alimon!alimon@nat/intel/x-ywmqzuzrmcdyamsq> has quit IRC12:14
ionteuhhmm.. so.. i'm once again trying to install a custom kernel config for raspberrypi...12:17
iontei struggled with this some year or so ago, found out there was no fragment support, etc...
iontei finally got it working with this method:
iontebut now when i've returned to this project, new kernel has arrived and i can't get it to work anymore :(12:18
ionteanyone familiar with meta-raspberrypi who could give me some hints?12:19
*** kscherer <kscherer!~kscherer@> has joined #yocto12:26
*** lamego <lamego!lamego@nat/intel/x-ynmpyyplcjeadqbs> has joined #yocto12:43
*** vmeson <vmeson!~rmacleod@> has joined #yocto12:44
*** alimon <alimon!~alimon@> has joined #yocto12:45
*** zeddii <zeddii!~ddez@> has quit IRC13:06
*** zeddii <zeddii!~ddez@> has joined #yocto13:08
*** hsychla <hsychla!~hsychla@2001:6f8:12d9:13:8cad:a82d:ecd8:27f1> has quit IRC13:08
*** naedanger <naedanger!> has quit IRC13:10
*** berton <berton!~fabio@> has joined #yocto13:12
*** belen1 <belen1!Adium@nat/intel/x-lwnbfjnwlucuxqkb> has joined #yocto13:18
*** belen <belen!Adium@nat/intel/x-vwttgpfngaiacprf> has quit IRC13:19
*** hsychla <hsychla!~hsychla@2001:6f8:12d9:13:ddb4:6597:6f13:49f9> has joined #yocto13:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:21
mckoanionte: what's wrong into following again the same steps?13:22
iontemckoan: it did not work for some reason, not sure why. i finally got it working though...13:23
*** stiandre <stiandre!~stiandre@> has quit IRC13:35
*** stiandre <stiandre!~stiandre@> has joined #yocto13:35
*** wadim_ <wadim_!> has quit IRC13:36
*** wadim_ <wadim_!> has joined #yocto13:36
*** wadim_ <wadim_!> has quit IRC13:43
*** wadim_ <wadim_!> has joined #yocto13:44
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-vibdqhpqwgjkoixd> has joined #yocto13:45
roricerbo, go eftermiddag =)13:57
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto14:06
*** belen2 <belen2!Adium@nat/intel/x-tilmmehczbdeucmi> has joined #yocto14:07
*** belen1 <belen1!Adium@nat/intel/x-lwnbfjnwlucuxqkb> has quit IRC14:07
*** DanielAdolfsson <DanielAdolfsson!> has quit IRC14:08
*** jku <jku!jku@nat/intel/x-idcyspwsgrkmxaaf> has quit IRC14:11
*** madisox <madisox!> has joined #yocto14:15
*** bluelightning <bluelightning!> has joined #yocto14:17
*** bluelightning <bluelightning!> has quit IRC14:17
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto14:17
*** manuel__ <manuel__!> has joined #yocto14:19
*** manuel_ <manuel_!> has quit IRC14:20
*** manuel__ is now known as manuel_14:20
*** alimon <alimon!~alimon@> has quit IRC14:23
*** staylor <staylor!> has joined #yocto14:24
*** tsramos <tsramos!~tsramos@> has joined #yocto14:28
*** tsramos <tsramos!~tsramos@> has quit IRC14:30
*** tsramos <tsramos!tsramos@nat/intel/x-maygvsnfkhmeihce> has joined #yocto14:31
*** Jefro <Jefro!> has joined #yocto14:34
*** Jefro <Jefro!> has quit IRC14:38
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC14:38
*** wadim_ <wadim_!> has quit IRC14:39
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC14:41
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto14:45
*** frsc <frsc!> has quit IRC14:47
*** hamis <hamis!~irfan@> has quit IRC14:47
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:50
*** Jefro <Jefro!> has joined #yocto14:51
*** Jefro <Jefro!> has quit IRC14:54
*** timsche <timsche!> has quit IRC14:54
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto14:56
*** lamego <lamego!lamego@nat/intel/x-ynmpyyplcjeadqbs> has quit IRC15:03
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto15:09
vmrod25HI team , yesterday I did the final experiments with MPI + Yocto . And it works like a charm :) . If you have any specific feedback please do not hesitate to tell me . The next phase is to test it with some real HW ( minnowboards ) and publish the results. The real goal is to modify MPI to make it lighter and faster for embedded and IoT.15:11
vmrod25in the end I will try to look for a way to merge it into the Open Interconnect standard15:11
vmrod25open for comments :)15:11
*** sarahsharp <sarahsharp!~sarah@> has quit IRC15:13
-YoctoAutoBuilder- build #315 of nightly-arm-lsb is complete: Failure [failed] Build details are at
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC15:16
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto15:16
-YoctoAutoBuilder- build #336 of eclipse-plugin-juno is complete: Failure [failed Building Eclipse Plugin Publishing Artifacts] Build details are at
*** berton <berton!~fabio@> has quit IRC15:21
*** lamego <lamego!lamego@nat/intel/x-gpbmhfefkkytpcba> has joined #yocto15:22
*** belen2 <belen2!Adium@nat/intel/x-tilmmehczbdeucmi> has quit IRC15:35
*** belen1 <belen1!Adium@nat/intel/x-habbvgngdnuheoqu> has joined #yocto15:35
*** ajtag_ <ajtag_!> has quit IRC15:35
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto15:35
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto15:36
*** belen1 <belen1!Adium@nat/intel/x-habbvgngdnuheoqu> has quit IRC15:38
*** bluelightning <bluelightning!> has joined #yocto15:46
*** bluelightning <bluelightning!> has quit IRC15:46
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto15:46
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC15:47
*** dvhart_ <dvhart_!dvhart@nat/intel/x-xhltlmjkkpnhmoti> has quit IRC15:50
*** belen1 <belen1!Adium@nat/intel/x-zckxoxxzslskyvnn> has joined #yocto15:51
*** ant_work <ant_work!> has quit IRC15:53
*** DS__ <DS__!c9529440@gateway/web/freenode/ip.> has joined #yocto16:00
*** aswin <aswin!~aswin@> has joined #yocto16:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:07
*** alimon <alimon!~alimon@> has joined #yocto16:11
*** mckoan is now known as mckoan|away16:13
DS__Hi, I want to extend a defconfig file defined in a layer. The configurations I want to change are already present in the defconfig file. I created a .cfg file in my layer, added it in my bbappend of the kernel recipe, however the changes are never included in the final defconfig16:18
DS__If I make the changes in the defconfig directly, those changes are applied, but that breaks the entire point of not changing a layer that isn't "mine"16:18
*** belen2 <belen2!Adium@nat/intel/x-lwdprqwpwohzqcps> has joined #yocto16:18
DS__Why is this happening? Any ideas? Any ideas of how to solve this as well?16:18
*** belen1 <belen1!Adium@nat/intel/x-zckxoxxzslskyvnn> has quit IRC16:20
joshuaglcfg files only work for kernel recipes that inherit kernel-yocto16:20
*** sjolley <sjolley!sjolley@nat/intel/x-gfwkmebyhldwnbjh> has quit IRC16:20
DS__joshuagl in my case I'm adding them in a .bbappend of the kernel recipe16:20
DS__So it should work, shouldn't it?16:20
DS__Ah, just found that in the recipe it inherits "kernel" only16:21
DS__Not "kernel-yocto"16:21
DS__How should I proceed in this case?16:21
*** jku <jku!> has joined #yocto16:22
joshuaglprobably the easiest thing to do is cp the defconfig into your layer and make the modifications you require16:23
DS__And prepend the FILESEXTRAPATHS variable to "force" bitbake to find my defconfig before the original?16:24
DS__Would that work, considering this is an append of the original recipe?16:24
joshuaglyes, I'm pretty sure that works16:24
* joshuagl vaguely recalls doing the same16:24
DS__Right. I'm gonna try that joshuagl and will report back in some minutes. Thanks :)16:25
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto16:30
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto16:33
*** JaMa <JaMa!> has quit IRC16:36
*** jbrianceau is now known as jbrianceau_away16:37
*** JaMa <JaMa!> has joined #yocto16:37
DS__joshuagl: things didn't work very well. bitbake is still using the "old" defconfig file16:37
DS__Is it a thing of appending or prepending my path? I'm prepending right now, but I'm not sure if bitbake searches forward or backward in the paths provided16:39
joshuaglDS__: I'd expect a prepend to work, do you know what tasks were run? do you need to cleansstate?16:41
DS__joshuagl: I'm running a "bitbake <recipe_name> -c clean", which in my experience forces the entire rebuild of that recipe16:42
DS__in my experience as in: I see the configure, compile etc. tasks running again16:42
joshuaglah, OK - hmm16:42
joshuaglOK, my bbappend that overrides the defconfig looks like:16:43
joshuaglFILESEXTRAPATHS_prepend := "${THISDIR}/files:"16:43
joshuaglSRC_URI += "file://defconfig"16:43
DS__That's what my bbappend does16:44
joshuaglhmm, all I can tell you is that the lines I pasted WFM16:45
*** sjolley <sjolley!sjolley@nat/intel/x-mylecjtorjnqiuxm> has joined #yocto16:46
DS__joshuagl: which version of yocto are you using?16:47
joshuaglfido 1.816:48
DS__Same as me. This is weird :(16:48
DS__Well, I'll try some more things. If I find anything that works I'll let you know. Thank you for your help!16:49
joshuaglyou could cleansstate or even cleanall to make sure you're starting from a clean slate, I'd imagine adding an append invalidates the cache but I don't know that for certain16:50
joshuaglthen pass some -V's to increase the verbosity and see whether the file is being used16:50
joshuaglwhen I say -V's I mean -D's i.e bitbake virtual/kernel -c cleansstate && bitbake virtual/kernel -DDD16:51
* joshuagl heads off16:51
*** dvhart_ <dvhart_!~dvhart@> has quit IRC16:52
*** [Sno] <[Sno]!> has joined #yocto16:55
DS__joshuagl: yeah, I'm gonna try that. Thanks for the tip16:55
*** ][Sno][ <][Sno][!> has quit IRC16:55
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto16:57
-YoctoAutoBuilder- build #337 of eclipse-plugin-juno is complete: Success [build successful] Build details are at
*** dvhart_ <dvhart_!~dvhart@> has quit IRC17:00
*** ddom <ddom!> has quit IRC17:02
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-vibdqhpqwgjkoixd> has quit IRC17:04
*** paulg_ <paulg_!~paulg@> has joined #yocto17:04
*** sameo <sameo!~samuel@> has quit IRC17:09
*** paulg_ <paulg_!~paulg@> has quit IRC17:09
*** belen2 <belen2!Adium@nat/intel/x-lwdprqwpwohzqcps> has quit IRC17:10
*** paulg_ <paulg_!~paulg@> has joined #yocto17:11
DS__joshuagl: you're awesome! :)17:11
DS__joshuagl: thing is: bitbake was searching for <path>/<machinename> first, before searching only in <path>, and it didn't come to me that in the other layer the defconfig file was inside a <machinename> folder17:12
DS__I updated my files directory to have this <machinename> directory and things worked :)17:13
DS__That -DDD trick was awesome. I didn't know it. Thank you for your help!17:13
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC17:13
*** diego_r <diego_r!> has quit IRC17:13
*** varibull <varibull!> has joined #yocto17:18
*** varibull <varibull!> has quit IRC17:18
*** varibull <varibull!> has joined #yocto17:19
*** jku <jku!> has quit IRC17:19
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto17:25
*** dvhart_ <dvhart_!~dvhart@> has quit IRC17:38
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto17:39
*** lamego <lamego!lamego@nat/intel/x-gpbmhfefkkytpcba> has quit IRC17:41
*** dvhart_ <dvhart_!~dvhart@> has quit IRC17:42
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto17:45
*** jimBaxter <jimBaxter!> has quit IRC17:49
*** hitlin37 <hitlin37!uid16371@gateway/web/> has quit IRC17:52
*** lamego <lamego!lamego@nat/intel/x-hqksxwsluwiizale> has joined #yocto17:54
*** dvhart_ <dvhart_!~dvhart@> has quit IRC17:56
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto17:57
*** dvhart_ <dvhart_!~dvhart@> has quit IRC17:59
*** Jay7 <Jay7!> has quit IRC18:00
*** Jay7 <Jay7!> has joined #yocto18:00
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto18:04
*** DS__ <DS__!c9529440@gateway/web/freenode/ip.> has quit IRC18:05
*** TobSnyder <TobSnyder!> has quit IRC18:06
*** TobSnyder <TobSnyder!> has joined #yocto18:06
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC18:08
*** dvhart_ <dvhart_!~dvhart@> has quit IRC18:09
*** Jay7 <Jay7!> has quit IRC18:12
*** roric <roric!~roric@> has quit IRC18:13
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto18:14
*** dvhart_ <dvhart_!~dvhart@> has quit IRC18:15
*** aswin <aswin!~aswin@> has quit IRC18:26
*** stiandre <stiandre!~stiandre@> has quit IRC18:26
*** ncgs <ncgs!> has quit IRC18:27
*** belen1 <belen1!> has joined #yocto18:35
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC18:39
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto18:39
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto18:54
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto18:55
*** berton <berton!~fabio@> has joined #yocto18:56
*** dvhart_ <dvhart_!~dvhart@> has quit IRC18:56
*** belen1 <belen1!> has quit IRC18:59
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto19:03
*** JaMa <JaMa!> has quit IRC19:04
*** dvhart_ <dvhart_!~dvhart@> has quit IRC19:04
*** Aethenelle_ <Aethenelle_!~Aethenell@> has joined #yocto19:10
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC19:11
*** Aethenelle_ is now known as Aethenelle19:11
AethenelleBefore I bang my head against it again, is jdk 1.8 still only supported on aarch64?19:11
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto19:13
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC19:32
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto19:33
*** ncgs <ncgs!> has joined #yocto19:34
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC19:37
*** onoffon <onoffon!~khem@unaffiliated/khem> has joined #yocto19:44
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC19:44
*** jku <jku!> has joined #yocto19:49
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC19:55
*** roric <roric!> has joined #yocto19:56
*** DS_ <DS_!c9529440@gateway/web/freenode/ip.> has joined #yocto20:03
DS_Hi! I've created a python recipe that uses cffi. I need to compile something locally and output that in the site-packages directory. To do that in my machine, I just have to set an option in the, and cffi's integration will do the job for me. However, it appears that bitbake uses a different python than my machine's, and because it doesn't have cffi, the file never gets compiled as a result. How do I make yocto have cffi as a mod20:06
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto20:06
onoffonadd it to python-native20:06
*** onoffon is now known as khem`20:06
khem`RP: do we have latest build runs with gcc-5 somewhere ?20:07
khem`RP: I am interested to see x86_64 builds after binutils fixes20:07
*** ddalex1 <ddalex1!~ddalex@> has joined #yocto20:07
DS_onoffon: what do you mean? I've googled a bit and found this python-native thing, but didn't understand it very well. Does that mean I have to turn python-cffi into a native package?20:07
khem`as well20:08
DS_And then specify nativesdk-python-cffi in the TOOLCHAIN_HOST_TASK?20:08
khem`OE's dependency on python meant that we ended up building our own and not rely on the one from build host20:08
khem`if you want that it should go into SDK then yes20:09
DS_I just want bitbake's python (whatever that is) to have cffi as a module20:10
DS_That way the option I've set in will work20:10
*** dfaught <dfaught!> has joined #yocto20:13
khem`OK then you just need native version20:13
khem`not sdk one20:13
DS_khem`: so I inherit "native" instead of "nativesdk"?20:14
DS_What should be the name I put in TOOLCHAIN_HOST_TASK?20:15
DS_I've tried 'native-python-cffi' but bitbake didn't pick it up20:16
khem`you dont have to20:18
khem`just add the proper dependency on the  recipe needing it20:18
DS_Bitbake will automatically parse the recipe and know it is a native recipe, and then automatically build it?20:19
DS_I just tried baking stuff, but it doesn't seem the native recipes got picked up20:20
khem`add a dependency on native-<blah>20:22
khem`or <blah>-native20:22
DS_Ah! Gotcha20:24
DS_I did that and got this feedback from bitbake: "WARNING: QA Issue: python-tss rdepends on python-cffi-native, but it isn't a build dependency? [build-deps]"20:24
DS_And then the build failed because when trying to install python-tss, it said no package provided python-cffi-native20:25
DS_That recipe was just created exactly for that to work :(20:25
*** pohly <pohly!> has quit IRC20:26
DS_Duh, maybe it should've been "depends" instead of "rdepends"20:26
DS_Of course it wouldn't work with rdepends :)20:26
DS_khem`: this doesn't appear to have worked. Bitbake's python still didn't recognize the option in setup.py20:28
DS_"/home/...../tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/ UserWarning: Unknown distribution option: 'cffi_modules'"20:29
khem`DEPENDS += "python-cffi-native"20:29
DS_Yup, I did that20:29
khem`ok and you wrote recipe to provide it ?20:30
khem`if not you will need that20:30
DS_Basically I copied the recipe from meta-opembedded and added an "inherit native" as the last clause20:32
DS_No errors with the baking happened, but from the log of python-tss, I get this warning, which shows that bitbake's python didn't get the module20:33
*** vmeson <vmeson!~rmacleod@> has quit IRC20:34
DS_Damn this is beautiful. native recipes to build the stuff you need to build the image. Now I only gotta make it work haha20:37
DS_khem`: ok. I have confirmed that python-cffi-native is being built. It's inside the site-packages directory of the native python20:39
DS_For some reason it's not integrating with the native distutils20:39
DS_I'll figure this out now20:39
DS_Thanks for your help20:39
*** jku <jku!> has quit IRC20:44
DS_Ok khem` ! Got it working :) Thanks for all your help20:50
*** ant_home <ant_home!~ant__@> has joined #yocto20:53
*** tmpsantos <tmpsantos!> has quit IRC21:01
*** ddalex1 <ddalex1!~ddalex@> has quit IRC21:01
*** [w00t] <[w00t]!88a32c66@gateway/web/cgi-irc/> has quit IRC21:03
*** varibull <varibull!> has quit IRC21:04
*** varibull <varibull!> has joined #yocto21:04
*** DS_ <DS_!c9529440@gateway/web/freenode/ip.> has quit IRC21:06
*** ddalex1 <ddalex1!> has joined #yocto21:08
*** tsramos <tsramos!tsramos@nat/intel/x-maygvsnfkhmeihce> has quit IRC21:17
*** tsramos <tsramos!tsramos@nat/intel/x-szopysvpprmlofcy> has joined #yocto21:18
*** ant_home <ant_home!~ant__@> has quit IRC21:21
gabrbeddDoes 1.9 have a codename? (wiki sez no, but I don't believe that. )21:22
*** tsramos <tsramos!tsramos@nat/intel/x-szopysvpprmlofcy> has quit IRC21:23
*** nighty^ <nighty^!> has quit IRC21:35
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto21:37
*** nighty^ <nighty^!> has joined #yocto21:40
RPkhem`: no, I should queue one up21:44
RPgabrbedd: not yet, no21:45
gabrbeddRP: thanks21:45
*** ryoshu <ryoshu!~kamil@unaffiliated/ryoshu> has joined #yocto21:47
ryoshuI'm working on BPS, having 3 questions21:47
ryoshu1. I need custom toolchain for my platform, how to "connect" it to the yocto target21:48
ryoshu[Sno]: hi!21:50
*** berton <berton!~fabio@> has quit IRC21:50
*** dfaught <dfaught!> has quit IRC21:55
*** rburton1 <rburton1!> has quit IRC21:57
*** ddalex1 <ddalex1!> has quit IRC21:58
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC21:58
*** bfederau <bfederau!> has quit IRC22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** sarahsharp <sarahsharp!~sarah@> has quit IRC22:07
-YoctoAutoBuilder- build #320 of build-appliance is complete: Failure [failed BuildImages] Build details are at
*** roric <roric!> has quit IRC22:20
*** btp <btp!d8f01e19@gateway/web/freenode/ip.> has joined #yocto22:38
btpanyone here?22:38
*** btp <btp!d8f01e19@gateway/web/freenode/ip.> has quit IRC22:39
*** ajtag_ <ajtag_!> has joined #yocto22:39
*** ajtag- <ajtag-!> has joined #yocto22:43
*** ajtag_ <ajtag_!> has quit IRC22:43
*** nighty^ <nighty^!> has quit IRC22:54
*** Aethenelle_ <Aethenelle_!~Aethenell@> has joined #yocto22:55
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC22:56
*** Aethenelle_ is now known as Aethenelle22:56
*** paulg_ <paulg_!~paulg@> has quit IRC23:04
-YoctoAutoBuilder- build #327 of nightly-multilib is complete: Success [build successful] Build details are at
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC23:13
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC23:15
*** berton <berton!~fabio@> has joined #yocto23:15
*** madisox <madisox!> has quit IRC23:22
*** lamego <lamego!lamego@nat/intel/x-hqksxwsluwiizale> has quit IRC23:23
*** dvhart_ <dvhart_!~dvhart@> has quit IRC23:26
*** sjolley <sjolley!sjolley@nat/intel/x-mylecjtorjnqiuxm> has quit IRC23:28
*** [Sno] <[Sno]!> has quit IRC23:31
*** [Sno] <[Sno]!> has joined #yocto23:31
*** paulg_ <paulg_!> has joined #yocto23:34
*** alimon1 <alimon1!> has joined #yocto23:40
*** staylor <staylor!> has quit IRC23:42
*** alimon1 <alimon1!> has quit IRC23:46
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto23:47
*** alimon1 <alimon1!> has joined #yocto23:54

Generated by 2.11.0 by Marius Gedminas - find it at!