Thursday, 2015-07-23

*** RP <RP!> has quit IRC00:05
-YoctoAutoBuilder- build #395 of nightly-ipk is complete: Failure [failed Running Sanity Tests_1] Build details are at
*** RP <RP!> has joined #yocto00:33
*** sameo <sameo!~samuel@> has quit IRC00:35
*** SoylentYellow <SoylentYellow!> has quit IRC00:36
-YoctoAutoBuilder- build #62 of nightly-rpm-non-rpm is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #406 of nightly-x86-64 is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #63 of nightly-deb-non-deb is complete: Failure [failed Running Sanity Tests_1] Build details are at
*** ambrosius <ambrosius!~textual@> has quit IRC01:13
*** ryansturmer <ryansturmer!> has joined #yocto01:20
-YoctoAutoBuilder- build #400 of nightly-qa-skeleton is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #401 of nightly-qa-pam is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #394 of nightly-rpm is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #394 of nightly-intel-gpl is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #389 of nightly-deb is complete: Failure [failed Running Sanity Tests_1] Build details are at
*** Jefro <Jefro!> has quit IRC01:42
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has joined #yocto01:48
*** dmoseley <dmoseley!> has quit IRC01:51
-YoctoAutoBuilder- build #399 of nightly-qa-logrotate is complete: Failure [failed Running Sanity Tests] Build details are at
*** Ox4` <Ox4`!~user@> has joined #yocto02:16
-YoctoAutoBuilder- build #53 of nightly-mips64 is complete: Success [build successful] Build details are at
*** Ox4 <Ox4!~user@unaffiliated/zloy> has quit IRC02:18
-YoctoAutoBuilder- build #404 of nightly-arm is complete: Failure [failed Running Sanity Tests] Build details are at
*** afxez0r <afxez0r!~afxez0r@> has quit IRC02:32
-YoctoAutoBuilder- build #405 of nightly-x86 is complete: Failure [failed Running Sanity Tests] Build details are at
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC03:00
-YoctoAutoBuilder- build #402 of nightly-multilib is complete: Failure [failed Running Sanity Tests_2 Running Sanity Tests_3] Build details are at
-YoctoAutoBuilder- build #405 of nightly-world is complete: Failure [failed BuildImages] Build details are at
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto03:11
*** miandonmenmian__ <miandonmenmian__!~miandonme@> has joined #yocto03:28
*** miand118 <miand118!~miandonme@> has joined #yocto03:28
*** pidge <pidge!~pidge@2a02:8084:0:3000:d916:4206:2522:990f> has quit IRC03:30
*** ambrosius <ambrosius!> has joined #yocto03:31
*** Jefro <Jefro!> has joined #yocto03:34
*** hamis <hamis!~irfan@> has joined #yocto03:44
*** ambrosius <ambrosius!> has quit IRC04:05
*** aehs29 <aehs29!aehernan@nat/intel/x-ovcnowehwtzhjtih> has joined #yocto04:42
*** btooth <btooth!> has joined #yocto04:49
*** aehs29 <aehs29!aehernan@nat/intel/x-ovcnowehwtzhjtih> has left #yocto04:49
*** btooth <btooth!> has quit IRC04:57
*** [Sno] <[Sno]!> has quit IRC05:07
*** Jefro <Jefro!> has quit IRC05:10
*** seebs <seebs!> has joined #yocto05:12
*** tobiash_ <tobiash_!> has quit IRC05:16
*** ambrosius <ambrosius!> has joined #yocto05:23
*** marek__ <marek__!> has joined #yocto05:28
*** aehs29 <aehs29!~aehernan@> has joined #yocto05:53
*** aehs29 <aehs29!~aehernan@> has left #yocto05:53
*** Jefro <Jefro!> has joined #yocto05:58
*** wadim_ <wadim_!> has joined #yocto06:19
*** [Sno] <[Sno]!> has joined #yocto06:24
*** mansandersson <mansandersson!~Mans@> has joined #yocto06:51
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has quit IRC06:51
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto06:56
*** miandonmenmian__ <miandonmenmian__!~miandonme@> has quit IRC06:56
*** miand118 <miand118!~miandonme@> has quit IRC06:56
*** jbrianceau_away is now known as jbrianceau06:57
*** miandonmenmian <miandonmenmian!> has joined #yocto06:59
*** miand44 <miand44!> has joined #yocto07:00
*** egavinc <egavinc!> has joined #yocto07:03
*** TobSnyder <TobSnyder!> has joined #yocto07:11
*** diego_r <diego_r!> has joined #yocto07:13
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto07:21
*** Jefro <Jefro!> has quit IRC07:23
*** Biliogadafr <Biliogadafr!> has joined #yocto07:32
*** ambrosius <ambrosius!> has quit IRC07:39
*** sameo <sameo!~samuel@> has joined #yocto07:59
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-jescdbwxxlmdjqci> has joined #yocto08:08
*** bluelightning <bluelightning!~paul@> has joined #yocto08:12
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:12
*** jonathanmaw <jonathanmaw!> has joined #yocto08:18
*** grma_ <grma_!> has joined #yocto08:23
*** onoffon <onoffon!~khem@unaffiliated/khem> has joined #yocto08:25
*** ryanstur_ <ryanstur_!> has joined #yocto08:25
*** mchehab` <mchehab`!> has joined #yocto08:26
*** ryansturmer <ryansturmer!> has quit IRC08:26
*** mchehab <mchehab!> has quit IRC08:26
*** jwessel <jwessel!~jwessel@> has quit IRC08:26
*** khem <khem!~khem@unaffiliated/khem> has quit IRC08:26
*** grma <grma!> has quit IRC08:26
*** RP <RP!> has quit IRC08:26
*** sjolley1 <sjolley1!~sjolley@> has quit IRC08:26
*** mchehab` is now known as mchehab08:26
*** sjolley <sjolley!~sjolley@> has joined #yocto08:26
*** jwessel <jwessel!~jwessel@> has joined #yocto08:27
*** RP <RP!> has joined #yocto08:27
*** miandonmenmian <miandonmenmian!> has quit IRC08:28
*** miandonmenmian <miandonmenmian!> has joined #yocto08:28
bluelightningmorning all08:32
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC08:32
*** jimBaxter <jimBaxter!> has joined #yocto08:34
*** ddalex2 <ddalex2!> has quit IRC08:35
*** psnsilva <psnsilva!> has joined #yocto08:36
*** psnsilva <psnsilva!> has quit IRC08:42
*** phantoxeD <phantoxeD!> has quit IRC08:46
*** grma_ is now known as grma08:48
vdehors_does someone face issues with today ?08:52
*** jlasnier <jlasnier!> has joined #yocto08:52
vdehors_sometimes i get :[0:]: errno=Connection timed out08:53
*** psnsilva <psnsilva!> has joined #yocto08:54
*** zerus <zerus!> has joined #yocto09:10
*** egavinc <egavinc!> has quit IRC09:13
*** miand44 <miand44!> has quit IRC09:17
*** miandonmenmian <miandonmenmian!> has quit IRC09:17
*** miandonmenmian_ <miandonmenmian_!~miandonme@> has joined #yocto09:19
*** 7F1AAFGLZ <7F1AAFGLZ!~miandonme@> has joined #yocto09:19
*** psnsilva <psnsilva!> has quit IRC09:22
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC09:26
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto09:27
*** tmcguire <tmcguire!~tmcguire@> has quit IRC09:31
*** psnsilva <psnsilva!> has joined #yocto09:37
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-jescdbwxxlmdjqci> has quit IRC09:38
*** zerus <zerus!> has quit IRC09:39
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-csfeqcmllsanysuu> has joined #yocto09:41
*** rburton <rburton!> has joined #yocto09:51
AzaToth_bluelightning, I think we missunderstood eachother yesterday :( What I'm trying to do is to build a rootfs tar.gz, and then place that file into a directory in another rootfs. Atm we have two recipes to do this, but I need to run bitbake on the first recipe first and then run bitbake on the other; our current recipe code can be found at
bluelightningAzaToth_: so at the bare minimum the do_rootfs task of one needs to depend upon the other, which would be do_rootfs[depends] += "otherimagerecipe:do_rootfs"09:52
*** psnsilva <psnsilva!> has quit IRC09:58
AzaToth_bluelightning, seems to work; thanks :)10:01
*** belen <belen!Adium@nat/intel/x-abejebhliuhrlygt> has quit IRC10:08
*** psnsilva <psnsilva!> has joined #yocto10:15
*** pidge <pidge!~pidge@2a02:8084:0:3000:91aa:74f1:2ca6:5d5c> has joined #yocto10:20
abellonibluelightning: is there any plan for a YP dev day at elce ?10:24
bluelightningabelloni: I believe so, but you'd need to ask Jefro or Crofton|work for details10:24
*** pohly <pohly!~pohly@> has joined #yocto10:28
*** dshwang <dshwang!~dshwang@> has quit IRC10:32
*** pidge <pidge!~pidge@2a02:8084:0:3000:91aa:74f1:2ca6:5d5c> has quit IRC10:34
*** pidge <pidge!~pidge@2a02:8084:0:3000:91aa:74f1:2ca6:5d5c> has joined #yocto10:36
*** 7F1AAFGLZ <7F1AAFGLZ!~miandonme@> has quit IRC10:39
*** miand197 <miand197!~miandonme@> has joined #yocto10:40
*** phantoxeD <phantoxeD!> has joined #yocto10:42
*** miand197 <miand197!~miandonme@> has quit IRC10:43
*** miandonmenmian_ <miandonmenmian_!~miandonme@> has quit IRC10:43
*** abelloni <abelloni!> has quit IRC10:44
*** abelloni <abelloni!> has joined #yocto10:44
*** belen <belen!Adium@nat/intel/x-mvpwlkjzpfcnzxpx> has joined #yocto10:55
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-csfeqcmllsanysuu> has left #yocto10:56
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC10:59
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto11:00
*** belen1 <belen1!Adium@nat/intel/x-fybhrocgdtijvdhp> has joined #yocto11:03
*** belen <belen!Adium@nat/intel/x-mvpwlkjzpfcnzxpx> has quit IRC11:05
*** pohly <pohly!~pohly@> has quit IRC11:12
ericbuttershey.. i am missing javac in my yocto sdk. how to add this? i can find it in the host sysroot in tmp/11:19
*** zerus <zerus!> has joined #yocto11:21
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto11:30
*** psnsilva <psnsilva!> has quit IRC11:32
*** nighty-_ <nighty-_!> has joined #yocto11:42
Crofton|workabelloni, see my email to the list11:47
*** psnsilva <psnsilva!> has joined #yocto11:47
Crofton|workYP dev day after ELCE and OEDEM Friday11:47
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC11:51
*** zerus <zerus!> has quit IRC11:53
*** dshwang <dshwang!~dshwang@> has joined #yocto11:54
*** wadim_ <wadim_!> has quit IRC11:55
*** wadim_ <wadim_!> has joined #yocto11:56
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto12:07
*** kanucu <kanucu!4d5007b2@gateway/web/freenode/ip.> has joined #yocto12:17
kanucuhey, i'm trying to run a program on my poky distribution,  but when i start it,  the library icui18n is missing, altough it is in the dependencies and in build/tmp-glibc/sysroots/qemuzynq/usr/lib12:19
kanucualtough i cant find it in the ditribution12:20
kanucushouldnt the library be installed automatically?12:20
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC12:22
bluelightningkanucu: if its dlopen()ed then no, we can't detect that12:24
bluelightningwe can have explicitly stated dependencies when we find those though12:25
kanucusomehow RDEPENDS_${PN} += "libicui18n" doesnt give back an error12:26
kanucualso bitbake icu does work12:27
kanucubut still12:27
kanucuthe .so is missing12:27
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto12:28
bluelightningkanucu: where did you set that?12:28
*** davis <davis!> has joined #yocto12:31
davisI have built sato image for beaglebone using yocto. I'm trying to find the image to load on the sdcard for flashing a new image.  Do I use the poky/build/tmp/deply/images/core-image-sato-beaglebone.tar.bz2? This seems like just a rootfs and not everything I need.12:31
abellonidavis: you should use wic to generate the sdcard image12:32
bluelightningwe do have instructions on how to flash images for beaglebone in README.hardware12:33
davisone constraint I have, is that on my linux yocto build host, I dont have a sdcard writer. I was using a windows laptop with a sd card slot to write my previous images.12:34
davisbluelightning: README.hardware in yocto documentation dir?12:34
bluelightningdavis: it's in the root of the poky checkout12:34
davisyeah, that part assumes I have a card reader/writer for linux. unfortunately I don't.12:35
davisi was using the win32diskimager to write the image on a windows laptop. :-(12:35
davisi thought the build might make a compatible image for that tool.12:36
bluelightningwic might be able to build such an image12:37
bluelightningyou'd have to find some instructions on how to use it specifically for beaglebone though12:38
abellonidavis: you'll probably find a discussion between me and bboozzoo with instructions for the BBB on the ML12:39
davisthanks I'll look12:39
davisi just got lucky and found a collegue with a removeable one.12:40
davisill try it. many thanks folks, I appreciate your help.12:40
bluelightningkanucu: based on what you've told me I can't immediately see what the issue would be12:40
bluelightningkanucu: most of those explicit dependencies you've added are probably unnecessary though12:41
kanucuye might be, but shouldn't create problems right?12:41
bboozzoodavis: yup, wic will be the easiest to get you started, you'll get an image that you dd to sdcard, you skip all the manual fdisk/mkfs crutf that's listed on the web page ;)12:42
kanucui just started a new clean build, it seems meta-toolchain-qt also wont work out of the box...12:43
davisbboozzoo: its cool. i'm doing the manual method now, but for future reference where is this wic tool mentioned?12:46
*** gourve_l <gourve_l!> has quit IRC12:47
bluelightningkanucu: what does "won't work" mean?12:48
bboozzoodavis: mostly here I had not update README.hardware manual with input on wic12:49
davisfwiw, when I move the sd card to the beagle, do I hold down the boot button and it will turn on all leds when its done with its flashing?12:50
kanucu"satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-qt-toolchain-target:  *     libqtphonon4-dev "12:51
kanucualtough it should be in qt-x11-free12:52
davisheh, bboozzoo when i went to add your reply to my notes, I noticed I had already added some notes from you.12:52
davismany thanks again12:52
bboozzoouhm, no, it will just boot from the sd card12:52
davisso no holding down the button when I turn it on?12:53
abelloniI'd say only on the first power on12:56
abelloninot on the subsequent resets12:56
*** Hector_ <Hector_!500fd832@gateway/web/freenode/ip.> has joined #yocto12:56
Hector_I created a custom recipe that is simply copying a folder containing files and subfolders in the /root directory of the target rootfs. But the do_rootfs always fails because the package_split is empty :/ Do you have any idea why ?12:57
davishmm. well just putting the sdcard in and turning on, seemed to run the previous image.12:58
bluelightningkanucu: right, I think someone has forgotten to remove that reference12:58
davisif I hold down the boot button while I insert power, it does not flash any leds so it appears not to be trying to load the newly built image12:58
kanucubluelightning: so libqtphonon4-dev is not needed anymore?12:59
bluelightningkanucu: we recently disabled phonon by default, thus it should not be mentioned in the inc file used by meta-toolchain-qt13:02
bboozzoodavis: you need to connect the serial cable to actually see something useful13:02
davishmm. yes i have one of those on order.13:03
davisso i guess without serial cable, I can't complete the image install?13:03
bboozzoosince you're using the stock linux-yocto kernel, you're missing all the bells and whistles like blinking leds and so on13:04
kanucubluelightning: /openembedded-core/meta/recipes-qt/packagegroups/packagegroup-qt-toolchain-target.inc13:04
kanucui think?13:04
bboozzooso you're basically already running the image, it's just that there is not visual feedback, but if you connected a serial console, you'd see it boot13:05
bluelightningkanucu: yes13:05
davisfwiw, i have a lcd cape attached. when i finish booting to X (as it used to) I see the file manager and it shows the boot and root partitions in the file manager.13:06
*** hamis <hamis!~irfan@> has quit IRC13:06
kanucubluelightning: ok thank you13:06
kanucui'll try again13:06
bluelightningI will send a fix for that13:07
davisthe boot has MLO and u-boot.img and the root has what looks like a unix fs13:07
davisbut it looks like its running the stock debian/X after I did the upgrade procedure13:08
*** dl9pf_ <dl9pf_!> has quit IRC13:09
*** melio_cc <melio_cc!> has joined #yocto13:10
davisif it shows a X/openbox/ desktop on the lcd, its not booting what I built with yocto sato-img right?13:10
*** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has joined #yocto13:10
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto13:12
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC13:13
*** dlan <dlan!~dennis@> has joined #yocto13:14
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto13:14
*** abelal <abelal!~quassel@> has joined #yocto13:14
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-dkksrwbpffivayrc> has joined #yocto13:19
*** cference_ <cference_!> has joined #yocto13:21
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-dkksrwbpffivayrc> has left #yocto13:23
*** psnsilva <psnsilva!> has quit IRC13:26
*** drix <drix!c32a382b@gateway/web/freenode/ip.> has joined #yocto13:27
*** drix is now known as drou13:27
drouhi guys13:28
AzaToth_I'm trying to use yocto-autobuilder to build, and after a couple of builds, some files ends up with multiple .md5sum, for example core-image-minimal-initramfs-genebt05-20150723105004.rootfs.tar.gz.md5sum.md5sum13:32
*** jonathanmaw <jonathanmaw!> has quit IRC13:32
*** vmeson <vmeson!> has quit IRC13:33
AzaToth_I assume it's because the tmp dir isn't cleared after a build13:34
AzaToth_is it something I'm supposed to do manually?13:34
*** jonathanmaw <jonathanmaw!> has joined #yocto13:35
drouhas anyone got this from sanity check ?13:36
drouOE-core's config sanity checker detected a potential misconfiguration.13:36
drouPlease use a umask which allows a+rx and u+rwx13:36
drouI did a "find . -type f -exec chmod a+rx,u+rwx {} \;" but it's not working13:36
*** tsramos <tsramos!tsramos@nat/intel/x-gbzghrkubpdomqzj> has joined #yocto13:36
*** jonathanmaw <jonathanmaw!> has quit IRC13:37
*** tsramos <tsramos!tsramos@nat/intel/x-gbzghrkubpdomqzj> has quit IRC13:37
*** tsramos <tsramos!~tsramos@> has joined #yocto13:38
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto13:38
*** jonathanmaw <jonathanmaw!> has joined #yocto13:38
*** psnsilva <psnsilva!> has joined #yocto13:39
*** jonathanmaw <jonathanmaw!> has quit IRC13:40
bluelightningpidge: ^^13:40
abellonidrou: the issue is your umask, not you current permissions13:41
pidgeAzaToth_, the build dir should be getting cleared out, unless you have tmp somewhere else other than build dir?13:42
*** aehs29 <aehs29!~aehernan@> has joined #yocto13:42
*** jonathanmaw <jonathanmaw!> has joined #yocto13:48
AzaToth_pidge, have set TMP_DIR = "/home/buildbot/yocto-autobuilder/tmp" (and all others are rooted into /home/buildbot/yocto-autobuilder instead of under /tmp)13:51
pidgeAzaToth_: hrmm. do you want the md5sums?13:52
AzaToth_it's not important13:53
AzaToth_but I notice now it doesn't really cleanout at all13:53
AzaToth_all old builds are still in ~/yocto-autobuilder/tmp/deploy/images/genebt0513:54
drouabelloni: ah, so i should use umask instead of chmod, thx13:57
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto13:57
*** tsramos__ <tsramos__!~tsramos@> has joined #yocto13:59
*** tsramos <tsramos!~tsramos@> has quit IRC13:59
*** tsramos_ <tsramos_!~tsramos@> has quit IRC14:01
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto14:01
*** belen1 <belen1!Adium@nat/intel/x-fybhrocgdtijvdhp> has quit IRC14:02
AzaToth_pidge, which part of the system should delete stuff from tmp?14:09
pidgewell, normally14:09
pidgeat the start of every build we wipe yocto-autobuilder/yocto-worker/<buildername>/build14:10
pidgeputting SSTATE_DIR and DL_DIR somewhere else so they don't get wiped14:10
pidgeso that generally deletes tmp since we generally don't relocate it14:11
AzaToth_so I should disable TMP_DIR again14:11
pidgeI would. Let me look at making this a bit nicer. I would like to know if you see any performance impact of that.14:12
pidgeand if so what it looks like14:12
AzaToth_well, I saw now that TMP_DIR was commented out in the example; I moved everything off /tmp is it was a tmpfs and hadn't enough space14:13
AzaToth_I muse have in my hurry removed the # from TMP_DIR14:13
*** madisox <madisox!> has joined #yocto14:13
AzaToth_pidge, on an other note, I noticed latest commit to lib/python2.7/site-packages/autobuilder/buildsteps/ introduced a sntax error; where do I report/send patches if needed?14:16
pidgeAzaToth_, : cc: elizabeth.flanagan@intel.com14:16
pidgeAzaToth_, : ty!14:16
*** vmeson <vmeson!~rmacleod@> has joined #yocto14:17
kanucubluelightning: i tracked my missing library down to meta/recipes-support/icu/icu.inc14:23
bluelightningkanucu: oh?14:23
kanucuas far as i can see, the library is there whiole compiling, but isn't copyed to rootfs right14:23
kanucucp -r ${B}/lib ${D}/${STAGING_ICU_DIR_NATIVE}14:24
*** mansandersson <mansandersson!~Mans@> has quit IRC14:24
kanucushouldn't that command do that?14:24
bluelightningis a symlink?14:24
*** ryanstur_ <ryanstur_!> has quit IRC14:25
kanucuthere is  as library and  as syslink i think14:28
kanucubut onyl in build/tmp-glibc/sysroots/qemuzynq/usr/lib14:28
kanucunot on the target image14:28
*** Hector_ <Hector_!500fd832@gateway/web/freenode/ip.> has quit IRC14:28
*** tsramos__ <tsramos__!~tsramos@> has quit IRC14:29
bluelightningkanucu: right, so the symlink .so not being part of the main package is deliberate14:29
bluelightningit's only supposed to be used for development - binaries that link against libraries are supposed to link against the major-versioned symlink (or major/minor-versioned binary)14:30
bluelightningthus the .so symlink goes into the -dev package14:30
kanucuk, but then so.55.1 should exist?14:34
* paulg_ is seeing odd multilib fallout on the build appliance14:36
kanucubluelightnin: but it isn't14:36
kanucualso added in local.conf IMAGE_INSTALL_append = " icu"14:36
kanucunothing changed14:36
paulg_the deployed builder has all the libs in /lib64 but when that build tries to build itself, the native bins in the sysroot go looking in /lib (not lib64) and of course won't run.14:37
paulg_anyone recall some changes relating to multilib in say the last month or so?14:37
davisbboozzoo: I have a serial port connected now14:40
davissadly it seems to go by so fast i can not stop it and it starts booting frm emmc14:40
davisnvm, hit any key to stop boot14:41
*** marek__ <marek__!> has quit IRC14:41
davisso i am in uboot14:41
bluelightningkanucu: well I'm not sure what to tell you, if I build icu here and look inside the libicu18n package, it contains  /usr/lib/ and /usr/lib/
kanucu"look inside the libicu18n package"14:43
kanucuyou mean the target image?14:43
*** cference_ <cference_!> has quit IRC14:43
*** pidge <pidge!~pidge@2a02:8084:0:3000:91aa:74f1:2ca6:5d5c> has quit IRC14:44
*** lamego <lamego!lamego@nat/intel/x-svpdffhtrpejqfio> has joined #yocto14:45
kanucui might just found something14:46
kanucuwhen i run bitbake icu14:46
*** melio_cc <melio_cc!> has quit IRC14:46
kanucuit run icu_native14:46
kanucuwhich seems to refer to x86_6414:46
kanucuwhich is actually not the target system14:46
kergoththats what 'native' means14:46
*** davis <davis!> has quit IRC14:46
kanucugot icu -55 now..14:46
*** vincenet <vincenet!58bade28@gateway/web/freenode/ip.> has joined #yocto14:48
*** wadim_ <wadim_!> has quit IRC14:48
kanucuI added "install -m 0755 ${libdir}/* ${D}/usr/lib/" in do_install() now14:49
*** davis <davis!> has joined #yocto14:49
vincenetHello Guys, I am still trying to copy a lib from the sysroot to the images. I did some try with the FILE.. var but I need to learn more reading the doc. I have basic question about my last reading... When the sysroot folder is it populated ?14:51
*** benjamirc <benjamirc!~besquive@> has joined #yocto14:51
bluelightningkanucu: that shouldn't make any difference14:52
davisim trying to build my own image using yocto. I have copied the images to the sdcard using the README.hardware and I've booted with a debug serial port cable.14:52
bluelightningkanucu: if you're at that level you should be looking in the icu workdir to see what's actually happening14:52
daviswhen I boot, I see the first message after the uboot banner is spl_load_image_fat_os: error reading image args, err - -114:52
davisi take that as my image is not built correctly14:53
kanucubluelightning: i'll debug with -v now, the work directory/lib contains the necesarry file14:54
*** aehs29 <aehs29!~aehernan@> has quit IRC14:55
kergothvincenet: you really shouldn't be doing that. the sysroots area is specifically for use by bitbake to share content between recipes to satisfy dependencies, not for the user to poke at directly. If you want something from your build, pull it from the binary packages14:57
*** benjamirc <benjamirc!~besquive@> has quit IRC14:59
*** benjamirc <benjamirc!~besquive@> has joined #yocto15:00
vincenetkergoth : in my target is missing and I try to add in my recipe : FILES_lighttpd += "${prefix}/${BASELIB}/" but many question left. Is it correct syntax, is it really binary from lighttpd, and more widely how to print value of a var from recipe. What do you mean from the binary packages ? Should I explore lighttpd recipe ?15:03
kergothwhen you build a recipe in bitbake, binary packages are created (ipk, deb, or rpm) in tmp/deploy/<package type>. those packages are then used to build images. fairly sure this is covered by the documentation, as is the use of FILES15:04
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC15:04
kanucuwhat is the ${} variable for the target sysroot?15:05
*** robher <robher!sid20343@gateway/web/> has joined #yocto15:05
kergothbitbake -e is how you examine bitbake variables, this is also in the documentation15:05
kergothkanucu: see meta/conf/bitbake.conf for the main variables, specifically see the STAGING variables15:06
bluelightningkanucu: FYI, if you're looking at poking stuff in there directly, don't do that15:06
*** belen1 <belen1!Adium@nat/intel/x-tkwlhckwzujnmlud> has joined #yocto15:08
* kergoth re-runs oe-selftest to sanity test v3 of his bbpath plugin loading bits15:09
davishmm, i missed this. At the start of README.hardware for the beaglebone it says to mmc dev 1 and then mmc erase 0 512 to force the device to boot from sdcard.15:09
daviswhen I boot the target and get to a bash prompt, i try that mmc command but the debian image does not have mmc.15:10
kergothSo, sstate lockdown lets us make the build fail if something is changed that's locked down, but is there a way to force continuing use of the old sstate despite the changed checksums, rather than fatally erroring? Or, alternatively, to allow something to rebuild but not require that recipes that depend on it rebuild? I'm specifically concerned about the case where a release has gone out, and a bugfix update needs to be done, and we know the bugfix doesn't15:11
kergoth affect that recipe's ABI, and we don't wnat to have to redistribute half the dependency graph in binaries with the update15:11
davisapt-cache search mmc does not show anything which sounds like the mmc the doc is referring to15:11
kergothRP? I'm thinking I might need what we talked about as #2 (iirc) in that signatures bug, which we don't yet have15:11
bluelightningkergoth: it was supposed to work like that originally, I think that the final changes before it merged broke that15:11
kergothdavis: I'm curious about why you're asking about a debian distro in a channel for a tool that builds distros that aren't debian.15:12
bluelightningkergoth: it's one thing I've been meaning to follow up15:12
kergothbluelightning: ah. yeah, i seem to recall originally it was the intent to be able to lock down e..g the external toolchain in this way15:12
davisi'm trying to get this stock beaglebone to boot the yocto image I built.15:12
daviskergoth: i built the sato image and did the steps in the yocto README.hardware to load to a sd card, but when I boot the beagle it boots debian and not yocto on the sdcard15:13
daviskergoth: does that make sense?15:14
kergothdavis: #beagle might be the best bet for that15:15
daviskergoth: ok many thanks15:15
RPkergoth: It certainly was intended that you could force the signatures regardless of the actual value15:18
RPkergoth: I'm not remembering the #2 :/15:18
kergothah, not 2, it was 3 at
yoctiBug 5970: enhancement, Medium, 1.9, richard.purdie, RESOLVED FIXED, sstate signature generator issues15:19
RPkergoth: From the siggen code you can just force the value iirc15:20
kergothk, will take a look15:21
kanucubluelightning: you said you have the .so in the work directory, do you mean in the temp folder or sysroot(tareget)15:21
bluelightningkanucu: at the end of do_install it should be under image/ ; after do_package you should see it in packages-split/ under the appropriate package subdirectory15:22
*** pidge <pidge!~pidge@2a02:8084:0:3000:91aa:74f1:2ca6:5d5c> has joined #yocto15:23
davisso in the yocto README.hardware for beaglebone it says "step 4. If using core-image-base, .. skip to step 8" does that mean if you are trying to load image-base/sato or the board already has the images and you are trying to load any image skip?15:23
davisie does using in this sentence mean the target already boots this type of image or does it mean if you are trying to load this type of image?15:24
kanucubluelightening: i can confirm that15:26
kanucubitbake core-image-minimal15:26
kanucuand then it shoudl be in usr/lib ?15:26
*** sjolley <sjolley!~sjolley@> has quit IRC15:29
bluelightningkanucu: only if it's actually included in the image, either via a dependency or explicitly15:31
kanucuIMAGE_INSTALL_append = " icu"15:31
kanucuor has there to be somethin like icui18n15:32
bluelightningthe actual package name15:32
bluelightningi.e. libicui18n15:32
*** mansandersson <mansandersson!> has joined #yocto15:36
*** Ox4` <Ox4`!~user@> has quit IRC15:38
*** mansandersson <mansandersson!> has quit IRC15:40
*** Jefro <Jefro!> has joined #yocto15:53
*** sjolley <sjolley!~sjolley@> has joined #yocto16:01
*** Crofton|work <Crofton|work!> has quit IRC16:01
*** afxez0r <afxez0r!~afxez0r@> has joined #yocto16:01
*** belen2 <belen2!Adium@nat/intel/x-vzkzizcdcrwpkfke> has joined #yocto16:02
*** belen1 <belen1!Adium@nat/intel/x-tkwlhckwzujnmlud> has quit IRC16:03
*** dvhart <dvhart!dvhart@nat/intel/x-ndpbzftntalmtpuw> has joined #yocto16:03
kanucubluelightning: worked16:05
kanucuit was really something that simple16:06
*** aehs29 <aehs29!~aehernan@> has joined #yocto16:06
kanucuagain -.-16:06
vincenetGuys, to obtain in the image I finaly just add lighttpd-module-cgi in IMAGE_INSTALL. I was inspired when I was looking for lighttpd package in tmp/deploy/ but finaly I am still wonder if FILES could do the job dealing with ./build/tmp(...)/sysroots/eukrea-cpuimx25/usr/lib/mod_cgi.so16:07
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:08
*** Crofton|work <Crofton|work!> has joined #yocto16:08
*** Crofton|work <Crofton|work!> has quit IRC16:12
kergothah, nice, the tinfoil shutdown command patch i see16:13
*** tsramos <tsramos!~tsramos@> has joined #yocto16:14
*** Crofton|work <Crofton|work!> has joined #yocto16:14
*** SoylentYellow <SoylentYellow!> has joined #yocto16:26
*** jonathanmaw <jonathanmaw!> has quit IRC16:27
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto16:27
*** tsramos <tsramos!~tsramos@> has quit IRC16:31
*** jlasnier <jlasnier!> has left #yocto16:32
*** paulg <paulg!~paulg@> has joined #yocto16:32
*** vincenet <vincenet!58bade28@gateway/web/freenode/ip.> has quit IRC16:35
*** dvhart <dvhart!dvhart@nat/intel/x-ndpbzftntalmtpuw> has quit IRC16:37
*** dvhart <dvhart!~dvhart@> has joined #yocto16:37
*** tsramos_ <tsramos_!~tsramos@> has quit IRC16:42
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC16:43
*** nerdboy <nerdboy!> has joined #yocto16:45
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:45
khem`kergoth: I would like to install a symlink to a dir in nativesdk sysroot but barring all my efforts its not letting me do that16:46
khem`any ideas16:46
*** mansandersson <mansandersson!> has joined #yocto16:48
mansanderssonmorning, is it possible to remove a package from an image for a specific machine? e.g. removing u-boot-fw-utils from qemuarm builds16:49
*** dvhart <dvhart!~dvhart@> has quit IRC16:50
*** tsramos <tsramos!tsramos@nat/intel/x-fhcqkaselruecqju> has joined #yocto16:51
*** ryansturmer <ryansturmer!> has joined #yocto16:52
*** belen2 <belen2!Adium@nat/intel/x-vzkzizcdcrwpkfke> has quit IRC16:53
*** belen1 <belen1!Adium@nat/intel/x-nbnnswvnhflswifn> has joined #yocto16:53
khem`mansandersson: track down first the place where its added16:53
kergothkhem`: can you elaborate? where do you want the symlink, and what is it pointing to?16:54
mansanderssonkhem`: yes, that's easy16:54
mansandersson(at least in this case since it's I who have added it)16:55
*** ambrosius <ambrosius!~textual@> has joined #yocto16:56
*** belen1 <belen1!Adium@nat/intel/x-nbnnswvnhflswifn> has quit IRC16:58
bluelightningkanucu: I'm still a bit confused - didn't you add libicui18n to RDEPENDS_${PN} in a package what was in IMAGE_INSTALL ?17:00
*** diego_r <diego_r!> has quit IRC17:02
khem`kergoth: I am trying to create a symlink to usr/lib dir which is inside nativesdk sysroot couple of directories above the original sysroot17:02
kanucubluelightning: ye, actually i did17:02
kanucuno idea17:02
kanucuseems like a error onb my site17:03
*** benjamirc <benjamirc!~besquive@> has quit IRC17:03
khem`mansandersson: then whereever you have added use overrides to not do so for machine you wish17:03
*** jbrianceau is now known as jbrianceau_away17:04
*** afxez0r <afxez0r!~afxez0r@> has quit IRC17:04
khem`kergoth: its a crosssdk recipe where I am doing it17:04
mansanderssonkhem`: so something like IMAGE_INSTALL_remove_qemuarm = " u-boot-fw-utils" would work? Thought I'd tested that ..17:08
*** aehs29 <aehs29!~aehernan@> has quit IRC17:08
mansanderssonor IMAGE_INSTALL_append_othermachine = " u-boot-fw-utils" maybe17:08
*** belen1 <belen1!Adium@nat/intel/x-czemqcafysxbvxpw> has joined #yocto17:09
kanucubluelightning: I'm off now... thanks for your help!17:09
khem`mansandersson: remove shoudl17:11
*** ryansturmer <ryansturmer!> has quit IRC17:12
mansanderssonthanks, then I'll try that once again17:12
*** psnsilva <psnsilva!> has quit IRC17:13
khem`kergoth: i see that sysroot_stage_all puts it in components sysroot-destdir17:14
*** berton <berton!~fabio@> has joined #yocto17:14
khem`but then it doesnt appear in final sysroot17:14
*** mansandersson <mansandersson!> has quit IRC17:17
*** Biliogadafr <Biliogadafr!> has quit IRC17:21
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC17:28
*** ryansturmer <ryansturmer!> has joined #yocto17:28
*** aehs29 <aehs29!~aehernan@> has joined #yocto17:39
*** loggerbox <loggerbox!todor@nat/intel/x-uevenabrmvqxrxfp> has quit IRC17:50
*** loggerbox <loggerbox!todor@nat/intel/x-jjpvjbnoifrolknj> has joined #yocto17:54
*** ryansturmer <ryansturmer!> has quit IRC17:56
*** sameo <sameo!~samuel@> has quit IRC17:56
*** loggerbox <loggerbox!todor@nat/intel/x-jjpvjbnoifrolknj> has quit IRC18:01
*** ryansturmer <ryansturmer!> has joined #yocto18:01
*** loggerbox <loggerbox!~todor@> has joined #yocto18:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:01
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto18:08
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC18:13
*** dvhart <dvhart!~dvhart@> has joined #yocto18:22
fishey1With a recent poky update my rust-cross-arm package is now for some reason seen as rust-cross :( Was something changed about how PN_class-cross = "rust-cross-${TARGET_ARCH}" works?18:23
fishey1gdb & gcc appear somehow unaffected18:24
fishey1Ah, looks like there were some BBCLASSEXTEND changes... might be the issue18:24
*** dfaught <dfaught!> has joined #yocto18:35
fishey1Hrm, reverted a bunch but still was seeing rust-cross instead of rust-cross-arm. Issue cropped up somewhere between18:36
*** belen2 <belen2!> has joined #yocto18:36
* fishey1 has now gone back to his old branch and is still seeing the wrong PN18:39
*** afxez0r <afxez0r!~afxez0r@> has joined #yocto18:46
fishey1Looks fairly easy to reproduce: . Can someone tell me if I'm doing something horribly wrong there?19:01
*** belen2 <belen2!> has quit IRC19:02
*** ryansturmer <ryansturmer!> has quit IRC19:02
kergothfishey1: try PN_append_class-cross = "-${TARGET_ARCH}"19:02
kergothsee if that changes the behavior19:02
kergothyou may be running into an ordering issue with how cross.bbclass adds -cross to PN19:02
fishey1kergoth: nope, gives the same failure19:03
kergothRP would be the one to ask, most likely it's related to the recent changes that dropped update_data from the metadata19:04
fishey1kergoth: I looked, and it doesn't appear cross.bbclass is adding -cross (at least, not explicitly)19:04
fishey1I presume it's some inner class machinery that's doing the PN munging19:04
kergothah, yes, forgot about that19:05
fishey1Frankly, all of the cross packages seem to want PN_append = "-cross-${TARGET_ARCH}", it might make sense to add it to cross.bbclass :)19:06
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC19:06
fishey1Or rather: that's what gcc & gdb do, so I'm imitating them19:07
fishey1(not any other examples of cross.bbclass users I could find)19:07
*** benjamirc <benjamirc!~besquive@> has joined #yocto19:17
RPfishey1: cross.bbclass simply isn't setup to deal with BBCLASSEXTEND19:20
RPfishey1: looking at the code, when the class extend sets PN, it clobbers your override now19:23
RPfishey1: I'd guess that -                d.setVar("PN", "%s-%s" % (pn, name))19:24
RP+                d.setVar("PN", "%s-%s" % (pn, name), parsing=True)19:24
RPon would 'fix' that19:24
RPwhether that is the right way to fix it is another question19:24
fishey1RP: Ok, then: 1) why wouldn't it be the right way to fix it? 2) what things are bbclasses required to do to support BBCLASSEXTEND?19:25
*** phantoneD <phantoneD!> has joined #yocto19:26
RPfishey1: perhaps you could confirm I'm guessing right before we cross to those things19:27
fishey1Ok, I'll try it out19:27
* RP is sadly overwhelmed with things right now :(19:27
*** phantoxeD <phantoxeD!> has quit IRC19:29
*** hugovs <hugovs!~hugo@> has quit IRC19:31
*** [Sno] <[Sno]!> has quit IRC19:41
fishey1RP: interestingly, that works (both PN_append_class-cross and PN_class-cross), but the first time required that I `rm -rf tmp` (otherwise it kept the old PN without that).19:43
RPfishey1: I suspect an rm tmp/cache would have been enough19:44
RP(it just needed a reparse)19:44
RPtouch <recipe> would also work19:45
fishey1I see. So given that adding `parsing=True` seems to give the behavior I'm after, I think the 2 queries from earlier are relevent again :)19:46
*** jchonig <jchonig!> has quit IRC19:46
*** jchonig <jchonig!> has joined #yocto19:49
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto19:57
*** tsramos <tsramos!tsramos@nat/intel/x-fhcqkaselruecqju> has quit IRC20:00
kergothHmm, what's the process for adding selftests, do we need to add tests to testopia before adding the tests to the code?20:01
rburton(well, i don't think so)20:03
kergothso the test case numbers are optional in that case, i assume?20:03
-YoctoAutoBuilder- build #395 of nightly-intel-gpl is complete: Success [build successful] Build details are at
rburtonfiling testopia things means they'll be tracked a lot better though20:03
*** tsramos_ <tsramos_!~tsramos@> has quit IRC20:04
* kergoth is not a qa guy, so unit tests are about the most he ever bothers with :)20:04
rburtonusually, ditto20:05
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto20:06
* kergoth goes ahead and emails the patches to add the tests and will see how it goes20:07
khem`kergoth: did you see my snippet ?20:09
aehs29I'm getting .debug folders on my packages-split/$PN folder, and QA tests are complaining about it20:09
aehs29does anyone have any idea why that might be happening?20:09
khem`packaging deficiency20:10
khem`you need to add them to FILES_${PN}-debug = "../.debug"20:10
aehs29khem`: ohh make sense20:10
aehs29thanks khem`:20:10
khem`it should be FILES_${PN}-dbg20:11
-YoctoAutoBuilder- build #406 of nightly-fsl-ppc-lsb is complete: Failure [failed BuildImages] Build details are at
*** belen2 <belen2!> has joined #yocto20:12
aehs29khem`: haha yeah20:12
*** ddalex1 <ddalex1!> has joined #yocto20:14
*** psnsilva <psnsilva!~psnsilva@> has joined #yocto20:16
*** ryansturmer <ryansturmer!> has joined #yocto20:23
kergothHmm, has anyone looked into optional use of —single-branch or equivalent fetching for our git clones to reduce the git mirror tarball size? admittedly the tarball would then be a bit more specific, since it'd only have the branches for the recipes which had their branches fetched, but in the case of gigantic git repositories it'd be of use20:26
*** lamego <lamego!lamego@nat/intel/x-svpdffhtrpejqfio> has quit IRC20:27
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC20:29
paulgprobably not going to help a lot with the kernel.   Are there other large repos we use that are polluted silly with dead end branches not merged into master?20:32
kergothhmm, that's a good point20:33
kergothnot sure20:33
kergothshallow would be potentially of more use, but also possibly more complex for the fetcher to deal with20:34
*** belen2 <belen2!> has quit IRC20:36
-YoctoAutoBuilder- build #405 of nightly-x86-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
paulgi just checked 3.19 and zeddii has already ensured there are no stray stable branches or tags there that we don't explicitly need, so all their content should be gc'd away.20:38
*** jedix <jedix!> has joined #yocto20:38
*** lamego <lamego!lamego@nat/intel/x-tgzjvbhujcsxisfj> has joined #yocto20:40
-YoctoAutoBuilder- build #407 of nightly-non-gpl3 is complete: Failure [failed CheckForGPLv3] Build details are at
kergothpaulg: ah, thanks, good to know20:44
*** jimBaxter <jimBaxter!> has quit IRC20:44
*** hugovs <hugovs!~hugo@> has joined #yocto20:45
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto20:50
*** jkridner_ <jkridner_!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto20:51
*** ryansturmer <ryansturmer!> has quit IRC20:51
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC20:52
*** lamego <lamego!lamego@nat/intel/x-tgzjvbhujcsxisfj> has quit IRC20:53
*** zerus <zerus!> has joined #yocto20:53
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has quit IRC20:54
*** [Sno] <[Sno]!> has joined #yocto20:56
*** vmeson <vmeson!~rmacleod@> has quit IRC20:59
*** dfaught <dfaught!> has quit IRC21:03
*** lamego <lamego!~lamego@> has joined #yocto21:06
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto21:08
*** lamego <lamego!~lamego@> has quit IRC21:10
*** nighty-_ <nighty-_!> has quit IRC21:11
khem`kergoth: shallow clones ?21:12
khem`it works in principle21:12
khem`but its not useful when you do development21:13
khem`its ok for build ops21:13
*** tsramos <tsramos!~tsramos@> has joined #yocto21:14
-YoctoAutoBuilder- build #400 of nightly-qa-logrotate is complete: Success [build successful] Build details are at
kergothagreed. but quite often folks aren't doing active development with oe anyway, or if they are, they use externalsrc21:15
*** davis <davis!> has quit IRC21:18
*** paulg <paulg!~paulg@> has quit IRC21:18
kergothhmm, pflask works pretty well as a systemd-nspawn alternative21:21
khem`bitbake -e hangs for me for some days now21:21
khem`anyone seeing21:22
khem`kergoth I tend to agree21:22
khem`with shallow clones21:22
kergothhmm, think i've mostly seen -p hangs rather than -e so far21:22
*** jkridner_ <jkridner_!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:22
*** lamego <lamego!~lamego@> has joined #yocto21:23
kergothof course, shallow clones tend to be relative to a branch afaik, so unless we know the distance from the branch= value to the SRCREV, we won't know how shallow to go, unless we can fetch up to that commit rather than a branch, haven't tried. will have to poke at it21:24
*** tsramos <tsramos!~tsramos@> has quit IRC21:24
-YoctoAutoBuilder- build #406 of nightly-fsl-arm-lsb is complete: Failure [failed BuildImages BuildImages_1 BuildImages_2] Build details are at
khem`bitbake -DDD -e gdb21:25
khem`and its stuck there with no messages21:25
kergothah, that's probably siimlar to what i've been seeing, random, haven't been able to repro it reliably21:29
*** zerus <zerus!> has quit IRC21:29
kergothand folks like rp don't seem to have seen it at all21:29
RPI do try and fix the ones I run into or can reproduce...21:31
kergothnot complaining, just hate it when that happens :)21:32
RPkergoth: testopia entries are optional, we just link them where we have defined test cases21:32
kergothtough to fix when people can't reproduce it21:32
kergothRP: ah, k, thanks21:32
khem`its quite consistent for me on master21:32
khem`and I have ubuntu 15.04/64bit stock21:33
RPkhem`: I also run that...21:33
khem`it started to happen few weeks back21:33
RPkhem`: The most suspect things are the shutdown lock knotty changes21:34
RPkergoth: FWIW there is a shallow clone bug open. The issue is it will mean using a different mirror tarball name21:34
RPand more codepaths through the fetcher21:35
khem`is what happens on Ctrl+C21:35
RPkergoth: just that recipe or all recipes?21:36
*** jmpdelos <jmpdelos!> has quit IRC21:38
*** hugovs <hugovs!~hugo@> has quit IRC21:38
RPkhem`: nothing too suspect in that backtrace21:38
khem`its always same bt21:38
RPkhem`: so its hanging in varhistory() ?21:39
RPkhem`: what does strace say its doing?21:39
*** jmpdelos <jmpdelos!> has joined #yocto21:41
-YoctoAutoBuilder- build #408 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at
*** sameo <sameo!~samuel@> has joined #yocto21:41
-YoctoAutoBuilder- build #402 of nightly-qa-pam is complete: Success [build successful] Build details are at
khem`strace keeps scrolling21:46
RPfishey1: basically cross.bbclass has none of the automated variable mapping that native/nativesdk/multilib have for BBCLASSEXTEND. Its assumed that cross recipes basically do most of the mapping themselves. Is the  parsing=True a real fix? I'm torn. Its an ugly way to make what you're doing work. There are some cases where it would need to wipe out overrides when applying the new PN valye21:46
khem`its trying to open  bbclass files and .conf files which are not there21:48
khem`so its in some sort of stat() mode forever21:51
khem`yeah and its going in circles21:55
kergothnicely spotted22:00
*** bfederau <bfederau!> has quit IRC22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC22:02
*** ryansturmer <ryansturmer!> has joined #yocto22:03
*** dmoseley <dmoseley!> has joined #yocto22:04
khem`it just may be that it has become too slow22:05
*** benjamirc <benjamirc!~besquive@> has quit IRC22:07
khem`RP: you might be having less layers in your mix I guess22:07
RPkhem`: quite likely22:08
khem`but it has worked well22:08
RPkhem`: -e should never be that slow, its likely locked itself into some kind of a loop22:08
khem`it would take 2 mins max to do a fresh parse of angstrom layers22:08
*** dvhart <dvhart!~dvhart@> has quit IRC22:08
*** dvhart <dvhart!dvhart@nat/intel/x-tgxbicfogmydgann> has joined #yocto22:09
RPkhem`: have you latest bitbake? There was a performance regression and I did push a fix today22:09
khem`I just disabled all extra layers and it became fast22:09
khem`today ?22:09
khem`I am on commit 5196bfa9639eed2b1e6452f45775551203f8eeb422:10
khem`Author: Richard Purdie <>22:10
khem`Date:   Wed Jul 22 23:30:15 2015 +010022:10
khem`    bitbake-selftest: Add -v option for verbosity22:10
khem`    Also document BB_SKIP_NETTESTS=yes parameter in --help output.22:10
khem`    Signed-off-by: Richard Purdie <>22:10
RPkhem`: right, it was in fact 24 hours about22:10
*** paul_ <paul_!> has joined #yocto22:10
RP24 hours ago22:10
khem`I am on top of tree22:10
RPkhem`: ok, you have the performance fix then22:10
khem`RP its easy to reproduce22:11
khem`pick like 20 layers and put them into you bblayers22:11
khem`and you will see the hit22:11
RPkhem`: well, obviously parsing will slow down with more layers22:13
RPkhem`: you're saying -e is slow in particular?22:13
khem`yes expected22:13
khem`but do you think watin for bitbake -e for 15 mins is acceptable ?22:13
RPkhem`: no, I didn't say that22:13
*** dvhart <dvhart!dvhart@nat/intel/x-tgxbicfogmydgann> has quit IRC22:14
khem`yes -e is slow22:14
RPkhem`: that is the first time you've put a number on it though22:14
*** dvhart <dvhart!~dvhart@> has joined #yocto22:14
RPkhem`: sadly I am maxed out. I really don't need something like this to debug right now :(22:14
khem`RP: its optimistic number22:14
khem`since I have left it running for more22:14
khem`and it never finished22:14
khem`and it was working fine few weeks ago22:15
RPkhem`: have you that strace handy?22:15
RPkhem`: can it be shared?22:15
khem`1.8 works ok22:15
khem`I can save it22:15
khem`and send it22:15
RPkhem`: there have been a lot of recent changes includeing the data store rework22:15
RPI still suspect infinite looping is more likely though22:16
RPmaybe with some of the path resolution changes22:16
RPand that is probably from a single layer.conf with some kind of problem in it22:16
*** ddalex1 <ddalex1!> has quit IRC22:17
khem`strace goes fast at beginning and slows down as time goes22:18
khem`I wonder if its eating up all memory22:18
RPkhem`: that backtrace was in the dependency tracking code so that seems likely22:19
RPand is consistent with the infinite loop theory22:19
RPthe backtrace is less consistent with that mind22:19
*** ryansturmer <ryansturmer!> has quit IRC22:19
khem`whats difference between -e and with out ?22:21
khem`since it works ok with out -e22:21
khem`parsing takes about 30 seconds and it goes into building stuff22:22
-YoctoAutoBuilder- build #401 of nightly-qa-skeleton is complete: Success [build successful] Build details are at
khem`RP: here
khem`its still running22:27
khem`but I uploaded the run so far has been 4 mins or so22:27
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto22:33
RPkhem`: I just need a piece of the log hopefully22:35
*** berton <berton!~fabio@> has quit IRC22:36
RPkhem`: variable history tracking is enabled with -e22:38
RPkhem`: notice how it keeps reloading That is very odd22:38
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC22:38
khem`yes I am observing22:38
RPkhem`: sounds like a stray import22:38
khem`import in some bbclass you mean ?22:40
-YoctoAutoBuilder- build #397 of nightly-mips-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
RPkhem`: I think it must be the import in BBHandler.py22:41
*** lamego <lamego!~lamego@> has quit IRC22:42
RP(the import data which then triggers an import data_smart)22:42
RPkhem`: other puzzling thing is why it finds /mnt/home/kraj/work/angstrom/sources/openembedded-core/meta/conf/documentation.conf yet keeps looking for a documentation.conf22:42
khem`thats true for some other confs22:44
khem`30% parsing done22:44
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has joined #yocto22:49
RPkhem`: Even with OE-Core, if I do "rm tmp/cache -rf; time bitbake -p" I see 4m52, if I do "rm tmp/cache -rf; time bitbake -e bash" I see 16m5422:50
RPkhem`: I think we've somehow slowed down the variable tracking code and -e parses with it enabled22:51
-YoctoAutoBuilder- build #62 of nightly-arm64 is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Building Toolchain Images_1] Build details are at
khem`looks so22:51
RPkhem`: whether this is a regression or you've got lucky with a hot cache in the past...22:51
RPkhem`: I see the data_smart even when its going quickly. Its something to look into to improve things though22:52
* RP throws the profiler at this, see where the time is being eatne22:53
RPkhem`: . Looking at the profile its almost certainly the datastore changes that have done this :/22:56
*** rburton <rburton!> has quit IRC22:59
RPkhem`: If you put a "continue" in the "for event in" loop in _setvar_update_overrides() it certainly makes things faster22:59
RP(bypassing the record() call)22:59
RPkhem`: I'll sleep on it but this is fixable, we just need a better way of recording overrides in the logs23:00
*** alimon1 <alimon1!> has joined #yocto23:11
*** MiskaX_ is now known as MiskaX23:12
*** dvhart <dvhart!~dvhart@> has quit IRC23:16
*** madisox <madisox!> has quit IRC23:17
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC23:18
-YoctoAutoBuilder- build #392 of nightly-arm-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #397 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at
*** psnsilva <psnsilva!~psnsilva@> has quit IRC23:26
-YoctoAutoBuilder- build #396 of nightly-ipk is complete: Success [build successful] Build details are at
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto23:31
*** nighty^_ <nighty^_!> has joined #yocto23:31
*** afxez0r <afxez0r!~afxez0r@> has quit IRC23:31
*** nighty^ <nighty^!> has quit IRC23:33
*** tf <tf!> has quit IRC23:33
*** tf <tf!> has joined #yocto23:33
*** cazze <cazze!> has quit IRC23:33
*** cazze <cazze!> has joined #yocto23:34
*** sjolley <sjolley!~sjolley@> has quit IRC23:40
-YoctoAutoBuilder- build #63 of nightly-rpm-non-rpm is complete: Success [build successful] Build details are at
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC23:57
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto23:57

Generated by 2.11.0 by Marius Gedminas - find it at!