Wednesday, 2017-11-29

*** martinkelly1 <martinkelly1!> has joined #yocto00:06
*** Martian <Martian!~martian@> has quit IRC00:11
*** stephano <stephano!~stephano@> has quit IRC00:51
*** stephano <stephano!stephano@nat/intel/x-pqhiwwtohloebvse> has joined #yocto00:51
*** stephano <stephano!stephano@nat/intel/x-pqhiwwtohloebvse> has quit IRC00:53
*** stephano <stephano!stephano@nat/intel/x-qkprvfnjdywqfpse> has joined #yocto00:53
*** vmeson <vmeson!> has quit IRC00:53
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC00:56
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto01:02
*** sgw <sgw!~swold@> has quit IRC01:05
*** majuk <majuk!> has quit IRC01:05
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:07
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC01:09
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto01:18
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC01:25
*** jkridner|pd <jkridner|pd!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:30
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto01:31
*** martinkelly1 <martinkelly1!> has quit IRC01:32
*** ski7777 <ski7777!> has quit IRC01:45
*** grokreality <grokreality!~grokreali@> has quit IRC01:46
*** ski7777 <ski7777!> has joined #yocto01:46
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto01:47
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC02:12
*** sgw <sgw!> has joined #yocto02:13
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto02:14
*** rcw <rcw!> has quit IRC02:17
*** sgw1 <sgw1!~swold@> has joined #yocto02:20
*** sgw <sgw!> has quit IRC02:22
*** BubuIIC <BubuIIC!> has quit IRC02:30
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC02:33
*** fitzsim <fitzsim!> has quit IRC02:36
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto02:36
*** fitzsim <fitzsim!> has joined #yocto02:36
*** stephano <stephano!stephano@nat/intel/x-qkprvfnjdywqfpse> has quit IRC02:44
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC02:54
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto02:55
*** vmeson <vmeson!> has joined #yocto02:57
*** majuk <majuk!> has joined #yocto03:07
*** sjolley <sjolley!~sjolley@> has quit IRC03:10
*** majuk <majuk!> has quit IRC03:11
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC03:17
*** dv_ <dv_!> has quit IRC03:19
*** dv_ <dv_!> has joined #yocto03:19
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto03:24
*** martinkelly1 <martinkelly1!> has joined #yocto03:28
*** Guest51 <Guest51!> has joined #yocto03:34
*** Guest51 <Guest51!> has quit IRC03:55
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC04:00
*** stephano <stephano!~stephano@> has joined #yocto04:10
*** Guest51 <Guest51!> has joined #yocto04:23
*** martinkelly1 <martinkelly1!> has quit IRC04:25
*** joeythesaint <joeythesaint!~joe@2605:6400:2:fed5:22:41:45ec:bf91> has quit IRC04:29
*** joeythesaint <joeythesaint!~joe@2605:6400:2:fed5:22:41:45ec:bf91> has joined #yocto04:29
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto04:47
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC04:59
*** nighty- <nighty-!> has joined #yocto05:04
*** khem <khem!~khem@unaffiliated/khem> has quit IRC05:24
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto05:26
*** stephano <stephano!~stephano@> has quit IRC05:30
*** xtron <xtron!~xtron@> has joined #yocto05:38
*** ctwr <ctwr!~he@> has quit IRC05:47
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto05:51
*** Guest51 <Guest51!> has quit IRC05:54
*** Guest51 <Guest51!> has joined #yocto05:59
*** hamis <hamis!~irfan@> has joined #yocto06:02
*** ctwr <ctwr!~he@> has joined #yocto06:15
xtronHi all, I'm trying to fetch a git repo and compiling it using cmake, but getting error of "bad RPATH", by doing < do_package_qa[noexec] = "1" > provides a work around but not a proper fix. anybody have idea what can be wrong?06:24
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC06:26
*** paulg <paulg!> has quit IRC06:58
-xtron- USERINFO i'm good06:59
*** agust <agust!> has joined #yocto07:00
*** t0mmy <t0mmy!> has joined #yocto07:04
*** paulg_ <paulg_!~paulg@> has quit IRC07:13
*** sagner <sagner!~ags@2001:1620:c6e:0:b195:d372:4959:f429> has quit IRC07:15
*** paulg_ <paulg_!~paulg@> has joined #yocto07:15
*** Guest51 <Guest51!> has quit IRC07:16
*** pohly <pohly!> has joined #yocto07:16
*** t0mmy <t0mmy!> has quit IRC07:22
*** Bunio_FH <Bunio_FH!> has joined #yocto07:38
*** joshuagl <joshuagl!joshuagl@nat/intel/x-kdnqsjqkxvrozlmp> has joined #yocto07:45
*** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto07:49
*** mdnneo <mdnneo!~umaucher@> has joined #yocto07:49
*** sagner <sagner!~ags@> has joined #yocto07:56
*** t0mmy <t0mmy!~tprrt@> has joined #yocto07:58
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:ed43:b101:10d8:c219> has joined #yocto08:00
*** mckoan|away is now known as mckoan08:04
mckoangood morning08:05
*** fischerm <fischerm!> has quit IRC08:08
*** fischerm <fischerm!> has joined #yocto08:08
*** fl0v0 <fl0v0!> has joined #yocto08:11
*** rajm <rajm!~robertmar@> has joined #yocto08:14
yoctiNew news from stackoverflow: how to enable systemd in x11 in yocto <>08:17
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:ed43:b101:10d8:c219> has quit IRC08:19
*** ed21 <ed21!Adium@nat/intel/x-guglcviyugqpugle> has joined #yocto08:20
nayfemckoan: good morning08:21
*** yann <yann!> has quit IRC08:27
*** Kakounet <Kakounet!> has joined #yocto08:29
*** vdehors_arc <vdehors_arc!> has joined #yocto08:39
*** hnje <hnje!> has joined #yocto08:40
*** rburton <rburton!> has joined #yocto09:02
*** gtristan <gtristan!~tristanva@> has quit IRC09:12
*** dave0x6d <dave0x6d!uid190567@gateway/web/> has quit IRC09:19
*** kuneco <kuneco!~kuneco@> has quit IRC09:20
*** aurele <aurele!> has joined #yocto09:27
aurelehi everyone09:27
aureleI have a problem with the postinstall scripts, with a package, the scripts are not present in the rpm package, and they are not launched in the do_rootfs09:29
aurelehow can I debug this?09:29
*** yann <yann!~yann@> has joined #yocto09:30
aureleI can see the postinstall script in the pkgdata/runtime/"pkgname"09:31
aurelebut now I don't know where I can continue to debug this problem09:31
aureleIf anyone can help me...09:31
*** kuneco <kuneco!~kuneco@> has joined #yocto09:33
aurelethis is not my first package, I tried to set the pkg_postinst_${PN} but still nothing in the RPM (I'm trying to install a service file... and it is not activated during install)09:33
*** gtristan <gtristan!~tristanva@> has joined #yocto09:43
*** volestorm <volestorm!> has quit IRC09:43
*** volestorm <volestorm!> has joined #yocto09:45
nayfeaurele: systemd service ?09:45
aurelenayfe, yes systemd service09:46
aureleI have a lead, maybe it is because of the package name09:46
aureleI have 1 upper case in the package name09:47
nayfeaurele: you don't need postinstall to install systemd service, you can use SYSTEMD_SERVICE_${PN} = "XXX.service" is it a custom stuff ?09:47
aurelenayfe, I noticed the service doesn't install correctly then after investigation the postinstall script are not used in the package09:48
nayfedo you inherit systemd ?09:49
aurelenayfe, then if I fix the postinstall script missing, my service will be activated09:49
*** rburton <rburton!> has quit IRC09:49
aurelenayfe, yes09:49
nayfeaurele: maybe pastbin your recipe?09:51
*** t0mmy <t0mmy!~tprrt@> has quit IRC09:53
*** t0mmy <t0mmy!~tprrt@> has joined #yocto09:55
*** diembed <diembed!> has joined #yocto09:59
aurelenayfe,  the content of the file "pkgdata/runtime/onvifCpp"
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC10:01
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto10:03
*** hari_ <hari_!6a336c1b@gateway/web/freenode/ip.> has joined #yocto10:03
*** hari_ <hari_!6a336c1b@gateway/web/freenode/ip.> has quit IRC10:04
nayfeaurele: what's the name of your recipe ? onvifdiscovery ? maybe you need to RDEPENDS castel service ?10:05
aurelethe name of the package is onvifCpp10:06
aurelenayfe, I removed the upper case letter and everything is ok...10:08
*** luneff <luneff!~yury@> has joined #yocto10:08
nayfeaurele: good to hear10:09
aurelenayfe, Is it written somewhere that packages name should be lowercase?10:12
nayfeaurele: it says "use lower-case"10:13
aurelenayfe, thanks for pointing this.. I will have to fix some packages name10:13
nayfeaurele: didn't know about too, just grepping lower in manual :)10:17
aurelenayfe, I would have search after fixing this recipe10:18
aurelenayfe, thanks a lot for your help10:18
nayfeentre concurrents on peut bien s'aider :)10:20
*** nighty- <nighty-!> has quit IRC10:28
*** hnje <hnje!> has quit IRC10:30
*** kaspter <kaspter!~Instantbi@> has quit IRC10:30
*** kaspter <kaspter!~Instantbi@> has joined #yocto10:32
*** pohly <pohly!> has quit IRC10:42
*** pohly <pohly!> has joined #yocto10:48
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto10:56
fl0v0Hi! I'm in the process of migrating from 'fido' to 'rocko' at the moment and I'am now faced with the problem that i can't build a gpl-3.0 free build anymore.10:56
fl0v0the problem is that some packages require 'cpp-symlinks' which is a package that is provided by the gcc recipe (which is gpl-3.0).10:56
fl0v0I found out that in 'fido' there are some packages whitelisted in the which is no longer the case in 'rocko'.10:56
fl0v0Has the way changed how to achieve a gpl-3.0 free build? I couldn't find anything about it in the migration instructions except for the gplv2-layer that i have included.10:56
T_UNIXis it known that rocko fails to build due to 'Deprecated variable(s) found: "IMAGE_DEPENDS_wic"' in various recipes?  poky/meta/recipes-core/images/ poky/meta/recipes-core/ovmf/ovmf-shell-image.bb11:01
*** BubuIIC <BubuIIC!> has joined #yocto11:05
*** BubuIIC <BubuIIC!> has quit IRC11:07
*** BubuIIC <BubuIIC!~mhoffmann@2003:a:772:9200:5748:f262:e193:b5c1> has joined #yocto11:09
*** rburton <rburton!> has joined #yocto11:09
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto11:11
rburtonaurele: uppercase letters are not allowed (older releases may not sanity check this enough)11:14
rburton(overrides are lowercase, so you can't have a _${PN} where PN containers uppercase)11:14
*** vdehors_arc <vdehors_arc!> has quit IRC11:22
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC11:25
-YoctoAutoBuilder- build #874 of nightly-mips64 is complete: Failure [failed Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 BuildImages_1 Running SDK Sanity Tests_1] Build details are at
*** gtristan <gtristan!~tristanva@> has quit IRC11:37
aurelerburton, can you give me an example of override? you talk about writing PN="pkgname" in the recipe?11:37
rburtonsee the docs, but an overide is when you do pkg_postinst_${PN}.  the PN bit is the override11:37
rburtonthe variable is pkg_postinst, but its specific to PN11:38
rburtondistinct from pkg_postinst_${PN}-dev, where the override is ${PN}-dev11:38
*** gtristan <gtristan!~tristanva@> has joined #yocto11:39
*** hnje <hnje!~hnje@> has joined #yocto11:40
*** mdnneo_ <mdnneo_!~umaucher@> has joined #yocto11:41
aurelerburton, ok I understand now thanks for the tip11:42
*** milindur <milindur!> has quit IRC11:42
*** mdnneo <mdnneo!~umaucher@> has quit IRC11:44
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:44
*** umaucher__ <umaucher__!~umaucher@> has joined #yocto11:45
*** mdnneo <mdnneo!~umaucher@> has joined #yocto11:48
*** mdnneo_ <mdnneo_!~umaucher@> has quit IRC11:49
-YoctoAutoBuilder- build #1296 of nightly-x86-64 is complete: Failure [failed Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at
*** umaucher__ <umaucher__!~umaucher@> has quit IRC11:50
-YoctoAutoBuilder- build #1265 of nightly-arm is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 BuildImages_2 Building Toolchain Images_2 Running SDK Sanity Tests Building Toolchain Images_3 BuildImages_3 Running ESDK Sanity Tests] Build details are at
*** hamis <hamis!~irfan@> has quit IRC11:59
-YoctoAutoBuilder- build #1235 of nightly-mips is complete: Failure [failed Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at
*** gtristan <gtristan!~tristanva@> has quit IRC12:17
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto12:17
*** milindur <milindur!> has joined #yocto12:30
*** nighty- <nighty-!> has joined #yocto12:31
*** wouterstreamit <wouterstreamit!589f1708@gateway/web/freenode/ip.> has joined #yocto12:46
wouterstreamitI am trying to use a custom configuration for poky/meta/recipes-connectivity/openssh. To do this I am using a bbappend with FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" and my own sshd_config in the openssh folder, but it is still using the original one, why?12:48
*** vdehors_arc <vdehors_arc!> has joined #yocto12:49
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC12:53
nayfewouterstreamit: is your bbappend path is correct and sshd_config?12:55
*** Willy-- <Willy--!8eb15cbf@gateway/web/freenode/ip.> has joined #yocto12:56
wouterstreamitYes. After inspecting with bitbake -e openssh I found that in the expansion of FILESPATH the original file was included before mine (probably because the ${PN} folder in the original bb directory is included in FILESPATH before FILESEXTRAPATH is added). As I only needed one small change I have solved it in a better way now using a sed -i command in a do_install_append function13:02
*** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC13:04
*** uglyoldbob <uglyoldbob!~uglyoldbo@> has quit IRC13:04
wouterstreamitI would still like to learn how to work around the original problem though as I'd expect overriding a file included with file:// in the original recipe with one of your own should be a lot easier13:07
*** t0mmy <t0mmy!~tprrt@> has quit IRC13:15
*** peacememories <peacememories!> has joined #yocto13:19
-YoctoAutoBuilder- build #1250 of nightly-multilib is complete: Failure [failed BuildImages_6 Running SDK Sanity Tests] Build details are at
*** ed21 <ed21!Adium@nat/intel/x-guglcviyugqpugle> has quit IRC13:30
*** luneff <luneff!~yury@> has quit IRC13:32
*** t0mmy <t0mmy!~tprrt@> has joined #yocto13:33
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto13:38
*** mjourdan <mjourdan!~mjourdan@> has quit IRC13:39
*** kaspter <kaspter!~Instantbi@> has quit IRC13:40
*** mjourdan <mjourdan!~mjourdan@> has joined #yocto13:41
*** kaspter <kaspter!~Instantbi@> has joined #yocto13:41
*** smagnani <smagnani!~smagnani@> has joined #yocto13:45
*** zerus <zerus!> has joined #yocto13:46
yoctiNew news from stackoverflow: Yocto/OpenEmbedded Recipe Including library paths from host <>13:48
*** learningc <learningc!> has joined #yocto13:51
*** mjourdan <mjourdan!~mjourdan@> has quit IRC13:51
*** mjourdan <mjourdan!~mjourdan@> has joined #yocto13:52
*** learningc <learningc!> has quit IRC13:52
*** learningc <learningc!> has joined #yocto13:52
kanavinhahaha "I have the luxury of dealing with the endless error and warning paradise that is OpenEmbedded. "13:54
*** learningc <learningc!> has joined #yocto13:54
kanavin(from the above stackoverflow)13:54
*** learningc <learningc!> has quit IRC13:56
*** learningc <learningc!> has joined #yocto13:56
*** learningc <learningc!> has joined #yocto13:56
Crofton|workclearly we need to comment on his indentation13:57
*** marka <marka!~masselst@> has joined #yocto14:00
*** aragua__ <aragua__!> has joined #yocto14:02
kanavinthe poor chap is trying to build something which has bare makefiles14:03
nayfecrofton: i love stackoverflow, i give a hint to look at already made recipe here and my answer get deleted because it's only a link :p14:03
*** aragua_ <aragua_!> has quit IRC14:05
Crofton|workyeah, they have rulez14:07
kanavinI'm reluctant to start answering things on SO, because it could be a horrible time sink14:07
Crofton|workI find it interesting seeing what crazy shit people do14:08
Crofton|workat least skim14:08
Crofton|workI ddi find one of anders answers and use it to help a customer14:08
*** Artox <Artox!~Artox@> has quit IRC14:08
Crofton|workso it has value when we feed it properly14:08
*** Artox <Artox!~Artox@> has joined #yocto14:09
kanavinCrofton|work: this one however is just fixing someone's mutiply-broken recipe14:10
*** gtristan <gtristan!~tristanva@> has joined #yocto14:10
Crofton|workSo things we can do is down vote the original question14:11
Crofton|workor try to explain why the recipe is downvoted14:12
*** peacememories <peacememories!> has quit IRC14:12
Crofton|workreally need someone who understands the stack overflow process to help us shape it14:12
Crofton|workbut at least we are learning what is posted there14:12
nayfeI'd suggest the bot to auto reply a comment to join #yocto :)14:14
Crofton|worknot sure we want that either14:15
kanavinor even 'worse': join the yocto mailing list14:16
kanavinwill be flooded with n00bz14:16
sveinsekanavin: but that has its flipside: One assurance to the survival of communities like this is, well, recrutement by n00bz. I'm working on another project which does not have a large community and that is even harder to work on than a community (such as rasberry pi) overwhelming with noise (i.e. no00bs)14:19
*** ed21 <ed21!Adium@nat/intel/x-gqkistqowwlovreh> has joined #yocto14:21
kanavinsveinse: I'm well aware, I actually do think that the best response to the above question is to invite the person to the yocto ML14:23
kanavinwhere his recipe and the upstream project can be better dissected14:23
sveinseyes, I don't disagree to that14:24
kanavinin other cases, it's possible to answer directly, if the question/answer is common and useful to many14:24
*** rcw <rcw!> has joined #yocto14:26
sveinseFrom my two years with Yocto, I've learned that even thou the ruleset for the bitbake recipe language is pretty easy, getting all the tricks and rules of how oe builds an image is a long and steep learning process.14:26
sveinseI have colleagues (and myself) who have been utterly frustrated with Yocto at times. Perhaps this stackoverflow post is just that: venting of built up frustration. -- Though vile is usually not the best way to get help thou14:28
kanavinsveinse: yeah, people keep saying that yocto is too complicated, but to me that's about as meaningful as saying that 'linux kernel is too complicated'14:28
kanavinsveinse: there's also buildroot, you know :) if it suits someone's goals, then that's just fine!14:29
kanavinwe need competition :)14:29
sveinsekanavin: yes, competition is good.14:30
sveinseAnd I hope this community is open for hearing pain points and user stories as well14:30
-YoctoAutoBuilder- build #1248 of nightly-ppc is complete: Failure [failed Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at
sveinseWe're using Yocto to build the linux system on a commercial product (where the customer does not interact with Linux other than via the GUI) and we're not going back14:33
kanavinsveinse: I find it hilarious that uses the word 'easy' at least 10 times on the front page :) clearly they're trying hard not to mention YP :)14:34
sveinseJust upgraded from krogoth to pyro to now very soon rocko, and for the first time ever, these migration has been utterly smooth14:34
kanavinactually, exactly five times, but still - major selling point14:35
*** ed21 <ed21!Adium@nat/intel/x-gqkistqowwlovreh> has quit IRC14:35
LetoThe2ndif it fits your use case. BR is fine (just like ptxdist, or whatever comparable)14:36
LetoThe2ndwe switched from ptxdist to OE in the last couple of years, and there's certainly no going back for us too.14:36
rburtoni bought a iot camera thing this week, openwrt based14:37
sveinseI've been using a lot of buildsystems across the years. One of the most innovative details of OE is the sstate scheme.14:37
rburtonturns out on first boot you can telnet in as root without a password14:37
LetoThe2ndrburton: ip plz14:38
rburtoni've since discovered its first boot only as i moved the power socket and can't telnet in anymore, which is a shame14:38
sveinseperhaps that safe, rburton. Haven't telnet become exotic these days?14:38
*** austen <austen!268c0cd2@gateway/web/freenode/ip.> has quit IRC14:38
*** dfaught <dfaught!> has joined #yocto14:44
sveinseI wish yocto would have a unified configuration management system on top of oe. I know it is deliberately not included in the project, but the consequence of it is that when you're moving from BSP to BSP or system to system, the vendor's scheme for CM changes wildly14:44
sveinseWe've ended up with a separate build system on top of yocto to handle these variations14:45
kanavinsveinse: it's not that it's deliberate, it's that there's only 24 hours a day14:46
sveinsekanavin: yup, granted14:46
kanavinsveinse: if you polish, publish, and commit to taking care of your solution, then we'll be happy to take it14:46
*** lamego <lamego!~jose@> has joined #yocto14:47
sveinsekanavin: yeah, maybe I should. An oppertunity to perhaps help shape this. Let me wing this to my managers14:48
yoctiNew news from stackoverflow: How can I build Yocto image to using build script? <>14:48
nayfemaybe pick one vendor solution with its permission is easier ?14:49
sveinseooi, what do you use to collect/manage the layer repos? google's repo?14:50
*** peacememories <peacememories!> has joined #yocto14:50
*** smagnani <smagnani!~smagnani@> has quit IRC14:51
-YoctoAutoBuilder- build #19 of eclipse-plugin-oxygen is complete: Success [build successful] Build details are at
nayfesveinse: i'm using freescale env. with google repo (don't know if question was for me)14:52
kanavinokay, this last one is best solved with a yocto ml invite too - my best guess is he's trying to write a recipe around some cmake-based upstream project and is having trouble doing that14:53
kanavinthere's no detail there, or even a question14:53
nayfe"it's too complicate" hum ...14:53
sveinsenayfe: thanks (no it wasn't) -- We're also using freescale in the base system14:54
kanavinnayfe: I'm fine with bad grammar if the person is willing to be an active partner in finding a solution, which in this case doesn't quite look like that14:56
*** nathani_ <nathani_!> has joined #yocto14:57
nayfekanavin: same :) i can't comment yet on SO i'll not risk to answer and get a minus14:58
*** gabrbedd <gabrbedd!> has quit IRC15:01
*** gabrbedd <gabrbedd!> has joined #yocto15:02
*** pohly <pohly!> has quit IRC15:04
*** smagnani <smagnani!> has joined #yocto15:04
*** pohly <pohly!> has joined #yocto15:05
nayfewell let's try15:05
*** xtron <xtron!~xtron@> has quit IRC15:07
Crofton|workyou need to build reputation on stack overflow to be useful :)15:08
nayfeCrofton|work> trying hard but it seems i'm bad company15:09
LetoThe2ndnayfe: cue
sveinseWhen was the multiple configuration support added to yocto?15:10
sveinserocko or pyro?15:10
andycooperearlier. we're using it on morty15:10
sveinseok, thanks15:11
Crofton|workno porblem takes time and patience15:12
nayfe<LetoThe2nd: i had this in mind :)15:13
LetoThe2ndnayfe: ++15:14
LetoThe2ndnayfe: albeit 5FDP being a bit too depressing for me, i particularly like jekyll and hyde :-)15:15
*** Bunio_FH <Bunio_FH!> has quit IRC15:19
*** hnje <hnje!~hnje@> has quit IRC15:20
*** jku_ <jku_!> has joined #yocto15:30
*** ed21 <ed21!Adium@nat/intel/x-vxqrbabqmxiorwlq> has joined #yocto15:32
-YoctoAutoBuilder- build #856 of nightly-arm64 is complete: Failure [failed Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 BuildImages_1 Running ESDK Sanity Tests] Build details are at
*** smagnani <smagnani!> has quit IRC15:39
*** majuk <majuk!> has joined #yocto15:40
*** sgw1 <sgw1!~swold@> has quit IRC15:41
*** Argylelabcoat <Argylelabcoat!> has joined #yocto15:42
*** ed21 <ed21!Adium@nat/intel/x-vxqrbabqmxiorwlq> has quit IRC15:45
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC15:46
*** zero_note <zero_note!> has joined #yocto15:48
*** Bunio_FH <Bunio_FH!> has joined #yocto15:49
*** armpit <armpit!~armpit@2601:202:4001:9ea0:2c7f:421f:20ad:ca14> has quit IRC15:49
*** jku <jku!> has joined #yocto15:50
*** smagnani <smagnani!> has joined #yocto15:50
*** learningc <learningc!> has quit IRC15:51
*** jku_ <jku_!> has quit IRC15:52
*** sgw <sgw!~swold@> has joined #yocto15:52
sveinsewow, bitbake --parse-only when using multiconfig is *extremely* slow. Like 15 minutes or so for 3 configurations15:55
andycooperI've also found multiconfig to be extremely slow to parse and initialize tasks. it seems to take more than n times longer than non-multiconfig but I haven't timed it to confirm15:59
kergothsveinse: yikes16:00
kergothram usage issue? pushing into swap due to the memory usage of the parsing threads?16:00
* kergoth shrugs16:00
*** armpit <armpit!~armpit@2601:202:4001:9ea0:d548:d1b6:641d:9c1c> has joined #yocto16:02
sveinsekergoth: no, doesn't look like it. I have plenty phy ram left16:03
sveinsekergoth: now it is stuck at parsing recipes: 0%. One Cooker process eating 100% CPU. The rest is idle16:03
*** jku <jku!> has quit IRC16:05
*** Bunio_FH <Bunio_FH!> has quit IRC16:06
*** Bunio_FH <Bunio_FH!> has joined #yocto16:07
sveinseAt this point, I'm not really sure it saves times to use multiconfig vs running bitbake three times with different MACHINE settings. I have to benchmark it16:09
sveinseThe beauty of multiconfig is that you get one progress to relate to, not three in a row16:10
kergothagreed, i think the main advantage is being able to store the multiconfigs in source control in a declarative fashion rather than hacking on a shell script, for your automated builds16:10
kergoththat's a fair point16:10
sveinsekergoth: are you the maintainer for the multiconfig?16:13
*** gtristan <gtristan!~tristanva@> has quit IRC16:13
kergothnope. one of the folks with bitbake expertise, but only just starting to poke at multiconfig recently16:13
kergothRP is the maintainer of it16:13
rburtonandycooper, sveinse: definitely worth filing a bug if you can make a minimal reproducer against oe-core. probably a bad algorithm doing far too much work.16:15
*** toscalix <toscalix!~toscalix@> has joined #yocto16:15
sveinserburton: yes, I'll see if I can boil this down16:16
*** dave0x6d <dave0x6d!uid190567@gateway/web/> has joined #yocto16:16
sveinseWhat is good generic MACHINE to use that does not rely on specific BSP or hardware?16:16
yoctiNew news from stackoverflow: aarch64-poky-linux-gcc: error: : No such file or directory <>16:19
rburtonsveinse: qemu*?16:19
sveinserburton: ok, thanks. I'll try to use them for my example16:19
*** nathani_ <nathani_!> has quit IRC16:21
*** nathani_ <nathani_!> has joined #yocto16:21
zero_notehi guys, following I've added (above others) qtwebengine-plugins to my sdk (I'm on morty) and all goes fine. After a while I move to another machine with the same yocto configuration, pulled my layer (upstream commits consist mainly of the qtwebengine stuff added to the sdk), and rebuild the sdk. Surprisingly16:26
zero_notethe do_populate_sdk task failed complaining about the missing qtwebengine-plugins package16:26
zero_noteusing oe-pkgdata-util list-pkgs | grep qtwebengine16:27
zero_notein the machine where the populate_sdk task failed, the qtwebengine-plugins is missed from grepped list16:29
RPsveinse: parsing shouldn't hang like that :(16:30
RPsveinse: multiconfig has pros and cons. I'm pleased we have it but I think it highlights there are some performance issues we need to look at if we want to scale builds like that16:30
sveinseRP: Yeah, I'll see if I can look into and see what I can help with16:31
zero_notewhile on the other machine it was not. Using devshell on qtwebengine package, I see that on the machine where the task failed the package-split/qtwebengine-plugins directory is empty. Any clues about that? thanks in advance16:32
*** gtristan <gtristan!~tristanva@> has joined #yocto16:32
rburtonarmpit: your glibc CVE patches don't apply to khem's glibc upgrade (see ross/mut2), can you see if they've been upstreamed and/or rebase?16:33
armpitrburton, I suspected that might happen. the fun part is going to ID what glib version.. Master and Rocko are on the same version but different source bases16:35
armpitcan we bump the PR for the master version?16:36
armpit.1 or something. its going to confuse folks16:36
armpituntil 2.27 is adopted16:37
armpitdo you recall if the hash is part of the PV ?16:38
armpitrburton, if I recall the commits are after the point Khem is referencing.16:40
*** top22 <top22!540ed2b2@gateway/web/freenode/ip.> has joined #yocto16:40
rburtonok.  they don't apply to the source then16:40
rburtonpatching file posix/glob.c16:40
rburtonHunk #1 FAILED at 843.16:40
armpitI will have to respin against mut2.16:41
rburtonjust pushed a minor update to it16:41
top22Hello, I'm using the morty version of yocto and I'm trying to build an image for an x64 hardware on a x64 host (I'm using archlinux on the host computer). The build fails when installing glibc. Do you have any idea what could be wrong ?16:41
rburtonarmpit: trying to consolidate all the toolchain changes so they all land at once16:41
top22It says something about registers not being defined (sorry, I don't have the logs right now)16:42
rburtontop22: its probaby that the fooflip has dangled on the left flangee.  seriously, logs are essential.16:42
rburtonentirely possible that the problem is your arch has a compiler too new to build glibc from morty16:42
rburtonyou can try using our buildtools tarball to use a supported compiler instead of your host16:43
top22rburton: :D I will provide the logs as soon as I get them, probably tomorrow; thanks for the hints, I will try them16:44
*** jku <jku!> has joined #yocto16:46
*** rajm <rajm!~robertmar@> has quit IRC16:46
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC16:47
armpitrburton, how soon where you trying to do that?16:47
* armpit is seeking away from work to eat German food and beer16:48
*** mdnneo <mdnneo!~umaucher@> has quit IRC16:48
*** Guest51 <Guest51!~textual@2620:10d:c090:200::7:927f> has joined #yocto16:49
-YoctoAutoBuilder- build #1213 of nightly-mips-lsb is complete: Success [build successful] Build details are at
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto16:51
rburtonarmpit: not right now, maybe monday?16:51
armpitk. that gives me time.16:52
*** toscalix <toscalix!~toscalix@> has quit IRC16:55
*** fl0v0 <fl0v0!> has quit IRC17:01
*** martinkelly1 <martinkelly1!> has joined #yocto17:02
*** wouterstreamit <wouterstreamit!589f1708@gateway/web/freenode/ip.> has quit IRC17:04
*** vdehors_arc <vdehors_arc!> has quit IRC17:10
*** bavery_fn <bavery_fn!~bavery@> has quit IRC17:13
*** Kakounet <Kakounet!> has quit IRC17:18
*** rburton <rburton!> has quit IRC17:18
*** armpit <armpit!~armpit@2601:202:4001:9ea0:d548:d1b6:641d:9c1c> has quit IRC17:21
*** nemequ <nemequ!~nemequ@2600:8801:d100:0:91b7:cf33:d97f:785c> has quit IRC17:25
*** smagnani <smagnani!> has left #yocto17:33
-YoctoAutoBuilder- build #1228 of buildtools is complete: Failure [failed BuildImages BuildImages_1 BuildImages_2] Build details are at
*** Snert <Snert!> has quit IRC17:34
seebssome nice people just sent me a proposed patch for the sticky bit getting lost, it looks reasonable to me. I'm still pondering whether there's a way to make it better, but I don't immediately see one. They'll likely send it to oe-core.17:34
seebs(And I *still* don't have a clear ETA on "some free time to merge changes and fix a couple of things".)17:35
*** t0mmy <t0mmy!~tprrt@> has quit IRC17:36
-YoctoAutoBuilder- build #1255 of nightly-x86 is complete: Failure [failed Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at
*** yann <yann!~yann@> has quit IRC17:42
Guest51new to yocto. building a lib. do_compile worked. i can see all the files compiled. but i'm having issues with do_install. the error i'm getting is QA: Issue: -dev package contains non-symlink .so: mylib-dev path: <some path>/ Did a lot of searching online but didn't find an answer. What is the problem? (obviously it is the .so file). How do I fix it?17:44
*** Guest51 is now known as flashburn17:44
*** Snert <Snert!> has joined #yocto17:45
*** bavery_fn <bavery_fn!~bavery@> has joined #yocto17:47
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC17:50
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto17:50
*** sagner <sagner!~ags@> has quit IRC18:01
*** thaytan <thaytan!> has quit IRC18:05
*** thaytan <thaytan!> has joined #yocto18:06
*** CTtpollard <CTtpollard!~CTtpollar@> has quit IRC18:07
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:95b5:299d:3e5a:3222> has joined #yocto18:08
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC18:09
*** zero_note <zero_note!> has quit IRC18:09
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto18:10
flashburnnew to yocto. trying to build a library, but running into issues. getting an error, -dev package contains non-symlink .so: mylib-dev path: <some path>/ searched online but didn't find an answer on how to fix it. can someone help me out?18:12
*** peacememories <peacememories!> has quit IRC18:20
*** pohly <pohly!> has quit IRC18:21
*** rcw <rcw!> has quit IRC18:23
*** rcw <rcw!> has joined #yocto18:24
*** dave0x6d <dave0x6d!uid190567@gateway/web/> has quit IRC18:25
kergothflashburn: you aren't setting the SONAME correctly to version the library. the convention is which is symlinked to (which is its soname), andt here's a symlink used to link when developing. which is why ends up in the -dev package.18:26
*** diembed <diembed!> has quit IRC18:26
*** BubuIIC <BubuIIC!~mhoffmann@2003:a:772:9200:5748:f262:e193:b5c1> has quit IRC18:38
flashburnkergoth: thanks for the reply. given that i have never done this before, i feel like i'm missing a big chunk of information. when my library was built (i used a makefile that was given to me), I got the following output: (actual file), -> (link to the library) and -> (another link). I'm not quite sure what value to use for SONAME. would you mind helping out?18:38
*** stephano <stephano!~stephano@> has joined #yocto18:41
*** peacememories <peacememories!> has joined #yocto18:41
kergothif you're getting that error indicating the .so isn't a symlink, then clearly it's not a symlink. if it was after the make, but isn't after the make install, then you'll need to fix the makefile to install them properly without resolving the symlink18:47
yoctiNew news from stackoverflow: Upgrade to yocto 2.4 vmdk is no longer a image type <>18:49
*** zerus <zerus!> has quit IRC18:50
flashburnkergoth: I see. thanks.18:51
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC18:58
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto19:08
*** BubuIIC <BubuIIC!> has joined #yocto19:08
*** peacememories <peacememories!> has quit IRC19:12
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has joined #yocto19:16
flashburnnew to yocto. reading through, about libdir. confused if it is a variable since is it used as ${libdir} or it is a name of a check used by QA. can someone help me out?19:17
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC19:19
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:95b5:299d:3e5a:3222> has quit IRC19:19
*** peacememories <peacememories!> has joined #yocto19:20
*** joshuagl <joshuagl!joshuagl@nat/intel/x-kdnqsjqkxvrozlmp> has quit IRC19:24
kanavinflashburn: you can perhaps clear up the confusion by reading insane.bbclass itself?19:26
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC19:29
*** bluelightning <bluelightning!> has joined #yocto19:32
*** bluelightning <bluelightning!> has quit IRC19:32
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:32
*** dave0x6d <dave0x6d!uid190567@gateway/web/> has joined #yocto19:32
kergothflashburn: the answer is yes.19:36
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto19:37
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC19:37
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC19:41
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto19:43
*** armpit <armpit!> has joined #yocto19:46
flashburnkergoth: do you mean it is both, a check and a variable?19:49
*** luneff <luneff!~yury@> has joined #yocto19:54
*** yann <yann!> has joined #yocto19:58
*** peacememories <peacememories!> has quit IRC20:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:12
*** AndersD <AndersD!> has joined #yocto20:13
*** aragua__ <aragua__!> has quit IRC20:14
*** bluelightning <bluelightning!> has joined #yocto20:15
*** bluelightning <bluelightning!> has quit IRC20:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:15
*** Bunio_FH <Bunio_FH!> has quit IRC20:16
*** peacememories <peacememories!> has joined #yocto20:16
khemarmpit: ping?20:24
khemare you using master-next for aggregating patches or something else for meta-openembedded20:24
khemarmpit: usually, I test mastet-next which Martin was using for aggregation20:25
khemand will run bunch of builds myself20:25
khemits fine if you are using some other repo or branch I just need to know20:26
*** kpo_ <kpo_!> has joined #yocto20:30
*** BubuIIC <BubuIIC!> has quit IRC20:32
*** Crofton <Crofton!> has quit IRC20:32
*** AndersD <AndersD!> has quit IRC20:34
*** Willy-- <Willy--!8eb15cbf@gateway/web/freenode/ip.> has quit IRC20:40
*** learningc <learningc!> has joined #yocto20:41
*** learningc <learningc!> has quit IRC20:44
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC20:48
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto20:58
*** stephano <stephano!~stephano@> has quit IRC21:02
*** lty <lty!> has joined #yocto21:05
*** stephano <stephano!stephano@nat/intel/x-kjfkyvyzmkohfpfw> has joined #yocto21:10
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has joined #yocto21:14
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC21:14
yoctiNew news from stackoverflow: Unique ID of embedded system running Yocto <>21:20
*** flashburn <flashburn!~textual@2620:10d:c090:200::7:927f> has quit IRC21:21
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto21:23
nayfeseriously yocti, i need better questions! :D21:23
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:23
*** kuneco <kuneco!~kuneco@> has quit IRC21:23
*** marka <marka!~masselst@> has quit IRC21:23
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:24
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:26
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:26
*** lty <lty!> has quit IRC21:29
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:31
*** kuneco <kuneco!~kuneco@> has joined #yocto21:38
*** WillMiles <WillMiles!~Will@> has joined #yocto21:41
*** martinkelly1 <martinkelly1!> has quit IRC21:42
*** stephano <stephano!stephano@nat/intel/x-kjfkyvyzmkohfpfw> has quit IRC21:42
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC21:44
*** batman_ <batman_!95c73efe@gateway/web/freenode/ip.> has joined #yocto21:46
batman_What would be a use case for the publish option when extracting the esdk?21:47
bluelightningbatman_: on the command line? it's internal, it's used by the oe-publish-sdk script which sets up the files for the server side for updating from the client21:49
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto21:49
*** Crofton <Crofton!> has joined #yocto21:49
batman_bluelightning: yes, on the command line. I see that running the esdk script with -p will not do a bitbake build and produce tmp directory. If I look at the env setup script, $CC is set to gcc inside tmp directory.21:53
batman_So I am not getting why we have a publish option and when should I use it?21:54
peacememorieshmm, i'm trying to use the samba recipe in meta-networking, and for some reason the autostart configuration isn't created (using sysv)21:57
peacememoriesthe recipe inherits update-rc.d and sets the initscript_name and initscript_params, but when i start the created image no links to are in any rc*.d folder21:57
bluelightningbatman_: you would not use that option directly, the oe-publish-sdk script uses it so that it can get just the files in the archive extracted which is what is needed for update purposes21:58
*** Guest51 <Guest51!~textual@2620:10d:c090:200::7:927f> has joined #yocto22:00
batman_bluelightning: Ah! ok. thanks!22:02
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto22:08
*** stephano <stephano!stephano@nat/intel/x-dooryuhreypeqqip> has joined #yocto22:09
*** lamego <lamego!~jose@> has quit IRC22:13
*** sjolley <sjolley!~sjolley@> has joined #yocto22:16
Guest51getting the error: on-symlink .so: mylib-dev path: <some path>/package-split/mylib-dev/usr/lib/ Original suggestion was to fix the Makefile that generates the library to point to have correct SONAME. It was done and I verified it. Unfortunately the problem still persists. Did more digging and found out that it is happening during a do_package task. did more googling but didn't find out how to fix the problem. PS. I'm still learning22:19
Guest51 Yocto.22:19
*** peacememories <peacememories!> has quit IRC22:20
*** peacememories <peacememories!> has joined #yocto22:23
*** bavery_fn <bavery_fn!~bavery@> has quit IRC22:32
*** bavery_fn <bavery_fn!~bavery@> has joined #yocto22:32
*** armpit <armpit!> has quit IRC22:36
*** martinkelly1 <martinkelly1!> has joined #yocto22:40
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC22:42
*** agust <agust!> has quit IRC22:42
*** martinkelly1 <martinkelly1!> has quit IRC22:43
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto22:44
*** SoniaLeon <SoniaLeon!~sleonbau@> has joined #yocto22:47
-YoctoAutoBuilder- build #1227 of nightly-qa-extras is complete: Failure [failed BuildImages_2 BuildImages_4 BuildImages_5 BuildImages_8 Running Sanity Tests_7] Build details are at
*** SoniaLeon <SoniaLeon!~sleonbau@> has left #yocto22:49
*** peacememories <peacememories!> has quit IRC22:49
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC22:53
*** dfaught <dfaught!> has quit IRC22:53
*** Argylelabcoat <Argylelabcoat!> has quit IRC23:00
-YoctoAutoBuilder- build #1009 of nightly-oe-selftest is complete: Failure [failed Running oe-selftest] Build details are at
*** batman_ <batman_!95c73efe@gateway/web/freenode/ip.> has quit IRC23:24
*** BubuIIC <BubuIIC!> has joined #yocto23:29
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC23:30
*** bavery_fn <bavery_fn!~bavery@> has joined #yocto23:33
*** nighty- <nighty-!> has quit IRC23:34
sum1I'm running into an issue of a native dependency not being accessible to other recipes, how do I go about troubleshooting?23:38
sum1this is in reference to protobuf recipe that has protobuf-compiler as a seperated package23:39
sum1i've tried adding "protobuf", "protobuf-compiler", "protobuf-native", "protobuf-compiler-native" to DEPENDS in the recipe that is attempting to use 'protoc' but it keeps stating command not found23:40
kergothif it needs to *run* a binary, then you have to depend on the -native recipe that builds that binary23:42
sum1I have checked the build artifact directory for protobuf and i can see protoc in image/usr/bin and package/usr/bin and packages-split/protobuf-compiler/usr/bin23:42
*** luneff <luneff!~yury@> has quit IRC23:44
sum1from reading the mega-manual i thought I should be seeing a '" in addition to '"23:45
*** Guest51 <Guest51!~textual@2620:10d:c090:200::7:927f> has quit IRC23:46
neverpanicsum1: You'll have to differentiate recipe and package namespace. For example, protobuf-compiler is a package generated by the protobuf recipe. Packages will never show up in DEPENDS, only recipes will.23:47
*** martinkelly1 <martinkelly1!~martin@> has joined #yocto23:47
neverpanicsum1: Second, while you're correct in expecting, bitbake allows you to emulate that separate recipe in most cases with some syntactic sugar by setting BBCLASSEXTEND = "native nativesdk"23:48
neverpanicThat's the case for the protobuf recipe, which is why you don't see a separate
sum1okay but if i place the recipe name in DEPENDS the same issue happens.23:48
neverpanicAdding DEPENDS = "protobuf-native" will at least provide the correct protoc. The question is whether the build system of whatever software you are building correctly finds that protoc binary.23:48
sum1hmm k, i guess I'll have to go digging why this isn't working the way i thought23:49
sum1because I assumed using DEPENDS="protobuf-native" was enough but it didn't work23:49
neverpanicwell, you'll also need protobuf itself in DEPENDS, because you're likely linking against protobuf libraries23:50
neverpanicSo if you don't have both, make sure to change that.23:50
*** anselmolsm <anselmolsm!~anselmols@> has left #yocto23:50
sum1and i'm new to yocto so i thought maybe my understanding was wrong23:50
sum1i'm pretty sure i had every variation in at the same while trying to troubleshoot last night23:51
sum1but i will attempt it again with protobuf&protobuf-native23:51
sum1s/same/same time/23:51
sum1is there a default location that native packages are "installed" into to be usable by other recipes? or is $PATH just modified?23:53
neverpanicThey're on $PATH23:54
neverpanicBut there also is a location, you'll find a variable for it in poky/meta/conf/bitbake.conf (but I don't remember its name from the top of my head now)23:54
neverpanicIf you're using CMake for your software, check the value for CMAKE_FIND_ROOT_PATH_MODE_PROGRAM; you may have to set it to BOTH (although I think that's the default)23:56
*** BubuIIC <BubuIIC!> has quit IRC23:56
sum1hmm k, that should give me a starting point to figure it out23:59
sum1thanks for your help23:59

Generated by 2.11.0 by Marius Gedminas - find it at!