Monday, 2015-07-06

*** tismith_ <tismith_!~toby@> has quit IRC00:33
*** ambrosius <ambrosius!> has joined #yocto00:33
*** abelloni <abelloni!> has quit IRC01:13
*** tismith <tismith!~toby@> has joined #yocto01:33
*** destrudo <destrudo!~destrudo@> has joined #yocto01:36
*** ambrosius <ambrosius!> has quit IRC01:42
*** tismith <tismith!~toby@> has quit IRC01:42
*** tismith <tismith!~toby@> has joined #yocto01:44
*** lyang0 <lyang0!~lyang001@> has quit IRC01:49
*** lyang0 <lyang0!~lyang001@> has joined #yocto01:50
*** _dv_ <_dv_!> has joined #yocto02:39
*** dv_ <dv_!> has quit IRC02:40
*** tismith <tismith!~toby@> has quit IRC02:50
*** varibull__ <varibull__!> has quit IRC03:52
*** varibull__ <varibull__!> has joined #yocto03:52
*** nemequ <nemequ!> has quit IRC04:41
*** tismith <tismith!~toby@> has joined #yocto05:14
*** [Sno] <[Sno]!> has quit IRC05:23
*** ambrosius <ambrosius!> has joined #yocto05:24
*** _dv_ is now known as dv_05:30
*** nemequ <nemequ!> has joined #yocto05:31
*** nemequ <nemequ!> has quit IRC05:36
*** frsc <frsc!~frsc@> has joined #yocto05:54
*** AndersD <AndersD!> has joined #yocto05:57
*** abelloni <abelloni!> has joined #yocto06:06
*** frsc <frsc!~frsc@> has quit IRC06:07
*** frsc <frsc!~frsc@> has joined #yocto06:08
*** wadim_ <wadim_!> has joined #yocto06:18
*** wadim_1 <wadim_1!> has joined #yocto06:18
*** zecke <zecke!> has joined #yocto06:23
*** grma <grma!> has joined #yocto06:26
*** jku <jku!jku@nat/intel/x-diuqwmvsxgsvivvl> has joined #yocto06:27
*** wadim_ <wadim_!> has quit IRC06:32
*** TobSnyder <TobSnyder!> has joined #yocto06:48
*** hitlin37 <hitlin37!uid16371@gateway/web/> has joined #yocto06:53
*** nighty-_ <nighty-_!> has joined #yocto07:01
*** Ox4 <Ox4!~user@unaffiliated/zloy> has quit IRC07:15
*** ambrosius <ambrosius!> has quit IRC07:25
*** [Sno] <[Sno]!> has joined #yocto07:32
*** mckoan|away is now known as mckoan07:33
mckoangood morning07:34
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto07:35
*** jbrianceau_away is now known as jbrianceau07:35
*** pohly <pohly!> has joined #yocto07:36
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto07:37
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto07:37
*** varibull__ <varibull__!> has quit IRC07:41
*** varibull__ <varibull__!> has joined #yocto07:41
*** sameo <sameo!~samuel@> has joined #yocto07:43
*** nicolas_ <nicolas_!58a61e6b@gateway/web/freenode/ip.> has joined #yocto07:47
*** laurent1 is now known as gourvy07:51
*** gourvy is now known as gourve_l07:51
*** roric <roric!~roric@> has joined #yocto07:53
*** cristianiorga <cristianiorga!~cristiani@> has joined #yocto07:56
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto08:07
*** dshwang <dshwang!~dshwang@> has quit IRC08:23
*** dshwang <dshwang!dshwang@nat/intel/x-oecvmkcgeextmjpu> has joined #yocto08:24
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:25
bluelightningmorning all08:26
*** jonathanmaw <jonathanmaw!> has joined #yocto08:40
*** rburton <rburton!> has joined #yocto09:01
*** belen <belen!~Adium@> has joined #yocto09:05
*** ddalex1 <ddalex1!> has quit IRC09:12
*** milan <milan!~milan@> has joined #yocto09:13
milanbluelightning: Is there any option called IMAGE_INSTALL_remove (like IMAGE_INSTALL_append) ? I want to prevent a package from installing into the rootfs temporarily via local.conf .09:16
bluelightningmilan: there's PACKAGE_EXCLUDE09:17
bluelightningmilan: but the important thing to note about that is that it will not remove dependency chains for you, so if something else depends on the thing you are trying to remove you will get an error straight away09:17
bluelightningwhich may be useful as it will at least tell you what that dependency is09:17
milanThat's fine I think for current scenario though.09:18
milanBut how can I dump in advance the list of packages to be included in final rootfs09:18
milanHave been using this .. "bitbake -g default-image && cat | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq"09:19
bluelightningcompletely in advance, you can't - the contents of the image is up to the package manager and that operation happens as part of building the image09:19
bluelightningyou can however look at how the image got constructed *after* it has been done09:19
bluelightningthe dependency graphs produced by buildhistory provide one way to track down how a package got into the image09:20
bluelightningthis manual section gives some details on how to set up buildhistory:
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-iakyrcfvrduwtltv> has joined #yocto09:26
*** ddalex <ddalex!~ddalex@> has joined #yocto09:27
*** aoibhinn <aoibhinn!uid95825@gateway/web/> has joined #yocto09:27
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:33
*** tanamo <tanamo!cb7dac02@gateway/web/freenode/ip.> has joined #yocto09:36
*** jimBaxter <jimBaxter!> has joined #yocto09:51
*** jchonig <jchonig!> has quit IRC09:52
LocutusOfBorg1Hi folks, my customer asked me to give him a list of packages and respective licenses in the target image09:53
LocutusOfBorg1do you have any bitbake command to extract them?09:53
* LocutusOfBorg1 wonders if playing with bash is the right way to do it09:53
LetoThe2ndLocutusOfBorg1: like, tmp/deploy/licenses?09:54
bluelightningright, was just about to suggest that :)09:54
bluelightningspecifically, tmp/deploy/licenses/<imagename>-<machine>-<datetime>09:55
LetoThe2ndbluelightning: hand me a red sharpie, please! first time i answered faster than you and it was even correct :)09:55
* LetoThe2nd needs to make a mark in his caldendar09:55
LocutusOfBorg1bluelightning, yes, but the problem is: how I convert that "tree" directory list in a table with "package --> license"09:56
LocutusOfBorg1excluding sh tools09:57
LetoThe2ndits a plain text file that fits the image you crated09:57
bluelightningLocutusOfBorg1: it's not a tree structure, under the directory for the image there are two files - one, the license manifest (a list of package + license) and two a plain list of packages09:57
LetoThe2ndfor tabelizing, awk/sed :)09:58
bluelightning$ ls tmp/deploy/licenses/core-image-minimal-qemux86-64-2015061812331309:58
bluelightninglicense.manifest  package.manifest09:58
LocutusOfBorg1I was looking at "licenses", not licenses/imagename-and so on09:58
LocutusOfBorg1that's true09:58
LocutusOfBorg1and it's monday :) sorry!09:58
bluelightningnp :)09:58
LocutusOfBorg1damn, I was aware of the deploy/licenses, but not of the subdirectory with everything inside :D09:59
bluelightningI'll have to check how well we document that, maybe we can make it clearer10:00
LocutusOfBorg1that is *exactly* what I was needing for10:00
LocutusOfBorg1I also need coffee, but this is a little bit OT there :p10:00
LocutusOfBorg1I searched here10:00
LocutusOfBorg1but I didn't find anything useful, at least I thinkk10:01
LocutusOfBorg1I also have the yocto book, but I do not remember it was listed10:01
*** raykinsella781 <raykinsella781!rkinsell@nat/intel/x-zlyelqqenqgopmff> has joined #yocto10:02
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-iakyrcfvrduwtltv> has quit IRC10:03
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto10:04
*** bluelightning_ <bluelightning_!~paul@> has quit IRC10:04
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:04
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:04
*** jchonig <jchonig!> has joined #yocto10:10
ftonellodoes oe has any support for git submodules out of the box?10:11
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:15
*** Keshav <Keshav!7d3f5a22@gateway/web/freenode/ip.> has joined #yocto10:15
*** simmel80_ <simmel80_!> has joined #yocto10:19
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC10:21
*** raykinsella781 <raykinsella781!rkinsell@nat/intel/x-zlyelqqenqgopmff> has left #yocto10:21
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto10:22
rburtonftonello: do you mean does the bitbake fetcher support submodules?10:25
joshuaglrburton: RP: autobuilder is idle, may I?10:26
rburtonjoshuagl: yes10:26
*** tmpsantos <tmpsantos!> has joined #yocto10:27
ftonellorburton: well, yes. I would think that submodules would be something optional.10:28
rburtonthere's a gitsm fetcher10:28
ftonellook, let me check10:29
*** jchonig <jchonig!> has quit IRC10:30
ftonellorburton: where should I look for?10:31
*** frsc <frsc!~frsc@> has quit IRC10:31
rburtonthe source is in bitbake's fetch directory10:32
rburtonbut its basically just a git fetcher that does a submodule update for you10:32
*** frsc <frsc!~frsc@> has joined #yocto10:32
*** frsc <frsc!~frsc@> has quit IRC10:33
rburtonpay attention to the warning in the docs though10:33
*** jchonig <jchonig!> has joined #yocto10:34
*** frsc <frsc!~frsc@> has joined #yocto10:36
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC10:38
*** frsc <frsc!~frsc@> has quit IRC10:39
*** frsc <frsc!~frsc@> has joined #yocto10:39
ftonellorburton: Thanks!10:43
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto10:43
*** bluelightning_ <bluelightning_!~paul@> has quit IRC10:43
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:43
*** bluelightning_ is now known as bluelightning10:44
ftonelloI am having trouble fetching a repository from github.10:46
ftonelloThe fetcher always adds a ssh:// when the protocol is ssh, but for some reason that won't close the repository.10:46
rburtonwhat URI are you using?10:46
ftonellothis url works, but bitbake does ssh:// which doesn't work.10:47
ftonellogithub denies access when using ssh://10:47
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-piweeosmadspednf> has joined #yocto10:47
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-piweeosmadspednf> has left #yocto10:47
rburtonthe default protocol for git fetches is git10:49
rburtonnot ssh10:49
ftonelloI am using protocol=ssh, because the git:// doesn't support the colon (:) which thinks is a port.10:49
ftonelloI remembered I solved this problems a long time ago, but I forgot, TBH.10:50
rburtongit: doesn't support authentication10:50
rburtonwhich is why that doesn't work10:50
rburtonuse http?10:50
ftonelloyes. http requires http user and pass, which sucks.10:51
rburtonssh should work if you have keys that work10:51
ftonelloI do have, is just wrong path.10:52
ftonelloI have to use / instead of : for ssh://.10:52
ftonelloWhat happens is that when not specifying what protocol, git does it under the hood.10:52
rburtonremember the URI in a SRC_URI isn't exactly what git is given10:53
ftonelloYes, I was checking.10:54
ftonelloTo use github ssh URI on bitbake one needs to replace : with /10:54
ftonellofor example10:54;protocol=ssh;user=git10:55
*** ddalex1 <ddalex1!> has joined #yocto10:59
*** ddalex <ddalex!~ddalex@> has quit IRC11:01
-YoctoAutoBuilder- build #373 of build-appliance is complete: Success [build successful] Build details are at
*** kimo <kimo!> has joined #yocto11:29
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC11:38
*** cristianiorga <cristianiorga!~cristiani@> has quit IRC11:39
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto11:46
*** tmpsantos <tmpsantos!> has left #yocto11:49
*** hitlin37 <hitlin37!uid16371@gateway/web/> has quit IRC12:09
*** hitlin37 <hitlin37!uid16371@gateway/web/> has joined #yocto12:09
*** zeddii_home <zeddii_home!> has joined #yocto12:10
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto12:12
*** florian_kc is now known as florian12:13
*** mago__ <mago__!~mago@> has quit IRC12:21
*** LocutusOfBorg1 <LocutusOfBorg1!> has quit IRC12:22
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto12:24
*** belen1 <belen1!Adium@nat/intel/x-ncyjztlxzkonqpcw> has joined #yocto12:24
*** mago__ <mago__!~mago@> has joined #yocto12:24
*** belen <belen!~Adium@> has quit IRC12:25
*** timsche <timsche!> has joined #yocto12:27
*** raykinsella781 <raykinsella781!~rkinsell@> has joined #yocto12:33
*** smartin <smartin!~smartin@> has quit IRC12:36
*** smartin_ is now known as smartin12:37
*** challinan <challinan!> has joined #yocto12:38
*** diego_r <diego_r!> has joined #yocto12:38
-YoctoAutoBuilder- build #37 of nightly-arm64 is complete: Success [build successful] Build details are at
*** cristianiorga <cristianiorga!cristianio@nat/intel/x-uqtuqwqbayflblnj> has joined #yocto12:58
*** jku <jku!jku@nat/intel/x-diuqwmvsxgsvivvl> has quit IRC12:58
*** frsc <frsc!~frsc@> has quit IRC13:05
*** raykinsella781 <raykinsella781!~rkinsell@> has quit IRC13:05
*** kscherer <kscherer!~kscherer@> has joined #yocto13:07
-YoctoAutoBuilder- build #380 of nightly-arm is complete: Success [build successful] Build details are at
*** frsc <frsc!~frsc@> has joined #yocto13:17
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-gwyiruzzrxrtfqth> has joined #yocto13:19
*** hugovs <hugovs!~hugo@> has joined #yocto13:21
*** belen1 <belen1!Adium@nat/intel/x-ncyjztlxzkonqpcw> has quit IRC13:23
*** MInipada <MInipada!4ff8f1e0@gateway/web/freenode/ip.> has joined #yocto13:24
*** tsramos <tsramos!tsramos@nat/intel/x-ltptzmiebotvktgj> has joined #yocto13:28
*** vmeson <vmeson!> has joined #yocto13:28
realBigfootDoes anyone know what would cause my rootfs to boot in Read Only?13:31
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-gwyiruzzrxrtfqth> has left #yocto13:38
*** belen1 <belen1!~Adium@> has joined #yocto13:39
*** MInipada <MInipada!4ff8f1e0@gateway/web/freenode/ip.> has left #yocto13:41
*** Minipada <Minipada!4ff8f1e0@gateway/web/freenode/ip.> has joined #yocto13:41
*** ntl <ntl!> has joined #yocto13:42
MinipadaDoes someone know if there's a way to disable build flags for some packages ?13:43
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto13:45
bluelightningrealBigfoot: 'read-only-rootfs' in IMAGE_FEATURES ?13:49
bluelightningrealBigfoot: other than that, you'd have to look at your fstab and the boot log13:49
bluelightningMinipada: which build flags do you mean?13:49
MinipadaFor example O3 or ffast-math13:51
*** zecke <zecke!> has quit IRC13:51
bluelightningit depends on where those flags have actually come from13:53
*** zecke <zecke!~ich@> has joined #yocto13:53
bluelightningi.e. it's trivial to override CFLAGS or CXXFLAGS or whatever per-recipe, but if those flags are being passed within the makefile for the particular piece of software for example, then that's more difficult to override13:54
-YoctoAutoBuilder- build #29 of nightly-mips64 is complete: Success [build successful] Build details are at
*** phantoxeD <phantoxeD!> has joined #yocto13:56
MinipadaI don't know I'm doing the right thing, but these are not here by default, but I would like to apply it to the maximum packages possible, thus editing BUILD_OPTIMIZATION parameter and "disabling" it for packages who can't work with it13:57
*** AndersD <AndersD!> has quit IRC13:57
*** phantoneD <phantoneD!> has quit IRC14:00
*** int <int!~user@> has joined #yocto14:06
inthey guys14:06
intis there a way to use absolete path in bbappend.conf file?14:06
intI mean through the variable?14:07
*** loggerbox <loggerbox!todor@nat/intel/x-qambrbaypvwklgop> has quit IRC14:08
bluelightningint: absolute path in which variable ?14:09
*** loggerbox <loggerbox!~todor@> has joined #yocto14:09
*** zecke_ <zecke_!> has joined #yocto14:09
intbluelightning: can I user ${TOPDIR}/yocto instead of /home/user/yocto/poky/yocto in bbappend.conf file?14:10
bluelightningint: certainly you can yes14:10
bluelightningdo you mean bblayers.conf ?14:10
intbblayers yes14:11
intbluelightning: which variable can I user instead?14:12
*** zecke <zecke!~ich@> has quit IRC14:12
*** lamego <lamego!~jalamego@> has joined #yocto14:13
bluelightningint: I'm not sure I understand the question... ${TOPDIR} should work14:13
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-vjborpauqoaxdfkv> has joined #yocto14:13
bluelightningMinipada: perhaps you could do something similar to what meta/conf/distro/include/ does14:14
bluelightningMinipada: i.e. has a default set of flags and then clears them for select recipes where they don't work14:14
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-vjborpauqoaxdfkv> has left #yocto14:15
*** btooth <btooth!~daniel@> has joined #yocto14:18
*** lamego1 <lamego1!~lamego@> has joined #yocto14:18
btoothsome meta-mono guys here?14:18
intbluelightning: thank you14:22
MinipadaOk, I may do something like that. Thanks bluelightning14:23
btoothi get: aclocal: error: '' is required -- seems to be related to: (Specifically master enables separate build dir by default in)14:25
btoothautotools.bbclass whereas daisy doesn't14:25
bluelightningbtooth: see the migration section of the manual, specifically
bluelightninger, actually
bluelightningbtooth: well, actually I guess that isn't so helpful14:27
btoothbluelighning: back in the mailinglist thread they wrote: The simple way to fix this is to change14:28
btooth'inherit autotools' to 'inherit autotools-brokensep'14:28
btoothi am going to try this14:28
*** benjamirc <benjamirc!~besquive@> has joined #yocto14:28
bluelightningright yes, that's what it mentions in the second link I posted above14:29
*** lamego <lamego!~jalamego@> has quit IRC14:31
btoothbluelightning: that solved it14:31
*** wadim_1 <wadim_1!> has quit IRC14:31
intit is not correct, right?14:32
*** smartin <smartin!> has quit IRC14:34
bluelightningint: maybe you're not aware, but TOPDIR effectively points to your build directory, that probably isn't what you're expecting I guess14:36
bluelightningmorning kergoth14:42
kergothbluelightning: hey, congrats14:42
bluelightningkergoth: thanks!14:42
kergothstill a zombie?14:42
bluelightningkergoth: actually she's sleeping reasonably well at the moment, thankfully14:43
kergothah, nice :)14:43
bluelightningluckily we've had parents around to help us over the last few weeks, otherwise it would have been much more painful14:44
rink_oh, gratz bluelightning14:45
*** alimon <alimon!~alimon@> has joined #yocto14:48
*** david1 <david1!> has joined #yocto14:49
*** Minipada <Minipada!4ff8f1e0@gateway/web/freenode/ip.> has quit IRC14:49
intbluelightning: ok, which variable can I use instead?14:52
bluelightningint: which directory is it that you actually want?14:52
intbluelightning: /home/user/yocto/poky14:53
intin poky there are meta, meta-yocto, meta-yocto-bsp, etc14:53
bluelightningok... so ${COREBASE} might give you that14:53
*** roric <roric!~roric@> has quit IRC14:55
intbluelightning: ERROR: Unable to parse ${COREBASE}/meta/conf/layer.conf: file ${COREBASE}/meta/conf/layer.conf not found in /home/vadimi/yocto_jenkins/poky/build14:55
bluelightningoh right... that's set in layer.conf, so that's not going to work14:56
bluelightninglayer.conf in meta/conf/ that is14:56
bluelightningif you really absolutely must have this done through a variable, I would suggest you set one yourself - if you want you can set one externally and add it to BB_ENV_EXTRAWHITE (again externally) and it'll come through into bitbake's environment14:57
*** cference <cference!> has joined #yocto15:00
*** zecke_ <zecke_!> has quit IRC15:01
kergothyou can use a template with TEMPLATECONF, then ##OEROOT## will be substituted as th epath to corebase15:04
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto15:07
*** tsramos <tsramos!tsramos@nat/intel/x-ltptzmiebotvktgj> has quit IRC15:09
*** jimBaxter <jimBaxter!> has quit IRC15:10
*** roric <roric!~roric@> has joined #yocto15:10
*** jimBaxter <jimBaxter!> has joined #yocto15:12
*** tsramos <tsramos!~tsramos@> has joined #yocto15:16
*** tsramos_ <tsramos_!~tsramos@> has quit IRC15:17
*** jimBaxter <jimBaxter!> has quit IRC15:18
*** smartin <smartin!> has joined #yocto15:18
ftonelloI just sent a patch to bitbake regarding gitsm, if anyone can have a look if it makes sense.15:18
ftonelloI appreciate.15:18
*** ylouise <ylouise!~yalouise@> has joined #yocto15:19
*** staylor <staylor!> has joined #yocto15:20
*** roric <roric!~roric@> has quit IRC15:24
*** smartin_ <smartin_!~smartin@> has joined #yocto15:28
*** frsc <frsc!~frsc@> has quit IRC15:29
*** jimBaxter <jimBaxter!> has joined #yocto15:30
-YoctoAutoBuilder- build #383 of nightly-mips is complete: Failure [failed Building Toolchain Images_1] Build details are at
*** DriverCoder <DriverCoder!> has joined #yocto15:32
*** nicolas_ <nicolas_!58a61e6b@gateway/web/freenode/ip.> has quit IRC15:33
*** jimBaxter <jimBaxter!> has quit IRC15:35
kergothftonello: that patch will result in git mirror tarballs not including the submodules, so it'll be impossible to build with BB_NO_NETWORK=115:35
kergothsince fetch won't fetch them15:35
kergothafaict anyway15:36
kergothand fetching something from a remote in unpack is not kosher, thhat's what fetch is for15:36
rburtonkergoth: reply to the list too please :)15:36
kergothyeah, iw as just thinking that :)15:37
joshuaglhalstead: rburton: RP: I just had a builder fail on disk space15:37
rburtonyeah, its getting space back again now15:37
joshuaglah, OK15:37
* joshuagl may never see a succesful build run on the ab :-(15:37
halsteadjoshuagl, Plenty now. I'm going to start clearing based on space/number of builds instead of time.15:39
halsteadjoshuagl, Which will work much better.15:39
joshuaglhalstead: indeed, that does sound like it'll work better15:39
joshuagllooks like I need to find a fix for oe-selftest before I trigger another fido-next build anyway15:40
*** jimBaxter <jimBaxter!> has joined #yocto15:40
rburtonjoshuagl: check master, theres lots of fixes there :)15:42
*** DriverCoder <DriverCoder!> has quit IRC15:44
joshuaglrburton: aye, I plan to15:44
*** jimBaxter <jimBaxter!> has quit IRC15:44
kergothbluelightning: I'm sure you have a fair bit of stuff to catch up on, but just so it's on your radar, if you could look at the merged recipetool appendsrc patches and the not-yet-merged recipetool patches which let it pull plugins from BBPATH, would appreciate it. still need to write tests for appendsrcfile{,s} for oe-selftest though, forgot about that :)15:46
*** milan <milan!~milan@> has quit IRC15:46
bluelightningkergoth: ah yes that is definitely on my todo list, should be able to get to it soon15:46
rburtonkergoth: i think the unmerged bits are in mut, but the ab has been a bit funky recently15:46
kergothrburton: ah, np15:46
kergothhmm, need to play with devtool's update-recipe —append, haven't tried that, but remember wanting it when i was playing with it last :)15:46
kergothbluelightning: cool, thanks15:46
bluelightningI believe there's a bug open for the plugins in multiple layers thing, so we should probably add that to the commit message15:47
kergothah, didn't realize15:47
yoctiBug 7625: enhancement, Medium, 1.9, paul.eggleton, NEW , Add support for devtool/recipetool plugins in additional layers15:47
bluelightningit covers devtool as well though so I guess it's half of that ;)15:48
kergothcool. it was pretty straightforward, other than the argument parsing thing — had to split that up in order to get the —debug arg before the plugins were available15:48
ftonellokergoth: Yes, I see. I just replied there..15:48
*** jimBaxter <jimBaxter!> has joined #yocto15:48
*** kw01f <kw01f!> has joined #yocto15:49
* kergoth ponders15:50
bluelightningI just learnt that you can refer to bitbake vars as python vars in in-line python15:51
bluelightningkergoth: apparently you implemented that :)15:51
kergothIndeed :) Hmm, I'm not actually sure if the checksumming code properly captures those as variable dependencies, though, better check that before using it too much :)15:52
rburtonbluelightning: as in literal ${FOO} gets expanded at parse?15:53
bluelightningrburton: ${@FOO} yes15:53
bluelightningI stumbled across it in and thought "how can that possibly work?"15:53
rburtonbitbake needs a way to escape the $, very annoying when you're trying to write files containing ${FOO} statements :)15:53
*** sjolley <sjolley!~sjolley@> has quit IRC15:54
bluelightningit's not the only thing we cannot escape... , in PACKAGECONFIG springs to mind15:54
rburtonbluelightning: that VERSION assignment is just line noise15:54
rburtonif i read it a third time, maybe it will make sense15:55
kergothDISTRO_CODENAME is placed in parens after the version if the variable exists in the metadata, since DataSmart supports __contains__, but it should probably have been based on its value, otherwise you can't use the empty string to undo its set, you'd have to use delVar15:56
* kergoth yawns15:56
*** mckoan is now known as mckoan|away15:57
bluelightningright, that's just what I mentioned in my reply to someone on the yocto list15:57
kergothah, that's what the email was about :)15:57
rburtonyeah on the third read i realised that the ${@ is a python trinary test15:57
*** tsramos <tsramos!~tsramos@> has quit IRC15:57
kergothheh, i much prefer the inline if statements to how we used to do it.. remember indexing an inline array based on a boolean state?15:58
* kergoth shudders15:58
bluelightningthose variable names are a little... poorly name-scoped as well, perhaps should have picked that up on review15:58
rburtonkergoth: indexing an inline array was… disgusting15:58
bluelightningkergoth: yeah those definitely took multiple reads to figure out what was going on15:59
bluelightningwe may even still have those in the metadata in places15:59
kergothmost of those variables are un-prefixed since they're not ?=, intended to be isolated to the recipe / set via bbappend. but its a fair point, i don't think many folks cared about os-release at the time i submitted it15:59
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-hkyrgzmwzrbevrot> has joined #yocto16:00
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto16:01
*** bluelightning_ <bluelightning_!~paul@> has quit IRC16:01
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:01
kergoththat's odd, it looks like a patch to os-release was applied twice, or something. i'm seeing two of the comments about the valid fields, and two of the noexecs on patch/configure16:01
*** bluelightning_ is now known as bluelightning16:01
bluelightningkergoth: hmm, I can't see that in either poky or OE-Core... ?16:02
rburtonme neither16:02
kergothhuh, weird, terminal refresh artifact. nevermind :)16:03
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-hkyrgzmwzrbevrot> has left #yocto16:05
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-hkyrgzmwzrbevrot> has joined #yocto16:05
ftonellokergoth, rburton: Sent another patch, which works with previous implementation.16:06
*** dorileo <dorileo!~dorileo@> has joined #yocto16:06
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC16:13
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto16:14
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC16:19
*** jbrianceau is now known as jbrianceau_away16:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:22
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:24
*** TobSnyder <TobSnyder!> has quit IRC16:25
*** ryansturmer <ryansturmer!> has joined #yocto16:25
ryansturmerHi everyone, I'm getting started building an image for the Intel Edison16:25
ryansturmerI'm not a stranger to LFS or to Embedded Linux, but I am new to Yocto - is there a preferred starting point for working with the Edison?  I see that intel provides a source build that - includes yocto somehow - is that the preferred place to start?16:27
david1I started with their work, and their makefiles just to understand how it worked and I then switched to a normal yocto architecture16:28
ryansturmerI have cloned poky and done a test build without changing any of the default settings, and am having some difficulty figuring out where to go next to configure things.16:28
Crofton|workwhat are you trying to change?16:29
ryansturmerWell, I'd like to do some customization to the file systems that are used and the packages that are installed16:30
ryansturmerFor instance, booting with a read-only root FS16:30
ryansturmerSo compiling the image from scratch with my preferred packages and filesystem configuration is attractive16:31
kergoththat's documented. usually done from <build dir>/conf/local.conf. EXTRA_IMAGE_FEATURES += "read-only-rootfs". I'm actually surprised the existing section about image features in the local.conf doesnt' mention that feature16:32
kergothstill, read local.conf, which has many examples of cnfiguration, and the yocto project documentation16:32
ryansturmeroh that's nice!16:32
ryansturmerSo, the best thing to do would be to start with intel's package, rather than cloning yocto and working my way into it from there?16:33
kergothnot sure on that one, guessing the intel folks would know the answer to that better than i16:34
rburtonintel's bsp is yocto based, and you;ll need the right BSP if you actually want to run anything on the edison...16:34
rburton(for the kernel, drivers, etc)16:34
*** jonathanmaw <jonathanmaw!> has quit IRC16:34
*** sjolley <sjolley!sjolley@nat/intel/x-tzineqgkyvujtzln> has joined #yocto16:34
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto16:35
ryansturmerI'm running their makefile now, it looks like their thing is just a recipe, and a script that goes and clones poky, puts it in the right place, and runs the build16:41
*** behanw <behanw!~behanw@2001:470:b26c:0:7102:2af6:3587:ddeb> has joined #yocto16:42
david1yep exactly ryansturmer. It also set some variables in the local.conf16:42
ryansturmerAh gotcha16:42
ryansturmerWhat is the difference between a BSP and a recipe?16:43
ryansturmerThe terms BSP, recipe, layer all run togehter for me - a recipe is instructions for making a single package, and a layer is a bunch of recipes?16:44
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:44
ryansturmerand a bsp is a collection of layers and other stuff?16:44
david1The BSP layer contains hardware specific configuration and recipes16:44
david1A layer is just ... a layer, it can be hardware, software, for a middleware etc.16:45
david1It's a group of packages you get from recipes (someone stops me if I'm wrong)16:45
ryansturmerSo a layer is a bunch of recipes, and a BSP is really just a layer that contains the recipes for a specific hardware implementation16:46
*** smartin <smartin!> has quit IRC16:46
*** tsramos <tsramos!tsramos@nat/intel/x-cnbbharqsapmaygy> has joined #yocto16:48
*** smartin <smartin!> has joined #yocto16:48
*** bluelightning <bluelightning!~paul@> has joined #yocto16:49
*** bluelightning <bluelightning!~paul@> has quit IRC16:49
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:49
ryansturmerOk - complete tangent - anyone used toaster?  I got it setup and played with it some, it seems neat16:50
rburtontoaster is awesome!!!!16:51
rburton<disclaimer: i work with the people who wrote it>16:51
Crofton|workrburton, do you use it?16:52
ulf`I like my toaster16:52
Crofton|work(serious question)16:52
belen1yes, rburton: serious question ;)16:53
* Crofton|work does need to remember how to run it16:53
* Crofton|work needs to find out what he did with all his disk space first16:54
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has quit IRC16:54
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has joined #yocto16:54
*** ambrosius <ambrosius!~textual@> has joined #yocto16:55
ryansturmerMy toaster installation keeps prompting me to configure a layer source16:55
rburtonCrofton|work: terminal from cold dead hands etc16:55
Crofton|workI understand16:55
rburtonnow if only it had awesome analytics16:55
belen1ryansturmer: are you using master or fido?16:55
ryansturmerwhich I believe I did, and I'm not sure I fully understand the whole layer source thing16:55
belen1ryansturmer: a layer source is just a collection of layers. Toaster comes with a configuration file that sets up the layer source at layers.openembedded.org16:56
belen1ryansturmer: but you need to make you to import that configuration file when setting up Toaster16:57
*** diego_r <diego_r!> has quit IRC16:57
ryansturmerWhen I go to "view compatible machines" it says "configure a layer source" which I have done, using toasterconf.json during the install process16:57
ryansturmerI did tell it to use that file, and if I go to the django admin, it has a few layer sources listed, including the openembedded one16:58
ryansturmerthe openembedded one looks like the only "remote" source, and the other two just point to directories on disk16:58
belen1ryansturmer: mmm, something has gone wrong. Maybe it failed to import the information from the layer source. If you click to view compatible layers, do you have any?16:59
ryansturmerif I choose "view all compatible layers" from the project configuration area on a fresh project17:03
ryansturmerI get a list of 70 layers17:03
ryansturmerrelease is set to 1.8 fido17:03
belen1ryansturmer: that sounds about right. What if you click on 'view compatible recipes'?17:04
*** sameo <sameo!~samuel@> has quit IRC17:04
ryansturmertoaster has no recipe information17:06
ryansturmerto get recipes, configure a layer source, or import a thing and do a stuff17:07
belen1ryansturmer: are you sure you haven't cloned the yocto project master branch?17:07
ryansturmerhell no I'm not sure of that :)17:07
ryansturmerlemme check17:07
belen1ryansturmer: we have a bug in master that causes that problem, but it should work if you use the fido release instead17:07
ryansturmeri should be on the fido branch, right?17:07
ryansturmeror is there a release branch other than the one just called "fido"17:08
belen1ryansturmer: it's a bit confusing. Toaster supports building with several releases through the project release selection trick, but you need to run Toaster itself using a certain release17:08
ryansturmerso I need to pass something to toaster when I invoke it, or edit a config file?17:09
ryansturmerjust being on the fido branch isn't enough?17:09
belen1ryansturmer: no. You need to clone the fido branch of the yocto project and set up Toaster with that.17:10
belen1ryansturmer: purely because Toaster is broken in master right now. We broke it last week and we are still trying to fix it :)17:10
belen1ryansturmer: but if you cloned the fido branch of the yocto project and set up Toaster with that, and you are still seeing this problem, then we have an issue we didn't know about, and we should look into17:12
realBigfootWe got some yocto recpies repository. Does it make sense to have a license file on the recipes ?17:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:15
ryansturmerso, I have never been on the master, so far as I know. I cloned fido, and configured with fido17:16
ryansturmerI will try again from scratch to reproduce my issue for you, if that is helpful.17:16
belen1ryansturmer: Yes please. That would be really helpful17:18
*** bluelightning <bluelightning!~paul@> has joined #yocto17:18
*** bluelightning <bluelightning!~paul@> has quit IRC17:18
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:18
*** roric <roric!> has joined #yocto17:20
ryansturmergood time to mention im not on a "supported" linux distro17:21
*** belen1 <belen1!~Adium@> has quit IRC17:29
*** belen1 <belen1!~Adium@> has joined #yocto17:29
*** Noor <Noor!~quassel@> has quit IRC17:31
ryansturmerI did not notice this error message on toaster first run last time17:31
ryansturmerCannot find layer version  OpenEmbedded (1) 65 fido17:31
ryansturmerFailure while trying to import the toaster config file: Layer_Version matching query does not exist.17:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:31
*** bluelightning <bluelightning!~paul@> has joined #yocto17:31
*** bluelightning <bluelightning!~paul@> has quit IRC17:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:31
*** ylouise <ylouise!~yalouise@> has left #yocto17:33
*** roric <roric!> has quit IRC17:37
kergothrealBigfoot: yes. do you mean the license of the recipes themselves rather than the projects the recipes refer to?17:37
kergothusually that's MIT17:37
kergoth(doesn't have to be, though, just easy since they're usually trivial)17:37
realBigfootkergoth, yes.. Nice! This is the license we were planing to put it17:37
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC17:38
*** lamego1 <lamego1!~lamego@> has quit IRC17:41
*** lamego <lamego!lamego@nat/intel/x-vxwqnkvvvtnulygl> has joined #yocto17:42
ryansturmerIf there is any further toaster error information I can provide, let me know.17:44
ryansturmerI am diverting temporarily to go build with the intel makefile17:44
ryansturmerbut I can pick it back up again17:44
*** timsche <timsche!> has quit IRC17:45
Crofton|workhmm, opening page of toaster still refers to hob17:47
*** Noor <Noor!~quassel@> has joined #yocto17:47
Crofton|workI run toaster, not I can't tun bitbake17:48
*** behanw <behanw!~behanw@2001:470:b26c:0:7102:2af6:3587:ddeb> has quit IRC17:49
Crofton|worktoaster started bibtake server17:50
*** Noor <Noor!~quassel@> has quit IRC17:52
*** kw01f <kw01f!> has quit IRC17:59
*** ryansturmer <ryansturmer!> has quit IRC18:00
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC18:02
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto18:04
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:04
*** Noor <Noor!~quassel@> has joined #yocto18:07
*** benjamirc <benjamirc!~besquive@> has quit IRC18:10
*** Noor <Noor!~quassel@> has quit IRC18:14
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC18:15
*** bluelightning <bluelightning!~paul@> has joined #yocto18:17
*** bluelightning <bluelightning!~paul@> has quit IRC18:17
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:17
*** david1 <david1!> has quit IRC18:18
*** behanw <behanw!~behanw@> has joined #yocto18:22
*** [Sno] <[Sno]!> has quit IRC18:23
*** zecke <zecke!~ich@> has joined #yocto18:26
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC18:26
*** likewise_ <likewise_!> has joined #yocto18:27
*** Noor <Noor!~quassel@> has joined #yocto18:28
*** hitlin37 <hitlin37!uid16371@gateway/web/> has quit IRC18:29
*** roric <roric!> has joined #yocto18:29
*** benjamirc <benjamirc!besquive@nat/intel/x-mboshgeqakbortgg> has joined #yocto18:32
*** zecke <zecke!~ich@> has quit IRC18:32
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:34
*** belen1 <belen1!> has joined #yocto18:43
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto18:45
belen1ryansturmer: Thanks! That means the problem might be on the OE layer source.18:46
*** jimBaxter <jimBaxter!> has quit IRC18:47
belen1Crofton|work: well, if you are running Toaster in 'analysis' mode, yes it does.18:49
belen1Crofton|work: because you cannot build with Toaster if you are running it that way18:49
*** DriverCoder <DriverCoder!~mdrustad@> has joined #yocto18:53
*** benjamirc <benjamirc!besquive@nat/intel/x-mboshgeqakbortgg> has quit IRC18:53
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-vmlbsipgfmiowzwo> has joined #yocto18:56
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-vmlbsipgfmiowzwo> has left #yocto18:57
*** pdp7_ is now known as pdp718:58
*** pdp7 <pdp7!> has quit IRC18:58
*** pdp7 <pdp7!~pdp7@fsf/member/pdp7> has joined #yocto18:58
kergothHmm, I wonder if oe selftest unit tests can be loaded from external / layer locations, so i could write unit tests for the MEL layer-local kernel recipetool subcommands18:59
*** pohly <pohly!> has quit IRC18:59
*** kw01f <kw01f!> has joined #yocto19:00
Crofton|workbelen1, I was following instructinos :)19:00
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hymzoysozfmszcjc> has joined #yocto19:00
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hymzoysozfmszcjc> has left #yocto19:01
belen1Crofton|work: I was just talking about the Hob thing :)19:05
*** likewise_ <likewise_!> has quit IRC19:06
*** likewise_ <likewise_!> has joined #yocto19:06
Crofton|workbelen1, I started toaster, but it wouldn't let me run bitbake, claimed bitbake was already running19:07
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC19:08
kergothCrofton|work: are you running in the context where toaster was started? iirc it sets env vars so bitbake acts as a client with the bitbake server it starts rather than starting a server itself. course thats speaking as someone who knows jack about toaster, so i might be completely wrong :)19:08
Crofton|workyeah, I jsut did what it said on the wiki and it started the bitbaek server19:08
Crofton|workI'll poke more later, jsut wanted to see how it had changed since I last ran it19:09
kergothiirc the wiki has you source the thing, if you changed terminals....19:09
* kergoth shrugs, admittedly speaking from ignorance, should know better than to do that :)19:09
*** raykinsella78 <raykinsella78!~rkinsell@> has joined #yocto19:09
*** raykinsella78 <raykinsella78!~rkinsell@> has left #yocto19:09
belen1Crofton|work: I wouldn't follow the wiki. We have a manual now! :)19:10
Crofton|workah, I changed terminals :)19:10
belen1kergoth: I wouldn't be too worried. I know nothing myself ;)19:11
kergothso its trying to start a second server against the same build dir, probably19:11
kergothhah :)19:11
belen1Crofton|work: we should really get rid of those instructions in the wiki. I might get to that tomorrow19:12
*** pohly <pohly!> has joined #yocto19:19
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto19:19
*** behanw <behanw!~behanw@> has quit IRC19:23
*** Jefro <Jefro!> has joined #yocto19:25
*** lamego1 <lamego1!~lamego@> has joined #yocto19:32
*** lamego <lamego!lamego@nat/intel/x-vxwqnkvvvtnulygl> has quit IRC19:32
*** roric <roric!> has quit IRC19:36
*** Jefro1 <Jefro1!> has joined #yocto19:39
*** Jefro <Jefro!> has quit IRC19:41
*** Jefro1 <Jefro1!> has quit IRC19:58
*** lamego1 <lamego1!~lamego@> has quit IRC19:58
*** Jefro <Jefro!> has joined #yocto19:59
*** Jefro <Jefro!> has quit IRC20:01
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC20:02
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto20:05
*** kw01f <kw01f!> has quit IRC20:07
*** JaMa <JaMa!> has quit IRC20:11
*** lamego <lamego!~lamego@> has joined #yocto20:12
*** pohly <pohly!> has quit IRC20:12
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC20:13
*** [Sno] <[Sno]!> has joined #yocto20:14
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto20:16
*** nighty-_ <nighty-_!> has quit IRC20:18
*** roric <roric!> has joined #yocto20:19
*** likewise_ <likewise_!> has quit IRC20:19
*** roric <roric!> has quit IRC20:24
*** paulg_ <paulg_!> has joined #yocto20:26
*** lamego <lamego!~lamego@> has quit IRC20:35
*** lamego <lamego!~lamego@> has joined #yocto20:36
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto20:39
*** belen1 <belen1!> has quit IRC20:42
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC20:43
*** dmoseley <dmoseley!> has quit IRC20:52
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto20:57
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC20:59
*** destrudo <destrudo!~destrudo@> has quit IRC21:00
kergothHmmm, should add a recipetool sub-command which simply creates a bbappend in the specified layer for the specified recipe/provide, and prints the path to it, as a convenience when making changes other than those recipetool does for you21:08
*** grma <grma!> has quit IRC21:15
*** sameo <sameo!~samuel@> has joined #yocto21:16
*** destrudo <destrudo!~destrudo@> has joined #yocto21:18
*** behanw <behanw!~behanw@2001:470:b26c:0:80cb:dbfc:11aa:4ff5> has joined #yocto21:21
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC21:23
*** ryansturmer <ryansturmer!> has joined #yocto21:36
ryansturmerso I've run into a build issue with yocto and I'm struggling with what to do next.  My build for the intel edison passed, save for ncurses and pseudo21:39
ryansturmerWhat's the procedure for sorting this out - do I find a patch and add it to the recipe in the yocto tree?21:40
rburtonfirst step is usually to say what the problem is and see if its something we can help with21:42
rburtonpseudo not working is fairly fundamental to packages being built at all though21:42
* rburton has to go now though21:42
*** glfernando <glfernando!glfernando@nat/intel/x-hhmkpneorwgvmlxe> has quit IRC21:50
*** glfernando <glfernando!glfernando@nat/intel/x-cayfspkgupzegkzn> has joined #yocto21:52
ryansturmerwell, here's the paste of my output:21:52
*** glfernand_ <glfernand_!fernando@nat/intel/x-aegosjlwddtoawje> has joined #yocto21:53
*** glfernando <glfernando!glfernando@nat/intel/x-cayfspkgupzegkzn> has quit IRC21:53
ryansturmerThis was a subsequent build - the first build took a long time, and it looks like many tasks completed21:53
ryansturmerThis one was quick, but reported failures in the same two recipes21:54
ryansturmerI was not familiar with pseudo, but yeah, it looks essential, not sure why so much seemed successful without it?21:56
*** glfernand_ <glfernand_!fernando@nat/intel/x-aegosjlwddtoawje> has quit IRC21:56
*** bfederau <bfederau!> has quit IRC22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-hkyrgzmwzrbevrot> has quit IRC22:01
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-hkpapiouxrprazhi> has joined #yocto22:02
ryansturmerIt looks like with ncurses, that this is perhaps a known issue with the newest version22:05
ryansturmerI wonder if there's a way to convince it to use an older one22:06
*** sjolley <sjolley!sjolley@nat/intel/x-tzineqgkyvujtzln> has quit IRC22:06
*** evanp_ is now known as evanp22:10
*** benjamirc <benjamirc!~besquive@> has joined #yocto22:11
*** tsramos <tsramos!tsramos@nat/intel/x-cnbbharqsapmaygy> has quit IRC22:18
*** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has quit IRC22:22
vmrod25question .. does any one have being able to make a webcam works on Yocto ?22:25
*** hugovs <hugovs!~hugo@> has quit IRC22:31
nerdboydo you have the right module(s) enabled?22:32
*** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has joined #yocto22:32
nerdboydepending on camera driver you might need vendor fork/patch for all i know...22:33
nerdboy*if you're talking yocto kernel22:33
*** phantoxeD <phantoxeD!> has quit IRC22:33
*** phantoxeD <phantoxeD!> has joined #yocto22:34
*** sjolley <sjolley!~sjolley@> has joined #yocto22:39
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-hkpapiouxrprazhi> has quit IRC22:45
*** vmrod25 <vmrod25!~vmrod25@> has joined #yocto22:46
-YoctoAutoBuilder- build #374 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at
*** staylor <staylor!> has quit IRC23:03
*** ntl <ntl!> has quit IRC23:04
*** lamego <lamego!~lamego@> has quit IRC23:12
*** ntl <ntl!> has joined #yocto23:17
*** vmrod25 <vmrod25!~vmrod25@> has quit IRC23:18
*** vmrod25 <vmrod25!~vmrod25@> has joined #yocto23:18
*** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has quit IRC23:19
*** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has joined #yocto23:24
*** DriverCoder <DriverCoder!~mdrustad@> has quit IRC23:29
*** vmrod25 <vmrod25!~vmrod25@> has quit IRC23:38
*** benjamirc <benjamirc!~besquive@> has quit IRC23:47
*** varibull__ <varibull__!> has quit IRC23:54
*** varibull__ <varibull__!> has joined #yocto23:55
*** varibull__ <varibull__!> has quit IRC23:56
*** varibull__ <varibull__!> has joined #yocto23:56
*** staylor <staylor!~staylor@> has joined #yocto23:57

Generated by 2.11.0 by Marius Gedminas - find it at!