Thursday, 2017-01-12

*** tlab <tlab!~tlab@> has quit IRC00:09
*** manuel_ <manuel_!~manuel@> has quit IRC00:18
*** manuel_ <manuel_!~manuel@> has joined #yocto00:25
*** sameo <sameo!~samuel@> has quit IRC00:27
*** JordonWu <JordonWu!~quassel@> has joined #yocto00:27
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has quit IRC00:27
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has joined #yocto00:28
-YoctoAutoBuilder- build #359 of nightly-musl is complete: Success [build successful] Build details are at
*** catch22_ <catch22_!~aboseley@> has quit IRC00:36
-YoctoAutoBuilder- build #1057 of nightly-arm is complete: Failure [failed Running Sanity Tests] Build details are at
*** gtristan <gtristan!~tristanva@> has quit IRC00:44
*** Snert_ <Snert_!~snert_@> has quit IRC00:56
*** nighty <nighty!> has joined #yocto01:17
*** Son_Goku <Son_Goku!~King_InuY@> has quit IRC01:27
*** bavery_fn <bavery_fn!bavery@nat/intel/x-mmdqqxixtxbvlqey> has joined #yocto01:27
*** warthog9 <warthog9!> has joined #yocto01:29
*** paulg <paulg!> has quit IRC01:32
*** gtristan <gtristan!~tristanva@> has joined #yocto01:33
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto01:35
*** bavery_fn1 <bavery_fn1!bavery@nat/intel/x-uouyxutfhxscpayl> has joined #yocto01:35
*** bavery_fn <bavery_fn!bavery@nat/intel/x-mmdqqxixtxbvlqey> has quit IRC01:36
*** manuel_ <manuel_!~manuel@> has quit IRC01:37
*** vmeson <vmeson!> has joined #yocto01:37
*** bavery_fn1 <bavery_fn1!bavery@nat/intel/x-uouyxutfhxscpayl> has quit IRC01:40
*** dmoseley1 <dmoseley1!> has quit IRC01:40
*** dmoseley <dmoseley!> has joined #yocto01:41
*** dmoseley <dmoseley!> has quit IRC01:43
*** manuel_ <manuel_!> has joined #yocto01:43
-YoctoAutoBuilder- build #1045 of nightly-ppc is complete: Failure [failed Running ESDK Sanity Tests] Build details are at
*** gtristan <gtristan!~tristanva@> has quit IRC01:46
*** gtristan <gtristan!~tristanva@> has joined #yocto01:53
*** manuel_ <manuel_!> has quit IRC01:53
*** gtristan <gtristan!~tristanva@> has quit IRC02:01
*** gtristan <gtristan!~tristanva@> has joined #yocto02:02
*** t0mmy <t0mmy!> has joined #yocto02:08
*** gtristan <gtristan!~tristanva@> has quit IRC02:08
*** nrossi <nrossi!uid193926@gateway/web/> has joined #yocto02:11
*** tlab <tlab!~tlab@> has joined #yocto02:19
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto02:19
*** manuel_ <manuel_!> has joined #yocto02:20
*** gtristan <gtristan!~tristanva@> has joined #yocto02:25
*** t0mmy <t0mmy!> has quit IRC02:29
*** t0mmy <t0mmy!> has joined #yocto02:29
*** Son_Goku <Son_Goku!> has joined #yocto02:33
*** gtristan <gtristan!~tristanva@> has quit IRC02:33
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC02:44
*** gtristan <gtristan!~tristanva@> has joined #yocto02:44
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto02:49
*** morphis_ <morphis_!> has joined #yocto02:49
*** morphis <morphis!> has quit IRC02:53
*** anselmolsm <anselmolsm!~anselmols@2601:1c0:5402:7e90:adb0:54e3:3604:dd91> has quit IRC03:02
*** adca <adca!~adca@> has quit IRC03:07
*** bananadev <bananadev!~onlyester@> has joined #yocto03:20
*** gtristan <gtristan!~tristanva@> has quit IRC03:37
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC03:44
*** gtristan <gtristan!> has joined #yocto04:17
*** nighty <nighty!> has quit IRC04:32
-YoctoAutoBuilder- build #675 of nightly-mips64 is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** nighty <nighty!> has joined #yocto04:50
*** manuel_ <manuel_!> has quit IRC04:58
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC04:59
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto04:59
*** flihp <flihp!> has quit IRC05:05
*** flihp <flihp!> has joined #yocto05:06
*** hamis <hamis!~irfan@> has joined #yocto05:28
*** JordonWu_ <JordonWu_!~quassel@> has joined #yocto05:39
-YoctoAutoBuilder- build #1052 of nightly-x86-64-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at
*** JordonWu <JordonWu!~quassel@> has quit IRC05:42
*** nighty <nighty!> has quit IRC05:43
-YoctoAutoBuilder- build #1046 of nightly-ppc is complete: Success [build successful] Build details are at
*** nighty <nighty!> has joined #yocto06:04
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC06:09
*** stephano <stephano!~stephano@> has quit IRC06:10
*** agust <agust!> has joined #yocto06:12
*** qt-x <qt-x!~Thunderbi@> has joined #yocto06:16
*** Geera <Geera!c3572ad2@gateway/web/freenode/ip.> has joined #yocto06:17
*** stephano <stephano!~stephano@> has joined #yocto06:18
*** AndersD <AndersD!~anders@> has joined #yocto06:19
*** JordonWu_ <JordonWu_!~quassel@> has quit IRC06:22
*** JordonWu <JordonWu!~quassel@> has joined #yocto06:24
GeeraHi! I have a general question for process management. I have a C++ file and execute it in boot with Yocto. I use to run a command for playing audio with GStreamer. It's working but, I need to stop this process in some cases. So I have to kill process.  How can I stop a process while its running?06:25
*** t0mmy <t0mmy!> has quit IRC06:27
LetoThe2ndGeera: the simplest option is probably to sind the process SIGTERM/SIGKILL06:31
*** Ramose <Ramose!c05e2222@gateway/web/freenode/ip.> has joined #yocto06:35
RamoseI am getting this issue ERROR: Nothing RPROVIDES 'qtwebengine'06:35
Ramosebut I have recipe file placed in meta-qt5/recipes-qt/qt506:36
Ramoseand meta-qt5 is placed in build/conf/bblayers.conf06:37
Ramosehow can I get qtwebengine gets compiled and packed into rootfs ?06:37
LetoThe2ndRamose: add it to your IMAGE_INSTALL06:41
-YoctoAutoBuilder- build #428 of nightly-checkuri is complete: Success [build successful] Build details are at
RamoseLetoThe2nd : I tried adding to build/conf/local.conf as IMAGE_INSTALL_append = " qtwebengine"06:42
Ramosebut still seeing same error messages06:42
LetoThe2ndRamose: and did you verify that it actually gets built? bitbake -e your image maybe06:43
Ramosebitbake  imagename06:43
nrossiRamose: i presume you are using a machine that supports qtwebengine? (
Ramosenrossi; Yeah its arm machine06:46
Ramosenrossi: CPU type is ARM Cortex™-A906:47
nrossiRamose: that should be fine as long as you are using the meta arm includes06:48
*** morphis_ <morphis_!> has quit IRC06:49
*** pohly <pohly!> has joined #yocto06:52
Ramosenrossi: its there in bblayers.conf also other packages like qtwebkit gets compiled06:56
Ramosebut not qtwebengine06:57
*** sid__ <sid__!3cf3f5ea@gateway/web/freenode/ip.> has joined #yocto06:57
sid__I get error when I do06:57
sid__ bitbake-layers layerindex-show-depends meta-openembedded ERROR: Cannot get BBLAYERS_LAYERINDEX_URL06:57
nrossiRamose: and if you "bitbake qtwebengine" does it build?06:58
*** agust <agust!> has quit IRC06:59
*** agust <agust!> has joined #yocto07:00
nrossiRamose: well there you go, the issue is the License. Are you setting license restrictions in your build?07:02
Ramosenrossi: sorry but how do I check it ?07:03
*** gtristan <gtristan!> has quit IRC07:03
*** kjokinie <kjokinie!~kjokinie@> has quit IRC07:04
*** kanavin_home <kanavin_home!> has quit IRC07:04
*** kanavin_home <kanavin_home!> has joined #yocto07:04
*** sid__ <sid__!3cf3f5ea@gateway/web/freenode/ip.> has left #yocto07:07
*** gtristan <gtristan!> has joined #yocto07:07
nrossiRamose: I'm not entirely familiar with all the license tools in oe. But the error you are getting is due to "INCOMPATIBLE_LICENSE". Check its value in bitbake -e07:07
*** kjokinie <kjokinie!~kjokinie@> has joined #yocto07:12
*** rubdos <rubdos!> has quit IRC07:15
GeeraLetoThe2nd: This Process ID changing in every boot up.07:15
LetoThe2ndGeera: um, so what?07:16
Ramosenrossi: bitbake -e INCOMPATIBLE_LICENSE gives me nothing07:16
nrossiRamose: also, just reading the license string in the recipe. It seems wrong, since it says "LGPL AND GPL AND BSD..." which seems odd. I would have expected something like "(LGPL AND BSD) OR GPL..."07:16
Ramosebut I could see here few things07:16
LetoThe2ndGeera: there is stuff like pidof or pgrep. still its an ugly solution.07:17
LetoThe2ndGeera: I personally would have the process open some kind of communication channel, and wait for an abort command there. then cleanly abort and close all ressources.07:17
GeeraLetoThe2nd: I'm using a C++ file for playing audio. Like system("gst-launch-1.0 ..... ") command. Some special case I need to kill process while its running.07:18
LetoThe2ndGeera: i don't get the problem.07:19
Ramosenrossi: ok, I think its getting compiled now07:23
-YoctoAutoBuilder- build #1033 of nightly-x86-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at
Ramosenrossi: just replaced the LICENSE = "LGPL-3.0 & BSD" with LICENSE = "GFDL-1.3 & BSD & (LGPL-2.1 | LGPL-3.0)"07:27
Ramosenossi: does it look ok to you ?07:27
GeeraIf I use SIGKILL command, I need to know Process ID. But I dont know the ID before boot up. I use SIGKILL command in c++ file so how can I use this command without ID? A button pressed, play audio. B button pressed, stop audio. After then if A button pressed, it must play audio again.07:27
GeeraI'm very new to Yocto, thanks for helping me.07:28
nrossiRamose: Seems fine, though I would send a patch for the layer. And also check the proper licensing agreement to be safe (if you are distributing a product with this)07:28
*** morphis <morphis!> has joined #yocto07:29
Ramosenrossi: if you like you can have mine tested-by or reported-by ;)07:30
nrossiRamose: you can submit the patch, I don't use QT stuff :P07:31
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto07:32
Ramosenrossi: sure , I love to but for better understanding I still didn't get the difference between LICENSE = "LGPL-3.0 & BSD" and LICENSE = "GFDL-1.3 & BSD & (LGPL-2.1 | LGPL-3.0)" ;(07:32
LetoThe2ndGeera: this is totally not yocto related at all. if button b is pressed, find the process id and kill it. there are ways to find process ids given some criteria, and two means i already mentioned are pidof and pgrep07:32
Ramosenrossi: I mean why did expect this "It seems wrong, since it says "LGPL AND GPL AND BSD..." which seems odd. I would have expected something like "(LGPL AND BSD) OR GPL..." " ?07:34
LetoThe2ndGeera: yet thing probably get way easier if you wouldn't call system(), but directly use the c++ api of some library to play your media07:34
Ramosenrossi: oh sorry , I mean why did *you* expect this07:36
nrossiRamose: well the AND operator implies both licenses are applied together, as in you must comply with GPL and LGPL. However that pointless, since LGPL is intended to be used in place of GPL, so i would have expected it to be GPL or LGPL.07:36
Ramosenrossi: ok, got your point .07:37
*** aV_V <aV_V!~aV_V@> has joined #yocto07:42
*** rubdos <rubdos!> has joined #yocto07:49
*** jhar <jhar!> has quit IRC07:58
*** jku <jku!~jku@> has joined #yocto08:00
*** adca <adca!~adca@> has joined #yocto08:06
*** graphiqs <graphiqs!> has joined #yocto08:09
Ramoseis there any way I can force build a package08:12
RamoseI mean need to run bitbake qtwebengine again08:12
nrossiRamose: You can use -f to force a task to run08:13
Ramosenrossi: bitbake -f qtwebengine, like this  ?08:14
Ramosenrossi: earlier when I run "bitbake qtwebengine" I got qtwebengine folder in /home/build/tmp/work/cortexa9hf-vfp-neon-mfr-linux-gnueabi08:18
Ramosenrossi: but now when I run it again I couldn't find qtwebengine folder at same path( I just deleted it after first compilation)08:19
jkuRamose: "-f" requires a specific task, like "-f -c compile" ...08:19
Ramoseok let me try this bitbake -f -c compile qtwebengine08:20
*** eduardas_m <eduardas_m!~eduardas_@> has joined #yocto08:20
*** Kakounet <Kakounet!> has joined #yocto08:20
Ramosejku: Thanks, got it again08:20
Ramosejku : but its almost empty folder08:21
Ramosejku; is it required fetch nd all that ?08:21
jkuRamose: "-c cleansstate" (and then building normally) is often useful if you want to be sure you have all the artifacts in the workdir08:22
*** rubdos <rubdos!> has quit IRC08:24
Ramosejku: ok, fine.08:24
*** rajm <rajm!> has joined #yocto08:24
*** t0mmy <t0mmy!~tprrt@> has joined #yocto08:25
jkunote that when you do "-f -ccompile recipe" it only does the compile step, not e.g. packaging (you'll have to "bitbake recipe" for the default task)08:25
*** TobSnyder <TobSnyder!> has joined #yocto08:33
*** adca <adca!~adca@> has quit IRC08:34
hundebollfrom time to time I get task-hash mismatch on do_configure in my custom linux and u-boot recipes. Any pointers on how to debug it?08:34
hundebollI been looking around in temp/run.do_configure, but nothing time-related in there08:35
*** TobSnyder <TobSnyder!> has joined #yocto08:35
nrossihundeboll: try bitbake-diffsigs, might be able to tell you what is causing the hash to change08:37
*** sameo <sameo!~samuel@> has joined #yocto08:38
*** JordonWu <JordonWu!~quassel@> has quit IRC08:39
*** fl0v0 <fl0v0!> has joined #yocto08:49
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto08:52
*** poor-man <poor-man!d97eb626@gateway/web/freenode/ip.> has joined #yocto08:56
*** jku <jku!~jku@> has quit IRC08:58
*** jku <jku!~jku@> has joined #yocto08:58
*** Biliogadafr <Biliogadafr!> has joined #yocto09:00
*** adca <adca!~adca@> has joined #yocto09:01
*** toscalix <toscalix!~toscalix@> has joined #yocto09:01
*** aV_V <aV_V!~aV_V@> has quit IRC09:08
*** rob_w <rob_w!~bob@> has joined #yocto09:08
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto09:08
-YoctoAutoBuilder- build #999 of nightly-arm-lsb is complete: Success [build successful] Build details are at
*** ziggo <ziggo!~ziggo@> has quit IRC09:16
*** joshuagl <joshuagl!joshuagl@nat/intel/x-xwrcrqgvycwvfsvp> has joined #yocto09:22
*** ziggo <ziggo!~ziggo@> has joined #yocto09:31
*** arkver <arkver!> has joined #yocto09:36
*** mirza <mirza!~mirzak@> has quit IRC09:36
*** mirza <mirza!~mirzak@> has joined #yocto09:37
*** JoiF <JoiF!~jofr@> has joined #yocto09:37
*** mirza <mirza!~mirzak@> has quit IRC09:37
*** JoiF <JoiF!~jofr@> has left #yocto09:37
*** mirza <mirza!~mirzak@> has joined #yocto09:38
*** joseppc <joseppc!> has joined #yocto09:39
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto09:39
*** toscalix <toscalix!~toscalix@> has quit IRC09:40
*** psnsilva <psnsilva!> has joined #yocto09:40
*** toscalix <toscalix!~toscalix@> has joined #yocto09:41
*** psnsilva <psnsilva!> has quit IRC09:42
*** nighty <nighty!> has quit IRC09:45
*** zeenix <zeenix!~zeenix@> has joined #yocto09:50
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto10:01
*** grma <grma!~gruberm@> has joined #yocto10:02
*** toanju <toanju!~toanju@> has joined #yocto10:06
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:14
*** ed2 <ed2!~Adium@> has joined #yocto10:15
*** CTtpollard <CTtpollard!> has quit IRC10:19
*** AndersD <AndersD!~anders@> has quit IRC10:20
*** CTtpollard <CTtpollard!> has joined #yocto10:22
*** rburton <rburton!> has joined #yocto10:24
*** rajm <rajm!> has quit IRC10:32
*** bernarrrrrrrrrrr <bernarrrrrrrrrrr!~brnrd.rdr@> has joined #yocto10:32
bernarrrrrrrrrrrhey everyone10:33
bernarrrrrrrrrrrI'm trying to use devtool to use a c library in my bbb10:33
bernarrrrrrrrrrrthis one
bernarrrrrrrrrrrbut when I run "devtool build c-periphery"10:34
bernarrrrrrrrrrrI get "OSError: [Errno 13] Permission denied: '/../dl'"10:34
*** berton <berton!~berton@> has joined #yocto10:35
*** AndersD <AndersD!> has joined #yocto10:35
*** rubdos <rubdos!~rubdos@2a02:2788:1036:172f::1> has joined #yocto10:36
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC10:37
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has quit IRC10:40
*** aV_V <aV_V!~aV_V@> has joined #yocto10:41
*** rajm <rajm!> has joined #yocto10:46
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has joined #yocto10:47
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC10:48
*** diego_r <diego_r!> has joined #yocto10:48
*** sawk <sawk!~sawk@> has joined #yocto10:50
rburton| sed: warning: failed to get security context of /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-lsb/build/build/tmp/work/i586-poky-linux/lttng-tools/2.9.3-r0/image/usr/lib/lttng-tools/ptest/tests/Makefile: No data availableinstall: failed to access ‘/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-lsb/build/build/tmp/work/i586-poky-linux/lttng-tools/2.9.3-r0/image/usr/lib/lttng-tools/ptest/tests/destructive’: No such file or dir10:55
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto10:57
* ed2 surprised that there is no way to call python function from shell function in .class11:00
-YoctoAutoBuilder- build #1000 of nightly-arm-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at
*** geoffrey_l <geoffrey_l!~geoffrey_@> has joined #yocto11:05
*** clopez <clopez!> has quit IRC11:05
-YoctoAutoBuilder- build #661 of nightly-arm64 is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** clopez <clopez!> has joined #yocto11:10
*** Geera <Geera!c3572ad2@gateway/web/freenode/ip.> has quit IRC11:12
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has quit IRC11:14
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto11:14
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC11:16
abelalrburton: ping11:16
abelalrburton: I submitted and
abelalon which I got some feedback from you11:17
abelaland then submitted and
abelalto address your comments11:18
abelalhaven't seen any movement on these since...11:18
rburtonyeah theyre in the queue11:18
abelalgreat then11:18
abelalrburton: thanks :)11:18
*** arkver <arkver!> has quit IRC11:28
*** bernarrrrrrrrrrr <bernarrrrrrrrrrr!~brnrd.rdr@> has quit IRC11:32
aV_Vguys, I need some help appending my own defconfig. I dont understand why it doesnt work, it's only an appending isnt?11:35
aV_Vappending patches doesn't work neither, throwing error moreover11:36
*** Kakounet <Kakounet!> has quit IRC11:39
-YoctoAutoBuilder- build #1036 of nightly-world is complete: Failure [failed BuildImages] Build details are at
*** arkver <arkver!~arkver@> has joined #yocto11:41
RPaV_V: what is in your extended layer layer.conf?11:45
RPaV_V: does it tell it there are bbappend files?11:45
aV_VRP: I think so.
RPaV_V: bitbake-layers show-appends can be helpful11:46
RPaV_V: looks ok...11:47
RPaV_V: try show-appends, see if yours is listed11:47
aV_VRP is there, I also checked if defconfig is set, and it doesn't. But when I build, I just dont see expected changes11:49
aV_Vit does set*11:49
*** arkver <arkver!~arkver@> has quit IRC11:49
*** Kakounet <Kakounet!> has joined #yocto11:50
RPaV_V: so bitbake linux-compulab -e | grep SRC_URI= -C 10 (or similar) shows defconfig in your SRC_URI variable?11:51
aV_Vit doesnt appear my bbappend11:54
RPaV_V: I wonder how linux_compulab sets SRC_URI11:55
RPaV_V: you could try SRC_URI_append = " file://..."11:55
RP_append is a little harder for the system to override11:55
aV_Vwill try11:56
aV_VNow appears!11:56
*** arkver <arkver!~arkver@> has joined #yocto11:56
aV_Vwill try appending patches too11:57
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC12:01
*** eengie <eengie!> has quit IRC12:02
*** JacobGadikian[m] <JacobGadikian[m]!faddatmatr@gateway/shell/> has left #yocto12:07
*** Kakounet <Kakounet!> has quit IRC12:13
*** arkver <arkver!~arkver@> has quit IRC12:14
*** ftonello <ftonello!> has joined #yocto12:18
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto12:23
RPjoshuagl: the reason loading tests is so slow is: selftest/        self.distro = get_bb_var('DISTRO')12:25
RPcan anyone spot where that is actually used?12:26
rburtonselftest/        if self.distro == 'poky-tiny':12:26
rburtonbut that can be moved12:27
*** arkver <arkver!> has joined #yocto12:28
RPrburton: hmm, my grep skills clearly failing me12:28
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC12:28
rburtonRP: its only in mut :)12:28
RPrburton: ah12:29
*** toscalix <toscalix!~toscalix@> has quit IRC12:30
rburtonpatch incoming12:30
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto12:31
RPrburton: thanks12:31
*** aurele <aurele!> has joined #yocto12:31
aurelehi everyone12:31
aureledid anyone ever heard about webrtc on yocto/openembedded?12:32
RPrburton: makes an amazing difference to loading speed12:33
*** morphis <morphis!> has quit IRC12:36
*** morphis <morphis!> has joined #yocto12:38
rburtonRP: i can imagine!12:39
rburtonaurele: do you mean, has anyone used webrt on oe?12:40
ed2RP: ross: should we cache results of get_bb_var to avoid running bitbake every time? functools.lru_cache?12:40
rburtoned2: i expect some tests read the value, write a config fragment, read the value, etc.12:41
rburtoned2: memory resident is the way forwards: just replace the bitbake -e shell call with a RPC call to bitvake12:41
RPed2: right, memory resident bitbake is the way forward for this12:42
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto12:44
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC12:44
aurelerburton, yep this could be the question, I could not find any receipe12:46
rburtonaurele: chromium?12:46
aurelerburton, , pulseaudio-8.0 can use it also, but you have to build webrtc first no?12:47
* rburton shrugs12:47
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto12:48
aurelerburton, anyhow I just read about a webrtc-audio-processing for pulseaudio12:49
aurelerburton, maybe this will be easier to get12:50
*** Kakounet <Kakounet!> has joined #yocto12:50
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC12:51
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC12:51
*** BCMM_ <BCMM_!> has joined #yocto12:51
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC12:52
*** BCMM_ <BCMM_!> has quit IRC12:52
*** BCMM_ <BCMM_!> has joined #yocto12:53
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has joined #yocto12:58
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC13:01
*** manuel_ <manuel_!> has joined #yocto13:03
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto13:03
*** rburton <rburton!> has quit IRC13:03
-YoctoAutoBuilder- build #759 of nightly-world-lsb is complete: Failure [failed BuildImages] Build details are at
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto13:06
*** bananadev <bananadev!~onlyester@> has quit IRC13:08
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto13:10
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC13:12
*** ziggo <ziggo!~ziggo@> has quit IRC13:14
*** Snert_ <Snert_!> has joined #yocto13:15
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto13:15
*** dv_ <dv_!> has quit IRC13:16
*** rodgort` <rodgort`!> has joined #yocto13:16
*** Snert <Snert!> has quit IRC13:17
*** el_robin <el_robin!> has quit IRC13:17
*** rodgort <rodgort!> has quit IRC13:17
*** brrm <brrm!> has quit IRC13:17
*** el_robin_ <el_robin_!> has joined #yocto13:17
*** florian_kc is now known as florian13:18
*** brrm <brrm!> has joined #yocto13:18
-YoctoAutoBuilder- build #791 of nightly-oe-selftest is complete: Failure [failed Running oe-selftest] Build details are at
*** dv_ <dv_!~quassel@> has joined #yocto13:22
*** JosePerez <JosePerez!~jgperezc@> has joined #yocto13:22
*** dv_ <dv_!~quassel@> has quit IRC13:22
*** dv_ <dv_!> has joined #yocto13:23
*** geoffrey_l <geoffrey_l!~geoffrey_@> has quit IRC13:24
RPed2: I could use your help in fixing wic to work with recipe specific sysroots13:24
JosePerezRP morning.. I see some reds on 2.2.1 but I did receive mail to start QA... what is the status ?13:26
ed2RP: sure, I'll be glad to help.13:26
RPJosePerez: good question, the AB auto sends that when the build completes then we need to make a decision13:28
RPJosePerez: the nightly-arm looks like a random failure we've seen before which happens rarely (smart issue), the ESDK one worries me more, I think we're missing a patch for that. The checkuri one I have a patch ready to backport13:29
RPJosePerez: not sure what to do.13:29
RPjoshuagl, armpit: any opinions?13:29
*** lamego <lamego!~jose@> has joined #yocto13:29
joshuaglhmm, that eSDK one looks interesting. There are several ERRORs then a bunch of backtraces, I wonder if later tests rely on earlier tests succeeding13:36
*** gtristan <gtristan!> has quit IRC13:36
RPjoshuagl: I;'m sure we ran into this and have fixes in master13:36
RPjoshuagl: I think it was a patch from ed213:37
joshuaglRP: oh, neat. I just checked and that test suite doesn't appear to differ between morty and master13:37
RPed2: is my recipe specific sysroots branch. If you run the wic tests there you'll see the failures that need fixing13:38
*** Talorno <Talorno!~bob@> has joined #yocto13:38
Talornohi all13:38
RPed2: the trouble is there is now no common location for wic to find the tools in :/13:38
joshuaglhmm, did we backport uninative fixes to morty?13:38
RPjoshuagl: yes :/13:38
RPjoshuagl: but not all of them13:39
RPed2: there is now a "build-sysroots" target which combines all the output back into a common sysroot and we use that for the eSDK but I'm not sure how we could make wic rely on that. The alternative is a recipe specific sysroot. build-sysroots doesn't have any dependencies13:40
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto13:42
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto13:42
*** MrBrown <MrBrown!~bob@> has joined #yocto13:43
ed2RP: currently wic gets native sysroot path from either command line or from STAGING_DIR_NATIVE13:45
ed2RP: is it enough to change this logic to get common sysroot patch instead or something more sophisticated is needed.13:46
*** Talorno <Talorno!~bob@> has quit IRC13:47
*** toscalix <toscalix!~toscalix@> has joined #yocto13:47
RPed2: there is no common sysroot path anymore13:53
RPed2: each WORKDIR has its own sysroot13:53
RPand each sysroot is constructed for a specific set of dependencies13:53
*** poor-man <poor-man!d97eb626@gateway/web/freenode/ip.> has quit IRC13:54
joshuaglRP: I see a couple of related bugs, just trying to replicate locally13:56
aV_VRP: about my issue above. Now patches applies, but not the defconfig.13:57
aV_Vthis is the original recipe:
*** AndersD <AndersD!> has quit IRC13:58
aV_Vand this is what I did
ed2RP: is there any info about recipe specific sysroots? Is wic the only tool that runs native tools?13:59
aV_VI also tried changing the machine override13:59
RPed2: There is info that I previously sent to the arch list but I've not gotten to docs yet. wic is one of the few things that does this externally, yes14:01
RPaV_V: very hard to say without looking into the includes and seeing how that kernel generates its config by default14:02
aV_Vthis is the include used
*** BCMM_ <BCMM_!> has quit IRC14:03
*** qt-x <qt-x!~Thunderbi@> has quit IRC14:03
nrossiaV_V: i think you might be getting caught by the fact that the kernel recipe uses overrides to get the path for the defconfig. And those overrides have a higher priority than no-override.14:06
*** marka <marka!~marka@> has joined #yocto14:07
aV_Vnrossi: bad news for me then :(14:08
nrossiaV_V: not really, just put your defconfig in a "cm-fx6-custom" directory and your machine should win out :)14:08
*** csanchezdll <csanchezdll!> has joined #yocto14:10 there a "common way" to realize ReadOnly embedded devices? I mean... i wanna use just an sdcard to store configuration and whatever of my custom device with yocto. I'd like to lock the internal memory of the device for data loss protection. Is there a well known procedure?14:12
aV_Vnrossi: did it, but I dint see the changes. Maybe I'm doing wrong the process to test it.14:13
aV_VWhat I do14:13
*** eluong <eluong!> has joined #yocto14:13
aV_V1. cleansstate 2. preconfig 3. menuconfig14:13
nrossiaV_V: look at the "log.do_unpack" of in the workdir of your kernel. See if its pulling defconfig from the right place14:15
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC14:17
nrossiMrBrown: have a look at
*** rburton <rburton!> has joined #yocto14:20
*** ftonello <ftonello!> has quit IRC14:21
*** ftonello <ftonello!> has joined #yocto14:22
*** nbigaouette <nbigaouette!> has quit IRC14:22
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC14:22
*** eluong <eluong!> has quit IRC14:22
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto14:23
*** eluong <eluong!> has joined #yocto14:25
aV_Vnrossi: finally, I fixed it. At first I did what u told me, I created a sub-directory containing the defconfig and patches. THe problem was that I specified that sub-directory on FILESEXTRAPATHS_prepend, but it must be on SRC_URI instead14:25
aV_Vthanks nrossi and RP :)14:25
nrossiaV_V: Well if that works for you, great :). I did however mean move defconfig to ${THISDIR/${PN}-${PV}/cm-fx6-custom/deconfig without changing anything in the recipe.14:26
ed2RP: does RECIPE_SYSROOT_NATIVE directory contains native tools that wic can call?14:28
aV_Vnrossi: yes, is what I did. Sry I'm not expressing well. I mean that I did FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}/cm-fx6-custom:" but that doesnt work14:28
aV_Vand I did SRC_URI_append_cm-fx6-custom += "file://cm-fx6-custom/defconfig"14:29
ed2RP: I think I didn't fully get what's the difference between current and recipe specific sysroots in terms of native tools. They look similar to me.14:30
*** MrBrown is now known as Talorno14:30
*** eluong <eluong!> has quit IRC14:31
*** eluong <eluong!> has joined #yocto14:32
Talornowith a little bit of shame, i discover today that wonderful resource that the Yocto Dev Manual is14:33
nrossiTalorno: wait until you discover the "mega-manual" :)14:34
Talornoyou tell me! now! :D14:35
nrossiTalorno: :D14:35
Talornonrossi, i may fall in love with you14:36
JosePerezRP joshuagl so an 2.2.1 rc2 is the option ?14:37
RPed2: yes, RECIPE_SYSROOT_NATIVE contains native tools you can call14:37
RPed2: the difference is that only things which are direct dependecies of the recipe in question are included there14:37
RPed2: so wic would have to know a specific recipe was built14:37
RPed2: if we can know that, we can just use this path14:38
RPJosePerez: I think we need to understand this eDSK failure, yes14:38
*** mckoan|away is now known as mckoan14:38
RPrburton: any thoughts on the morty eSDK failure. I'm having trouble deciding which patch caused that :/14:38
RPrburton: the fix I thought we needed from you is in14:38
* rburton looks14:39
*** nbigaouette <nbigaouette!> has joined #yocto14:40
rburtonthat output isn't very helpful is it14:40
ed2RP: currently wic complains if it doesn't find native tool and user has to build it. Is it possible to do for recipe specific native sysroot?14:40
ed2RP: do you mean that required tool can be built, but to find it wic have to look at all available recipe specific native sysroots?14:42
*** manuel_ <manuel_!> has quit IRC14:44
RPed2: perhaps we need a wic-tools recipe/target which builds a sysroot containing the tools we need?14:44
rburtonRP: odd14:44
rburtononly happened on two of the buildsets14:45
RPrburton: machines with ccache on maybe?14:45
rburtononly happened on the centos machine14:45
RPrburton: hmm14:45
rburtonbut if PATH was set correctly it should have just worked14:46
ed2RP: yes, that will work. However, those tools may be already built for other recipes. So it would impact performance, disk space, etc.14:46
joshuaglRP: rburton I reproduced locally andhave ccache, trying again with ccache removed14:47
RPed2: ah, this is where the implementation comes into play. It will reuse them, they're created from hardlinks14:48
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC14:48
*** jku <jku!~jku@> has quit IRC14:49
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto14:50
ed2RP: that's cool! ok, let's go the way you propose: let's have wic-tools or recipe for this.14:50
RPed2: that works14:50
ed2RP: great!14:51
*** gregd <gregd!~greg@> has quit IRC14:51
ed2RP: how wic should get path to wic-tools native sysroot?14:51
RPed2: It will be WORKDIR/recipe-sysroot-native14:52
*** AndersD <AndersD!> has joined #yocto14:52
ed2RP: some tools like parted are unconditional dependency, but most of tools are not always used. It depends on plugins used in wks, type of bootloader, type of partition table etc.14:53
RPed2: that is going to be more of a problem :/14:54
RPed2: the recipe would need to know which tools to build and put in this sysroot14:54
*** eluong <eluong!> has quit IRC14:54
ed2RP: generally it's not possible as it depends on wks content, that can be changed by user anytime.14:55
*** loyee <loyee!> has joined #yocto14:55
ed2RP: as a workaround we can build all possible tools.14:55
RPed2: that may be what we need to do then14:56
ed2RP: the amount is not that big.14:56
ed2RP: ok. how and when you want me to implement it in wic?14:56
ed2RP: can you point me to your branch I can play with?14:57
RPed2: I want to create a recipe system sysroot branch that works on the autobuilder including oe-selftest so I could really do with patches for my branch14:57
RPed2: I gave you a branch earlier?14:57
ed2RP: it's mentioned in your e-mail., right?14:58
*** mckoan <mckoan!~marco@unaffiliated/mckoan> has quit IRC14:58
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:59
ed2ok, thanks.14:59
RPpohly: I put a specific task event in that series too btw14:59
RPpohly: I want to better define what that event means and what such a handler should/shouldn't do15:00
ed2RP: do you want me to make wic oe-selftest pass? When?15:00
RPed2: please, sooner than later if possible15:00
*** mckoan <mckoan!~marco@unaffiliated/mckoan> has joined #yocto15:00
RPed2: the rss work is due for M215:00
*** gtristan <gtristan!> has joined #yocto15:01
pohlyRP: RecipeTaskPreProcess I suppose. I'm curious about that extended documentation and how you intend to handle potential conflicts when rm_work.bbclass adds do_rm_work in that events.15:02
pohlyAs I said in my email, I think the same ordering problem still exists, just at a smaller scale.15:02
RPpohly: I'm going to propose it *not* add/remove tasks, only change their dependencies15:02
RPpohly: basically we minimise the cross section of problem to be small enough that if it ever happens, the handlers would likely have to be taught about each other15:03
pohlyFair enough.15:04
pohlySo initially, the only user would be rm_work.bbclass?15:05
RPpohly: and my rss code15:05
ed2RP: ok. I'm finishing my work on bug #10835. After that I'll try to do that. Is it ok if I start on Monday?15:05
yoctiBug normal, Medium, 2.3 M3, eduard.bartosh, IN PROGRESS DESIGN , WIC should not rely on hddimg creation for finding all needed artifacts15:05
RPpohly: thankfully the rss code won't conflict15:05
pohlyRP: how will those two cooperate?15:05
RPpohly: they shouldn't conflict15:06
pohlyrm_work.bbclass does an "addtask do_rm_work before do_build", and in the event adds all other tasks as dependencies?15:07
RPpohly: yes15:07
RPpohly: I want the event to have a list of tasks but not the internals of __BBTASKS like it does in my branch15:07
pohlyI'm not sure what we get from requiring that do_rm_work gets added without proper dependencies - that part seems a bit overly complicated to me.15:08
*** manuel_ <manuel_!~manuel@> has joined #yocto15:09
RPpohly: it means that the list of tasks is complete when the event is fired15:09
pohlyWe do ensure that the *list* of tasks is correct at the time that the event fires, but not their dependencies - is that why?15:09
RPpohly: yes15:09
RPpohly: that seems a sane API guarantee to make now15:09
*** eduardas_m <eduardas_m!~eduardas_@> has quit IRC15:11
pohlyRP: is still needed, right?15:11
RPpohly: yes15:11
*** simfir <simfir!> has left #yocto15:12
pohlyOnce you are done with your change, will you commit it or should I test it in combination with the other rm_work related changes first?15:13
RPpohly: well, I want to make sure that what I do is going to work for rm_work as well. I'm a little buried in rss problems atm though :(15:13
pohlyJust give me a ping when you have something that I should base rm_work on. Or should I already try with the current patch?15:14
RPpohly: I don't have any plans to fundamentally change it, just docs and turn __BBTASKS into a specific tasklist15:15
RPpohly: obviously if I run onto other issues I may need to do something but I think my problems are elsewhere15:15
pohlyAs rm_work.bbclass won't use that parameter (calling instead), I might as well try it out now.15:16
*** jku <jku!> has joined #yocto15:16
joshuaglRP: ross: after removing ccache from my system testsdkext succeeds15:16
*** madisox <madisox!> has joined #yocto15:16
*** Son_Goku <Son_Goku!> has quit IRC15:17
RPjoshuagl: does imply ross' patch isn't working for some reason15:17
joshuaglRP: rburton: right :-/15:18
rburtonjoshuagl: are you replicaing on morty or master?15:19
joshuaglrburton: morty15:19
joshuaglwhich has your utils patch15:19
rburtoncan you make it dump $PATH before spawning in host_gcc_version?15:19
RPrburton: sorry, it implies the universe is broken and your patch is perfect :)15:21
rburtonthats better15:21
joshuaglrburton: PATH=/home/joshuagl/Projects/poky/scripts:/srv/builds/poky-morty/tmp/sysroots/x86_64-linux/usr/bin/x86_64-poky-linux:/srv/builds/poky-morty/tmp/sysroots/qemux86-64/usr/bin/crossscripts:/srv/builds/poky-morty/tmp/sysroots/x86_64-linux/usr/sbin:/srv/builds/poky-morty/tmp/sysroots/x86_64-linux/usr/bin:/srv/builds/poky-morty/tmp/sysroots/x86_64-linux/sbin:/srv/builds/poky-morty/tmp/sysroots/x86_64-linux/bin:/home/joshuagl/Projects/poky15:21
*** toanju <toanju!~toanju@> has quit IRC15:22
rburtonbut but but but but but15:22
rburtonthat has /usr/bin in which I presume is where you have gcc15:23
*** eduardas_m <eduardas_m!~eduardas_@> has joined #yocto15:24
joshuaglrburton: sure, but ccache is in /usr/lib64/ccach which is earlier in PATH15:24
joshuagl$ which gcc15:24
joshuagl /usr/lib64/ccache/gcc15:24
rburtondoesn't ccache skip itself when looking for the real gcc?15:25
joshuaglwith ccache installed the tests explode, with it removed the don't15:25
RPand why was oe-selftest so slow? some idiot had BBMULTICONFIG enabled. Which only broke when combined with multilib15:30
*** manuel__ <manuel__!~manuel@> has joined #yocto15:32
*** manuel_ <manuel_!~manuel@> has quit IRC15:33
*** manuel__ is now known as manuel_15:33
*** jku <jku!> has quit IRC15:33
*** manuel__ <manuel__!~manuel@> has joined #yocto15:37
*** manuel_ <manuel_!~manuel@> has quit IRC15:37
*** manuel__ is now known as manuel_15:37
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@> has joined #yocto15:38
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto15:38
*** morphis <morphis!> has quit IRC15:51
*** ntl <ntl!> has joined #yocto15:52
*** geoffrey_l <geoffrey_l!~geoffrey_@> has joined #yocto15:53
*** aehs29 <aehs29!~aehernan@> has joined #yocto15:54
*** morphis <morphis!> has joined #yocto15:54
*** armpit <armpit!~akuster@2601:202:4001:9ea0:ea2a:eaff:fe0e:629e> has quit IRC15:57
*** AndersD <AndersD!> has quit IRC16:00
*** morphis <morphis!> has quit IRC16:03
*** morphis <morphis!> has joined #yocto16:05
*** csanchezdll <csanchezdll!> has left #yocto16:05
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:07
*** armpit <armpit!~akuster@2601:202:4001:9ea0:ea2a:eaff:fe0e:629e> has joined #yocto16:09
*** geoffrey_l <geoffrey_l!~geoffrey_@> has quit IRC16:10
*** eduardas_m <eduardas_m!~eduardas_@> has quit IRC16:13
*** manuel_ <manuel_!~manuel@> has quit IRC16:17
*** eduardas_m <eduardas_m!~eduardas_@> has joined #yocto16:18
*** mckoan is now known as mckoan|away16:19
*** eduardas_m <eduardas_m!~eduardas_@> has quit IRC16:20
*** manuel_ <manuel_!~manuel@> has joined #yocto16:24
*** bzb <bzb!> has joined #yocto16:27
*** rcw <rcw!~rwoolley@> has joined #yocto16:27
*** am55 <am55!~am55@unaffiliated/am55> has joined #yocto16:28
*** alimon <alimon!alimon@nat/intel/x-mvisbgockqgdsyza> has quit IRC16:29
*** anselmolsm <anselmolsm!~anselmols@2601:1c0:5402:7e90:2388:4a58:59f3:e0ee> has joined #yocto16:30
*** anselmolsm <anselmolsm!~anselmols@2601:1c0:5402:7e90:2388:4a58:59f3:e0ee> has quit IRC16:31
*** alimon <alimon!~alimon@> has joined #yocto16:32
*** hamis <hamis!~irfan@> has quit IRC16:34
*** aV_V <aV_V!~aV_V@> has quit IRC16:45
*** rstreif <rstreif!> has joined #yocto16:46
*** zeenix <zeenix!~zeenix@> has quit IRC16:48
*** rajm <rajm!> has quit IRC16:52
Talornohey guys! i'm trying to hard to change the psplash boot image.... created the image using the script, changed it [i am using core psplash recipe, i know it's not a very good practice but it should work in any case], cleaned psplash, baked all again... nothing, the yocto image is still proudly here :D Is there something that i don't know?16:52
Talornolet's say a maximum image size that if overheaded makes it not working? or anything similar?16:52
kergothI'd make sure you aren't accidentally flashing an old image binary or something16:53
rburtonTalorno: if you have poky then be aware that meta-poky (or meta-yocto if you have an old release) is appending its own image16:53
Talornoit's the fresh image16:53
rburtonand that will probably override yours16:53
Talornorburton, i am modifying core psplash16:54
Talornooh crap...another psplash recipe :D16:55
kergothgood call, rburton16:55
*** bluelightning <bluelightning!~paul@> has joined #yocto16:56
*** bluelightning <bluelightning!~paul@> has quit IRC16:56
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:56
*** Snert__ <Snert__!~snert_@> has joined #yocto16:57
*** qt-x <qt-x!~Thunderbi@> has joined #yocto16:59
rburtonTalorno: poky is for testing really, i recommend you make your own distro instead of using poky.  feel free to copy poky.conf as a starting point.17:00
Talornoi swapped the file in the recipe dir but now it doesn't bitbake anymore :D17:01
RPyocti: praise rburton17:01
yoctiRP: Error: There are no praises in my database for #yocto.17:01
RPah well :)17:02
rburtonhow does one add praises17:02
*** fl0v0 <fl0v0!> has quit IRC17:03
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC17:04
*** Snert___ <Snert___!~snert_@> has joined #yocto17:07
*** Snert__ <Snert__!~snert_@> has quit IRC17:07
*** gabrbedd <gabrbedd!> has quit IRC17:07
*** gabrbedd <gabrbedd!> has joined #yocto17:09
*** georgem <georgem!> has quit IRC17:10
*** lexano <lexano!> has quit IRC17:10
*** georgem <georgem!> has joined #yocto17:11
*** lexano <lexano!> has joined #yocto17:11
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC17:11
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC17:13
Talornooh.. nice.. i had to add "POKY" at the start of each variable name in the .h .... i generated it using the script, though17:15
*** rewitt <rewitt!~rewitt@> has quit IRC17:20
*** rewitt <rewitt!~rewitt@> has joined #yocto17:20
*** manuel_ <manuel_!~manuel@> has quit IRC17:23
Talornothanks for the hints, guys! gotta go17:26
*** Talorno <Talorno!~bob@> has quit IRC17:26
*** Kakounet <Kakounet!> has quit IRC17:27
*** rewitt <rewitt!~rewitt@> has quit IRC17:30
*** rewitt <rewitt!~rewitt@> has joined #yocto17:30
*** grma <grma!~gruberm@> has quit IRC17:31
*** manuel_ <manuel_!~manuel@> has joined #yocto17:31
RPyocti: rburton++17:35
*** todor <todor!~todor@> has joined #yocto17:41
*** qt-x <qt-x!~Thunderbi@> has quit IRC17:44
-YoctoAutoBuilder- build #429 of nightly-checkuri is complete: Failure [failed BuildImages] Build details are at
rburtonyocti: YoctoAutoBuilder--17:47
*** aehs29 <aehs29!~aehernan@> has quit IRC17:49
*** todor <todor!~todor@> has left #yocto17:51
*** todor <todor!~todor@> has joined #yocto17:52
*** TobSnyder <TobSnyder!> has quit IRC17:52
*** todor <todor!~todor@> has left #yocto17:52
*** todor <todor!todor@nat/intel/x-qtfvqmcdgkvbixxp> has joined #yocto17:52
*** Snert___ is now known as Snert__17:56
*** Snert__ is now known as Smert17:56
*** Smert is now known as Snert17:56
*** kalpu <kalpu!> has joined #yocto17:58
*** todor <todor!todor@nat/intel/x-qtfvqmcdgkvbixxp> has quit IRC17:58
*** todor <todor!~todor@> has joined #yocto17:58
kalpuHi, in my finale image there is the file /etc/network/interfaces - I want to change this to my own but don't know from which recipie this file is coming. How to solve this? Is there a tool to find out?17:59
*** todor <todor!~todor@> has left #yocto17:59
*** todor <todor!todor@nat/intel/x-zvyqnrtkukkfaumj> has joined #yocto17:59
davisanybody have any problems with selinux setfile segfaulting because it can not locate strcmp-sse2-unaligned.S18:00
*** aehs29 <aehs29!~aehernan@> has joined #yocto18:01
*** armpit <armpit!~akuster@2601:202:4001:9ea0:ea2a:eaff:fe0e:629e> has quit IRC18:01
*** gtristan <gtristan!> has quit IRC18:03
*** graphiqs <graphiqs!> has quit IRC18:03
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto18:05
-YoctoAutoBuilder- build #1037 of nightly-world is complete: Success [build successful] Build details are at
*** CTtpollard <CTtpollard!> has quit IRC18:11
*** ftonello <ftonello!> has quit IRC18:13
-YoctoAutoBuilder- build #760 of nightly-world-lsb is complete: Success [build successful] Build details are at
*** gtristan <gtristan!> has joined #yocto18:18
kalpuHow to find the package from where the file in the root-filesystem is coming?18:19
*** dv_ <dv_!> has quit IRC18:19
*** _dv_ <_dv_!> has joined #yocto18:19
kergothkalpu: oe-pkgdata-util18:19
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto18:30
-YoctoAutoBuilder- build #1035 of nightly-x86-lsb is complete: Success [build successful] Build details are at
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC18:41
*** t0mmy <t0mmy!~tprrt@> has quit IRC18:41
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto18:45
*** bzb <bzb!> has quit IRC18:48
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC18:57
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto18:59
*** toscalix <toscalix!~toscalix@> has quit IRC19:04
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto19:07
*** morphis <morphis!> has quit IRC19:14
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC19:15
*** kalpu <kalpu!> has left #yocto19:22
*** paulg <paulg!> has joined #yocto19:22
*** jamesp <jamesp!~jamesp@> has joined #yocto19:31
*** toanju <toanju!> has joined #yocto19:36
*** toanju <toanju!> has quit IRC19:40
*** morphis <morphis!> has joined #yocto19:46
*** armpit <armpit!> has joined #yocto19:57
*** gattuso <gattuso!> has quit IRC19:58
*** JaMa <JaMa!~martin@> has joined #yocto19:59
*** gattuso <gattuso!> has joined #yocto19:59
*** embexus <embexus!05bbc083@gateway/web/freenode/ip.> has joined #yocto20:00
*** paulg <paulg!> has quit IRC20:02
embexusAnyway to override machine conf settings of a bsp layer within my layer ?20:02
bluelightningembexus: if your layer is a distro layer with a conf/distro/something.conf and that's what you're pointing to in DISTRO, yes20:03
embexusyes it is a distro layer20:03
embexushowever I'm trying to override different machines conf20:03
kergothit's usually not a good idea unless there's no other option, though. admittedly there are cases where that's true, i.e. hardware that's expandable, but whose bsp maintainer forgot to include e.g. vfat in MACHINE_FEATURES20:03
embexusI created machine/conf/ in my distro layer20:04
bluelightningembexus: you can use machine overrides i.e. VARNAME_machinename = "value"20:04
kergothfirst, there's no such thing as machine/conf/, but beyond that, you don't want to override the entire machine, only a variable20:04
embexusThe only way I figured out which is working is to use another machine name and override20:05
embexusexample for raspberrypi.conf20:05
embexusI created machine/conf/rpi.conf20:05
embexusMACHINEOVERRIDES = "raspberrypi:${MACHINE}" require conf/machine/raspberrypi.conf20:06
embexusthen I could set my overrides20:06
kergoththat's excessive if all you need to do is adjust a variable or two. it's a valid option if you need to deviate heavily, though20:06
bluelightningembexus: why don't you do what I suggested?20:06
embexushowever I want to keep the same name20:06
embexusbecause I want to keep changes of each machine in separate files20:07
kergothyour only options to keep the changes isolated are to override at a var level in your distro, add new config files your distro includes (i.e. conf/distro/yourdistro/machineoveriddes/${MACHINE}.conf) or use new machines. take your pick20:08
kergothat mentor we use a different option, which i'm not 100% happy with, but it only works because we use custom setup scripts.20:08
bluelightningyou could use separate inc files if it's just separate files you want20:08
kergothalso if your changes are *fixes*, submit them upstream, don't hold onto them indefinitely20:09
embexusI was thinking that yocto is providing such mechanisms20:09
kergothyou're intentionally deviating from one of the core oe/yocto principles. machine, distro, and image are orthogonal. to have specifics of one in another crosses those boundaries in a way we prefer to avoid.20:11
kergothsometimes necessary, but i doubt anyone wants to make it easy to do20:11
kergothIMO, anyway20:11
*** morphis <morphis!> has quit IRC20:12
*** nrossi <nrossi!uid193926@gateway/web/> has quit IRC20:13
*** embexus <embexus!05bbc083@gateway/web/freenode/ip.> has quit IRC20:13
*** berton <berton!~berton@> has quit IRC20:18
khemrburton: there ?20:22
*** sameo <sameo!~samuel@> has quit IRC20:23
mattsmI'm in the fun position of comparing two different OE based products and reconciling the differences.. any new tools added to bitbake or poky for this? For now I'm going to try to use bitbake-layers show-appends/show-recipes and try to account for differences that way... just wondering if anyone else has any ideas20:24
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC20:26
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto20:27
kergothmattsm: buildhistory, bitbake -S printdiff, bitbake-whatchanged, bitbake -g, ..20:27
kergothcan also compare image manifests, etc20:28
mattsmkergoth: was looking at manifests for sure20:28
mattsmkergoth: i wonder how some of these will work with different oe-core releases too (forgot to mention that)20:28
kergothgood luck20:28
*** paulg <paulg!> has joined #yocto20:29
kergothworst case you'll have to resort to comparing file by file on disk20:29
mattsmkergoth: my plan is to scan for bbappends per package and recreate them in the new build..20:31
mattsmand hopefully the base packages are sane and debug from there20:31
khemare they based on same base release of OE/yocto ?20:31
kergoth[13:28:44]  <mattsm>kergoth: i wonder how some of these will work with different oe-core releases too (forgot to mention that)20:32
kergothdoesn't seem like it20:32
*** ed2 <ed2!~Adium@> has quit IRC20:32
khemif they are different releases then you can start with version comparisions that buildhistory spits out for image build20:33
khemthat will give you comprehensive list of package version differences20:33
khemrburton: I dont see in your mut, this is needed for rpi to work with gst 1.10.x20:35
kergothRP: do we have current performance numbers on before/after the switch to rss?20:45
rburtonkhem: done20:48
*** willdye <willdye!> has quit IRC20:52
*** hbruce <hbruce!~hbruce@> has joined #yocto20:54
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC20:57
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto20:59
*** manuel__ <manuel__!~manuel@> has joined #yocto21:02
*** manuel_ <manuel_!~manuel@> has quit IRC21:03
*** manuel__ is now known as manuel_21:03
RPkergoth: no, not yet21:06
RPkergoth: we have a patchset that mostly works so that is one of the next steps21:07
* kergoth nods21:07
kergothhaven't had a chance to even review it or test it yet, looking to do that soon finally21:07
kergothglad to hear it's coming along nicely21:07
RPkergoth: I've been trying to fix failures oe-selftest was finding. I know wic is currently bust with it as the sysroot it looks for tools in no longer exists21:08
RPkergoth: other than that, I'm waiting on my next test run to see how it looks. oe-selftest was around 25% failure but I'm hoping I've fixed the cause of most of that21:08
*** rcw <rcw!~rwoolley@> has quit IRC21:21
*** sveinse <sveinse!> has joined #yocto21:32
sveinseAny people hanging out here now? When I'm building using SSTATE_DIR and when I'm not, I'm getting different results in the output image. libanthy is missing from the former (located in meta-openembedded/meta-oe/recipes-support/anthy). Why can this be? Can't we trust SSTATE_DIR for building release images?21:35
*** marka <marka!~marka@> has quit IRC21:39
* kergoth and his company and every other dev int he company do builds from sstate every day, as do many others21:41
* sveinse depends on sstate because he has too little time21:42
*** pohly <pohly!> has quit IRC21:44
paulgsveinse, define "missing"  --- as in missing from tmp/work/*   or from the manifest and the rootfs image(s) ?21:49
sveinsepaulg: Missing from the rootfs image21:49
sveinsewhere can I find the manifest?21:49
paulgit is in the same dir -- tmp/deploy/images21:49
RPkergoth: please report or fix that one!21:57
RPsveinse: we do take such bugs seriously, we do all want to rely on sstate and do21:58
kergoth:) will do. i'm guessing somewhere it caught the error message in stdout rather than stderr and didn't handle the wrong exit code, or something.21:58
RPkergoth: yes, looks something like that21:58
sveinseRP: I'm rebuilding now to be able to compare side-by-side sstate-based build with non-sstate build. hang on.21:59
RPsveinse: that recipe doesn't look to have sstate issues I can see just looking at it at least. It does seem to hardcode packaging I'd have expected the system to figure out but that wouldn't break things as you describe afaict22:01
RPsveinse: best thing is to compare the builds side by side. start with the rootfs and the packages and work backwards22:02
*** clsulliv_home <clsulliv_home!> has joined #yocto22:05
sveinseRP, rootfs is different, manifest is equal22:06
*** JaMa <JaMa!~martin@> has quit IRC22:07
paulgmaybe you can diff the two do_rootfs logs....22:11
sveinseI'm checking how libanthy0 is pulled into the image, and it comes from RDEPENDS_uim-anthy = "takao-fonts anthy libanthy0" in uim_1.8.6.bb22:11
sveinseok, hang on22:11
frayin an override is the '/' character permitted.. i.e.22:16
frayOVERRIDES =. "foo/bar"22:16
frayMYVARIABLE = "TRUE"22:16
frayMYVARIABLE_foo/bar = "FALSE"22:16
frayI tried that and keep getting 'TRUE' from bitbake -e22:16
fraythe system does say foo/bar is an override, but doesn't seem to be parsing it22:17
paulgfray, to be clear -- if you replace the "/" with a "-" or "_" then it just works, right?22:17
frayIt appears to with '-' yes..22:18
sveinseRP, the logs seems at first glance very similar, with the exception that the non-sstate build contains a "NOTE: Executing postinstall for package: libanthy0 ..." and subsequently listing its files22:18
frayI thoguht '/' was going to work because of the virtual providers ands uch we have..22:18
*** manuel_ <manuel_!~manuel@> has quit IRC22:23
*** manuel_ <manuel_!~manuel@> has joined #yocto22:28
sveinseRP, just reverified, the only difference in the log.do_rootfs files are that the executing postinstall for package libanthy0 message...22:37
sveinseso where do I go from here?22:37
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto22:39
*** manuel_ <manuel_!~manuel@> has quit IRC22:40
*** manuel_ <manuel_!~manuel@> has joined #yocto22:42
kergothsveinse: if both filesystems are installing the same packages, then i'd start comparing package contents.22:43
kergothbuildhistory would be easiest, but oe-pkgdata-util would work as well22:43
sveinsekergoth: yeah, except buildhistory for the sstate enabled build is empty, since it retrieves it from the cache22:45
kergothyou know the package in question, use oe-pkgdata-util to dump its contents, or examine the binary package directly22:46
bluelightningsveinse: that's not supposed to be the case in current versions...22:46
*** arkver <arkver!> has quit IRC22:47
sveinseThe libanthy0_9100h-r0_armel.deb seems equal beween the two builds22:48
*** hbruce <hbruce!~hbruce@> has quit IRC22:51
sveinseso why is the manifest equal, but the image nor the log.do_rootfs is not. Postinstall is not run. Why Is that I wonder...22:52
*** JosePerez <JosePerez!~jgperezc@> has quit IRC22:52
*** rstreif <rstreif!> has quit IRC22:56
*** fmeerkoetter <fmeerkoetter!> has quit IRC23:01
*** bfederau <bfederau!> has quit IRC23:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** lamego <lamego!~jose@> has quit IRC23:09
*** ntl <ntl!> has quit IRC23:11
rburtonargh byacc failed for arm-lsb again23:15
rburton <— if anyone is bored :)23:15
*** aehs29 <aehs29!~aehernan@> has left #yocto23:21
*** manuel_ <manuel_!~manuel@> has quit IRC23:24
*** ftonello <ftonello!> has joined #yocto23:25
*** ftonello <ftonello!> has quit IRC23:33
sveinsewhat is the command to see what variable poky uses to compare with the sstate cache?23:37
*** manuel_ <manuel_!> has joined #yocto23:39
*** hbruce <hbruce!~hbruce@> has joined #yocto23:39
sveinseI've found that uim-common is different from the sstate cache build and the non-sstate cache build23:41
sveinseWe've had problems with the uim recipe before. E.g. we had to disable parallel install PARALLEL_MAKEINST = ""23:42
sveinseNow, the interesting thing is why poky does not detect the difference between the version in the cache and the local recipe23:42
sveinsePerhaps uim build isn't deterministic?23:45
*** joshuagl <joshuagl!joshuagl@nat/intel/x-xwrcrqgvycwvfsvp> has quit IRC23:47
*** rburton <rburton!> has quit IRC23:47
sveinseIt uses m4 and configure. And poky don't have isolated sysroot, right? So can uim's confiure pickup something else due to something being installed or missing from the sysroot. poky would get it's package and ship it off to the sstate cache. Next time around the recipe is the same, hence the sstate can be used, but in reality it's missing something? (puuh)23:48
sveinseFar fetch, I know23:48
*** agust <agust!> has quit IRC23:49
*** dvhart <dvhart!> has joined #yocto23:58

Generated by 2.11.0 by Marius Gedminas - find it at!