Tuesday, 2016-08-16

*** aehs29 <aehs29!aehernan@nat/intel/x-umfpqmovaofwcruf> has left #yocto00:00
*** billr <billr!~wcrandle@> has quit IRC00:59
*** sameo <sameo!~samuel@> has quit IRC01:03
*** sujith_h <sujith_h!~toaster@> has quit IRC01:03
*** zeddii_home_ <zeddii_home_!~zeddii_ho@CPEe8de27b71faa-CMbcc810032faf.cpe.net.cable.rogers.com> has joined #yocto01:06
*** sujith_h_ <sujith_h_!~toaster@> has joined #yocto01:08
*** sujith_h_ is now known as sujith_h01:08
*** zeddii_home <zeddii_home!~zeddii_ho@CPEe8de27b71faa-CMbcc810032faf.cpe.net.cable.rogers.com> has quit IRC01:09
*** zeddii_home_ is now known as zeddii_home01:09
*** vmesons is now known as vmeson01:10
*** sameo <sameo!~samuel@> has joined #yocto01:24
*** nighty <nighty!~nighty@p001.gate.atson.jp> has joined #yocto02:17
*** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-zefobuqcvbvjeyps> has joined #yocto02:23
*** nighty <nighty!~nighty@p001.gate.atson.jp> has quit IRC02:26
*** nighty <nighty!~nighty@p001.gate.atson.jp> has joined #yocto02:26
*** nighty <nighty!~nighty@p001.gate.atson.jp> has joined #yocto02:28
*** sameo <sameo!~samuel@> has quit IRC02:37
*** bananadev <bananadev!~onlyester@> has joined #yocto02:48
*** bluelightning <bluelightning!~paul@> has joined #yocto02:52
*** bluelightning <bluelightning!~paul@> has quit IRC02:52
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto02:52
*** AgentElrond <AgentElrond!~ELROND@97-102-189-66.res.bhn.net> has joined #yocto02:57
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC03:06
*** AgentElrond <AgentElrond!~ELROND@97-102-189-66.res.bhn.net> has quit IRC03:08
*** ntl <ntl!~nathanl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto03:16
*** sujith_h <sujith_h!~toaster@> has quit IRC03:31
*** AndersD <AndersD!~anders@h83-209-191-235.cust.se.alltele.net> has joined #yocto03:49
khemI am struggling chasing errors like  do_image_tar: Taskhash mismatch e46ba58e3a9cdc353a94548fd66fb109 verses 88d394eba0f2c542200ed8b0ad4b867a03:49
khemthis started to happen with krogoth03:49
khemI see it with rpi images and also some internal images03:50
khemwhen I run bitbake-diffsigs it says basehash changed from 9bbc36cad4c9ade1a346c4b6bb6c6f75 to 138f22157ec470f60a2071db0f68a4e403:50
*** ntl <ntl!~nathanl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC04:17
*** AndersD <AndersD!~anders@h83-209-191-235.cust.se.alltele.net> has quit IRC04:28
*** maxin <maxin!~maxin@37-219-27-165.nat.bb.dnainternet.fi> has joined #yocto05:01
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto05:19
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC05:27
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto05:28
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto05:31
*** visaev <visaev!~visaev@> has joined #yocto05:33
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC05:36
*** qt-x <qt-x!~Thunderbi@> has joined #yocto05:39
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC06:11
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:18
*** eduardas_m <eduardas_m!~eduardas_@> has joined #yocto06:21
*** qt-x <qt-x!~Thunderbi@> has quit IRC06:24
*** qt-x <qt-x!~Thunderbi@> has joined #yocto06:32
*** vin <vin!~vincent@fsf/member/vin> has quit IRC06:34
*** vin <vin!~vincent@fsf/member/vin> has joined #yocto06:35
*** gtristan <gtristan!~tristanva@> has joined #yocto06:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto06:41
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-exdhkdbrwzfnrdby> has joined #yocto06:48
*** jbrianceau_away is now known as jbrianceau06:48
*** fl0v0 <fl0v0!~fvo@pD9F6B7EE.dip0.t-ipconnect.de> has joined #yocto06:55
*** t0mmy <t0mmy!~tprrt@> has joined #yocto06:56
*** maxin <maxin!~maxin@37-219-27-165.nat.bb.dnainternet.fi> has quit IRC07:09
*** rajm <rajm!~robertmar@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto07:09
*** yann <yann!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC07:13
*** agust <agust!~agust@p4FCB4322.dip0.t-ipconnect.de> has joined #yocto07:13
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has quit IRC07:19
*** obsrwr_ <obsrwr_!~otp-amois@> has joined #yocto07:20
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:21
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC07:24
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto07:26
CTtpollardkhem: common problem for me as well in various do_$tasks07:32
CTtpollardkhem: meta-raspberrypi have pushed a *fix* for it, but I'm still seeing it occur for other tasks, such as populate sdk07:32
CTtpollardI'm not sure what the solution is other than forcefully removing the check routine07:33
*** Anticom <Anticom!~timo.m@> has joined #yocto07:43
*** melonipoika <melonipoika!~jose@> has joined #yocto07:49
*** mwalle <mwalle!~mwalle@> has joined #yocto07:52
*** jku <jku!jku@nat/intel/x-ewijegcombirpzkz> has joined #yocto07:52
*** jku is now known as Guest7386707:53
*** jku <jku!jku@nat/intel/x-fvicqpmsfwesjfyn> has joined #yocto07:53
*** jku is now known as Guest7386707:53
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto07:55
rburtonkhem, CTtpollard: stop using variables that change in between the cooker doing the calculations and the worker starting - often DATETIME and so on.  if those are being used, whitelist them.08:03
*** yann <yann!~yann@85-171-21-92.rev.numericable.fr> has joined #yocto08:04
CTtpollardyeh it seems to be rogue DATETIMES in various classes08:04
*** jku <jku!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has joined #yocto08:09
*** jku is now known as Guest9606208:09
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC08:14
*** sno <sno!~sno@> has joined #yocto08:17
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto08:18
*** T_UNIX <T_UNIX!d4d3bd3c@gateway/web/freenode/ip.> has joined #yocto08:24
eduardas_mHello. I am using the DART-6UL board from Variscite. I have problems related to using Qt5 with linuxfb plugin on a Yocto build. Are there people here working with a similar setup here? I have tried writing on the qt channel, but as far as I understand few people there have anything to do with embedded development. What would be the most appropriate place to get answers on Qt5 + Yocto related questions?08:25
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC08:33
AnticomHi all. Wasn't there an option you could set in your local.conf to only keep the last image that was built?08:33
*** seezer <seezer!seezer@quassel/developer/seezer> has quit IRC08:33
AnticomI do remember something like that but i can't find it in the docs anymore08:33
LetoThe2ndAnticom: there is rm_work, but thats a little bit dofferent08:34
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto08:34
redengineduardas_m, instead of asking why doesn't A work with B, do you know how A and B don't work together?08:34
AnticomLetoThe2nd: But there was no option to delete old images?08:35
LetoThe2ndAnticom: none that i knew of. but thats not an authoritative statement.08:35
AnticomIs rburton here?08:36
*** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto08:36
*** maxin <maxin!~maxin@37-219-27-165.nat.bb.dnainternet.fi> has joined #yocto08:37
* LetoThe2nd hands rburton the FLS hat.08:37
Anticomjoshuagl: thanks!08:38
joshuaglnp Anticom08:40
*** Guest96062 <Guest96062!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has quit IRC08:40
eduardas_mredengin: The point is I do not know what the proper way to rotate a Qt5 linuxfb application by 90 degrees on screen is and run into problems. My problem is elaborated here: http://forum.qt.io/topic/70184/weird-qcombobox-behaviour-under-qt-5-5-1-linuxfb-platform-yocto-build-for-imx6ul/208:44
eduardas_mI am not even sure whether this should be approached from the Qt framework side or from the framebuffer driver side.08:45
eduardas_mI am actually new to embedded linux so I wouldn't be surprised I am doing this completely wrong.08:47
LetoThe2ndisn't framebuffer kind of deprecated anyways?08:47
LetoThe2ndimx should have a decent usable drm, maybe even opengl implementation.08:48
redenginit sounds like a Qt bug based on expectations of Ubuntu builds08:48
eduardas_mimx6ul does not have a graphics accelerator, OpenGL is not usable08:48
redengineduardas_m, have you tried other distros?08:48
eduardas_monly Yocto and Ubuntu 14.04 (works properly with the latter)08:49
eduardas_mam investigating further08:49
redengineduardas_m, I'd try it out on other distros to determine if its just Ubuntu niceness that makes it work08:50
sveinseredengin: OOI, What has Ubuntu (or distros for that matter) to do with Variscites Qt5 yocto build?08:51
sveinseWe use Qt5 on imx, but we do use full fsl opengl thou08:52
redenginsveinse, all the plumbing back to decide where/how to place things within the display08:53
*** bananadev <bananadev!~onlyester@> has quit IRC08:54
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto08:55
eduardas_msveinse: what is the method that you would use to rotate a Qt5 widget application by 90 degrees then? perhaps using QGraphicsScene is actually the problem?08:57
eduardas_msveinse: do you use X window system?09:00
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC09:01
*** belen <belen!~Adium@> has joined #yocto09:04
sveinseeduardas_m: No, we have a full-screen linuxfb app09:05
eduardas_msveinse: thank you for sharing information, but could you tell anything about rotation? how would you go about implementing a portrait app in Qt5 under linuxfb?09:07
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto09:11
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC09:11
*** grma <grma!~gruberm@> has joined #yocto09:15
*** grma <grma!~gruberm@> has quit IRC09:16
*** grma <grma!~gruberm@> has joined #yocto09:16
*** AndersD <AndersD!~anders@213-64-218-130-no126.business.telia.com> has joined #yocto09:16
CTtpollardis it still the process for patches for /classes to be sent to the oe-core ml?09:19
*** pauloalvarez <pauloalvarez!~pauloalva@> has joined #yocto09:20
sveinseeduardas_m: Not sure, unfortunately. But Qt honors some environment variables, such as  QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS=rotate=90 and QT_QPA_PLATFORM=eglfs09:22
CTtpollardand do all patches require a relevant bug-id?09:22
redenginCTtpollard, my experience is that you need to both suggest and offer to maintain09:24
*** nighty <nighty!~nighty@p001.gate.atson.jp> has quit IRC09:25
*** maxin <maxin!~maxin@37-219-27-165.nat.bb.dnainternet.fi> has quit IRC09:28
*** Crofton <Crofton!~Crofton@> has joined #yocto09:37
jubreduardas_m: I believe newer Qt5 releases will have a soft-opengl renderer, released under GPL309:40
*** florian_kc is now known as florian09:42
*** Crofton <Crofton!~Crofton@> has quit IRC09:45
sveinseIf I set FOO="1" in a.bb and inherit a, then it can be accessed with ${FOO} from b.bb, right. How do I override FOO from local.conf then?09:46
Ulfalizersveinse: you mean inheriting a class a.bbclass from a recipe b.bb, where a.bbclass sets FOO = "1"?09:49
*** maxin <maxin!~maxin@2001:998:22:0:657c:8573:13c2:de73> has joined #yocto09:49
Ulfalizerif you're meant to be able to set the variable in a configuration file, it will usually be set with ?= or ??=09:49
Ulfalizerin the bbclass that is09:50
sveinseUlfalizer: Yes, my bad. a.bbclass in my example above, yes09:50
Ulfalizerthat will leave the variable alone if it already has a value09:50
sveinselocal.conf is read first when parsing?09:52
Ulfalizersveinse: yep... the note i added to http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-debugging-viewing-variable-values might clarify things09:53
Ulfalizerfirst the configuration (.conf) files are parsed, and then your particular recipe (along with any bbclasses it inherits)09:53
Ulfalizerany variables set in the configuration files will be visible by the time recipes are parsed09:54
sveinseUlfalizer: Ah, great. The NOTE block in section 2.3.2 which you just referred to answered another of my questions09:55
Ulfalizerneat :)09:56
sveinseThe docs is great, but as a n00b you tend to get lost in all the information -- even if you have read it once. :D09:56
Ulfalizerthat note was added within the last week i think :)09:57
Ulfalizeri've added quite a lot of stuff to the 2.2. manuals09:58
sveinsehow do you determine ?= vs ??=. Am I right to assume: Use ?= and you'll know it when you need ??= ?09:58
sveinseI see PACKAGECONFIG is usually defined with ??=10:00
Ulfalizersveinse: ??= is when you don't care whether another assignment comes before or after the ??=. that other assignment will win either way.10:00
UlfalizerFOO ??= "foo"  means "at the end of parsing, check if FOO was assigned a value. if not, assign 'foo' to FOO."10:01
Ulfalizerit's a "last resort" default in a way10:02
sveinseTo summarize:  I put FOO ??= "defaults" into a.bbclass.  From b.bb I "inherit a" and can set FOO ?= "something else".  I can then also do FOO_pn-b="mylocal", right? Not FOO_pn-a?10:05
Ulfalizera ?= will always "win" over a ??=. if you have a FOO ?= "foo", then either that will assign "foo" to FOO, or FOO already had a value. either way, FOO will have a value at the end of parsing, and so the ??= value will never get assigned.10:07
Ulfalizerand yeah, FOO_pn-b would be the override that applies for b.bb. it's set based on the name of the recipe, not based on the name of the bbclass.10:08
sveinseUlfalizer: Great. Understood!10:08
Ulfalizeryou could look up the OVERRIDES variable to see the underlying mechanism behind overrides btw. i think it helps to understand how it works.10:08
Ulfalizerthe rest becomes mostly "guessable" then :)10:09
Ulfalizerfood time10:09
sveinseActually I did read the OVERRIDES section, and I found the docs to very confusing10:09
sveinseLet me see if I can find it and explain10:09
sveinsesection 3.2.1 in BB manual under "selecting a variable". The example lists OVERRIDES = "architecture:os:machine". I don't understand the significance of that list. At first I might think that these are the TEST_* variable to chose from, but then the next example with KBRANCH= does not show OVERRIDES being set.10:14
sveinseI've read this many times, and I just can't get my head around this10:14
sveinseSo either I'm slow, or perhaps this section needs some better examples10:15
jubrsveinse: Ulfalizer: datastore-copies: cool note, I inferred this myself after some painstakingly long debug sessions10:20
iontehi. is it possible to run a task with bitbake, without running the tasks it depends on?10:21
iontei want to run deploy task, but i don't want to run the compile task, even if code has changed in the recipe10:22
iontethis is to build a device tree without recompiling the entire kernel. so i change the dts in my recipe, run "bitbake -c unpack <kernel-recipe>" and then "bitbake -c deploy <kernel-recipe>". but the last command also triggers a complete rebuild which is not necessary and takes a lot of time.10:23
*** joshuagl <joshuagl!~joshuagl@> has quit IRC10:25
jubrionte: bitbake -c task -f10:31
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC10:31
Ulfalizersveinse: the way it works is that FOO_someoverride will only be applied of "someoverride" appears in OVERRIDES10:31
Ulfalizerso the current "configuration" (which recipe? which machine? etc.) is written to OVERRIDES, and that'll make those overrides apply10:33
Ulfalizerand yeah, the manual sometimes isn't as explicit as it could be10:33
*** psadro <psadro!~Thunderbi@> has quit IRC10:35
Ulfalizersometimes it makes things seem fancier than they really are :P10:35
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto10:35
sveinseUlfalizer: So there is something like OVERRIDES="${MACHINE}" behind the scenes and then the example of KBRANCH_qemux86 will be selected?10:36
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto10:37
Ulfalizersveinse: yep10:37
rburtonbitbake -e will show you the value of OVERRIDES etc10:38
Ulfalizerit adds some indirection with a variable called MACHINEOVERRIDES though, that's added ot OVERRIDES10:38
Ulfalizerbut that's just to confuse you ;)10:38
Ulfalizeralso, makes it easier to customize10:39
jubrpoky/meta/conf/bitbake.conf:OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}:forcevariable"10:39
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has quit IRC10:40
sveinseUlfalizer: brilliant. :D (and it took four sentences to understand what I could not read from the text). IM-very-HO you should add that to the KBRANCH example. That OVERRIDES is set with ${MACHINES} and that is what makes it select the alternative overrides.10:40
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto10:40
Ulfalizersveinse: i'm working on some other documentation atm. the documentation maintainer is very open to contributions though: https://bugzilla.yoctoproject.org/enter_bug.cgi?classification=Documentation :)10:41
sveinseUlfalizer: all right, thanks10:41
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC10:42
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto10:42
sveinserburton, I've been running a day or so with sstate cache on NTFS (via the fuse driver). It seems to be working perfectly. Perhaps thought you wanted to know10:43
LetoThe2ndsveinse: Neanderthal Technology Fireplace System?10:43
sveinseLetoThe2nd: Yes10:43
LetoThe2ndsveinse: i hear mammoth steak work nicely along that, too!10:44
rburtonsveinse: presumably because its a local disk and as you said, the file system is fine with the names, its windows that isn't.  sstate over SMB on a NTFS file system is likely not going to work.10:44
sveinseNo actually, NTFS in itself isn't so bad. It's windows front end which is10:44
sveinseThe reason I have NTFS btw, is because I share this drive with Win machines. And unfortunately (and it's plain stupid) there are no other modern FS which share well with windows :(10:45
LetoThe2ndsveinse: i know, have ntfs extensively too. usually little hassles. but this is just stuck in my mind: http://www.onefunsite.com/images/nt.gif10:45
sveinse:D LOL. Well, I'm representing a very little Linux bubble in our company. The rest is Windows-centric, so I'm very alone at times.10:46
sveinseI'm looking forward to my presentation to the SW director that you need at least 50GB and native Linux machine to do anything useful in Yocto10:47
sveinseI wonder how i can sugar that pill :P10:47
LetoThe2ndsveinse: tell him you need a 32way build box with 128G ram10:48
LetoThe2ndsveinse: then let him negotiate you down to your actual needs.10:49
LetoThe2ndand if he just says 'yes', you're set anyways.10:49
iontejubr: nope, that forces the task to be run, which in turn may run other tasks. in my case, forcing "deploy" after an "unpack" also runs "compile" etc10:49
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC10:50
sveinseWhat I'm planning on is having a large build server running linux, and let it populate the sstate cache. Most devs will do app development, so they'll work on one recipe only. If they then can utilize the sstate cache, they can probably get away with running the yocto build virtually.10:51
rburtonsveinse: to be fair the disk requirements of yocto basically mean spending £50 on a hard disk10:52
LetoThe2ndsveinse: hm, sounds very much like you actually want to handle them the extensible sdk10:52
rburtonsveinse: spinning rust is far more economical and the performance gain of ssd isn't as impressive as you'd like, given sufficient ram10:52
LetoThe2ndsveinse: which basically is a shrinkwrapped sstate for app developers to work on one recipe :)10:52
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto10:52
LetoThe2ndrburton: ++10:52
LetoThe2ndgiven enough ram, all ssds for OE stuff are moot.10:52
rburtonspeaking of which i really need to raid my 2tb disks10:53
sveinseLetoThe2nd: We do SDK today. We have a product on the marked running Yocto, developed by a subcontractor. They provides us with a SDK and a core-image. We then build our app and integrate that into the core-image.10:53
LetoThe2ndsveinse: mind, i explicitly said "extensible sdk", not just "sdk"10:54
LetoThe2ndsveinse: its a rather new facility that targets the app developer case amongst some others.10:55
Ulfalizerrburton: all yocto does in the non-sstate case to check whether a task needs to be rerun is to look for a stamp file for the task with a matching input checksum, right?10:55
sveinseLetoThe2nd: The problem is that the glue to build our apps and integrate into the core-image now is a proprietary build system built by me. I'm now moving towards making recipes of everything so that we can use bb for what its good at10:55
LetoThe2ndsveinse: see: extensible sdk, really.10:55
sveinseLetoThe2nd: I will, thanks10:55
Ulfalizeri think one thing that makes the sstate cache harder to understand at the moment is that the non-sstate case isn't explained10:56
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto10:56
rburtonUlfalizer: effectively yeah.  "has this been done"10:56
Ulfalizerok, thanks. i'm thinking of adding a section on stamps.10:56
*** pauloalvarez <pauloalvarez!~pauloalva@> has quit IRC10:56
LetoThe2ndrburton: i've conducted a few trivial tests with building on spinning rust vs. ssd vs. tmpfs. difference: neglectible, if you have enough ram that caches can take care of everything.10:56
sveinseOOI, why is the sstate cache sorting on hash-id, rather than filename?10:57
Ulfalizersveinse: you mean for the two-character subdirectories?10:57
sveinseHow much RAM are we talking about for decent spin-drive performance with a yocto build?10:57
Ulfalizerprobably because it gives an even spread in that case10:57
rburtonsveinse: 16gb to start with.  my current machine has 64gb...10:58
sveinseUlfalizer: Yes. Ah yes, make sense. Otherwise its like the debian repo syndrome. "lib/" is overfull :P10:58
rburton(old machine had 16gb, and after a build meminfo said that ~12gb was disk cache)10:58
LetoThe2ndsveinse: do a clean build with empty sstate, du -hs after finish, add 20% :-)10:58
Ulfalizersveinse: some characters are more common than others too :)10:58
rburtonsveinse, Ulfalizer: also performance: file systems don't like having a single folder with 50k files in10:59
Ulfalizeryeah, that's the original reason for having those two-character subdirectories at all i guess11:00
Ulfalizerotherwise everything could have been in a single directory11:00
rburton$ find /data/poky-master/sstate/ -type f|wc -l11:00
rburtoni was out by an order of magnitude :)11:00
sveinseLetoThe2nd: du + 20% = RAM size, that what you meant?11:00
LetoThe2ndsveinse: yeah.11:00
rburtonthat might be *a bit* over kill :)11:00
LetoThe2ndrburton: that 128g suggestion above was not a joke11:01
sveinseLetoThe2nd: That assumes extfs, doesn't it?11:01
rburtonyeah start with 128 and negotiate down to just 6411:01
sveinseDifferent fs have different caching schemes11:02
LetoThe2ndthe point is, building a core-image-minimal or such is usually not a problem with less ressources. but once you pull in qt or even chromium, stuff gets nasty when you're low on ram11:02
rburtonif you're not building qt/webkit/etc then you'll be "fine" with 16gb, but get as much as you can justify11:03
sveinsemy sstate cache is at 43Gb... But I'm working on two flavors of arm, intel and qemu against the same sstate cache11:03
LetoThe2ndrburton: thats a good bottom line.11:03
* rburton waits for kergoth to join in11:04
sveinsewhoah! ok. I'm standing in line all the way back :P11:04
LetoThe2ndmuch more important than 16gb ram vs. 32gb or so is, having a native environment.11:04
LetoThe2ndor at least some kind of docker/etc. container.11:04
sveinse(On request from my manager) I have actually on my list to benchmark the actual penalty from doing this virtual (against a phy disk)11:05
rburtonIT HURTS SO BAD11:05
* LetoThe2nd would guess a 4x-10x penalty.11:05
sveinseLet's hope so, because it's tied to funding...11:05
rburtonsveinse: obviously you need to throw more ram to the host to give the vm enough ram to play with11:06
LetoThe2ndsveinse: show him the following equation with the numbers appropriately filled in: if (time_for_tests * your_pay_per_hour) > your_wanted_invest -> just buy.11:06
sveinseLetoThe2nd: No, I don't think anybody will be unreasonable. I just have to quantify it to justify it.11:07
sveinseIs virtual build server just as bad? Our IT department runs a datacenter, so there is a requirement that every server is virtual.11:08
LetoThe2ndsveinse: thats only natural. and for investment of size, absolutely reasonable. but if we're talking about stuff thats in the sub-1k range, or maybe even sub-300, evalutaion quickly becomes pointless if its a one-off invest11:09
LetoThe2ndsveinse: depends on the kind of 'virtual'11:09
LetoThe2ndof course, i'm always speaking from my perspective11:10
rburtonif its a xeon beast tricked out with all the ram and you can get dedicates slices then the overhead won't be too much11:12
rburtonobviously thats a different experience to running oe builds inside virtualbox on a macbook air11:12
rburton(which i've seen)11:12
sveinseLetoThe2nd: Our current build server run under Hyper-V with a dedicated phy (SSD) drive. 16 CPUS (E5-2637), but only 8GB ram (which can be extended or course). It's performance for Yocto SDK based Qt app building is decent.11:13
sveinseI think I will propose adding a spin-drive and much more RAM11:14
LetoThe2ndyeah. still that same xeon certainly makes a difference between natively being linux and running xen or even lxc/docker with direct memory access, and some hyper-v thing that maybe even has to rely on file-based container images.11:14
sveinseTo my experience, the biggest improvement in a VM is getting direct access to storage11:14
LetoThe2ndthat and enough ram, yes.11:16
rburtonall this talk of xeon is good for my stock, keep at it11:20
sveinserburton: yes, your at Intel, right?11:20
LetoThe2ndrburton: other noble gases relevant for you too?11:21
-YoctoAutoBuilder- build #908 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/90811:21
sveinseLetoThe2nd: I don't think Xeon is a gas. Xenon is :P11:22
LetoThe2ndsveinse: pun intended :)11:22
rburtonsuccess \o/11:22
sveinseIntel Raon :P11:22
sveinseno wait, brand used11:22
LetoThe2ndHeium. gives you more vowels.11:23
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC11:24
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto11:25
sveinseI have to say I really like the sstate scheme. rm -rf tmp; bitbake core-image, and you're set in minutes11:29
sveinseMy recipe, which use EXTERNALSRC rebuilds quite a bit thou. I suppose it's because of the external-thing, right?11:31
*** BlitzBlizz <BlitzBlizz!~blitz@2001:638:102:36:e3aa:c03b:c3ec:41c6> has joined #yocto11:33
*** arkver <arkver!~arkver@host81-135-58-159.range81-135.btcentralplus.com> has joined #yocto11:34
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC11:38
*** berton <berton!~fabio@> has joined #yocto11:39
*** gleikeo <gleikeo!b2143441@gateway/web/freenode/ip.> has joined #yocto11:39
gleikeoi try to compile postgresql on krogoth branch but i have got an error checking Python.h usability... no | checking Python.h presence... no | checking for Python.h... no | configure: error: header file <Python.h> is required for Python | NOTE: The following config.log files may provide further information. | NOTE: /md0/gletourneur/projects/openembedded/oe-core/build/tmp-glibc/work/i586-oe-linux/postgresql/9.4.8-r0.0/build/config.log | E11:39
gleikeoany idea11:39
*** Crofton <Crofton!~Crofton@> has joined #yocto11:41
*** Crofton <Crofton!~Crofton@> has quit IRC11:46
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto11:57
simonlI'm trying to figure out why the meta-oe glog recipe no longer builds on my machine. It seems it tries to link to libgcc_s.so.1 from my host distro, because -L/usr/lib is passed to the linker when linking the tests11:58
*** istarilucky <istarilucky!~rlucca@> has joined #yocto11:58
simonlCould someone give some hint as to how it is supposed to work? libglog.la has libdir = /usr/lib so I guess that's where the -L/usr/lib comes from?11:59
rburtonwell, maybe.12:01
rburtonpastebin the actual logs?12:01
neverpanicHow do I find out why a setscene task failed? I just get a warning but no reference to a log file or any other output that would indicate what the problem actually was.12:02
neverpanicwarning is WARNING: Setscene task /home/clemens/dev/poky/meta/recipes-support/db/db_6.0.30.bb:do_packagedata (/home/clemens/dev/poky/meta/recipes-support/db/db_6.0.30.bb:do_packagedata_setscene) failed with exit code '1' - real task will be run instead12:02
neverpanicI'm pretty sure I broke this, but I need to be able to debug this to fix it.12:02
T_UNIXI'm trying to build qt 5.5.1 using dylan infrastructure. For some reason the qmake binary of the qtbase package is build for the build target, instead of the target arch.12:03
T_UNIXis that a bug that was overcome somewhen?12:03
rburtonbuilding target qtcore will build a target qmake, you want to build the native form first12:04
sveinseT_UNIX: Do you have DEPENDS += "qttools-native" in your recipe?12:04
T_UNIXsveinse: I have "grep qtbase-native * qtbase_5.5.1.bb:DEPENDS += "qtbase-native""12:05
T_UNIXI think qttools[-native] is not available in dylan release.12:06
sveinseT_UNIX: ok, sorry, then I don't know12:07
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has quit IRC12:07
simonlrburton: ^12:07
T_UNIXrburton: there is no qtcore target :-/ neither grep nor find could reveal one12:08
T_UNIXrburton: I'm not quite sure what's going on.. Either the -native qmake is packaged in the package stage of the qtbase recipe, or the qmake in qtbase is compiled with the wrong compiler :-/12:09
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto12:09
T_UNIXI'll have a closer look at the compile and install stages of the corresponding recipes..12:13
*** bluelightning <bluelightning!~paul@fixed-203-32-189-203-32-226.iusacell.net> has joined #yocto12:16
*** bluelightning <bluelightning!~paul@fixed-203-32-189-203-32-226.iusacell.net> has quit IRC12:16
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto12:16
*** jkridner|pd <jkridner|pd!~jkridner@c-68-61-101-211.hsd1.mi.comcast.net> has joined #yocto12:29
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC12:30
*** rZr <rZr!~RzR@unaffiliated/rzr> has left #yocto12:30
*** joshuagl <joshuagl!~joshuagl@> has quit IRC12:31
*** dv_ <dv_!~quassel@> has quit IRC12:37
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:37
*** dv <dv!~quassel@> has joined #yocto12:38
neverpanicwhere would I find logfiles for a setscene task?12:38
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto12:44
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC12:47
*** zeddii <zeddii!~bruce@> has joined #yocto12:49
*** paulg <paulg!~paulg@OTWAON23-3096772825.sdsl.bell.ca> has joined #yocto12:54
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto12:54
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto12:55
*** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has joined #yocto12:57
*** BlitzBlizz <BlitzBlizz!~blitz@2001:638:102:36:e3aa:c03b:c3ec:41c6> has quit IRC12:58
HyP3rCan someone tell me the difference of DEPENDS and RDEPENDS? I don't get it out of the refreence13:06
rburtondepends is build time, rdepends is runtime13:08
HyP3rok, so if I do a only depends, Yocto will not include this package into the rootfs?13:08
rburtonyes, but if the depends results in eg your application linking to a library, that library's package is automatically added to RDEPENDS13:09
rburtonwhich is why you never see recipes rdepending on libc and so on13:09
HyP3rSo is it better to define everything twice, DEPENDS and RDEPENDS or only RDEPENDS?13:10
rburtonif the runtime depend is a library then it will be automatically added13:11
rburtonanything else depends on context13:11
rburtona package will build-depend on make but won't need it at runtime13:11
rburtona package may dlopen() a library so it won't get detected automatically, so you need to add it to RDEPENDS13:11
rburtonan app may call other apps, so you'll need them in RDEPENDS but not DEPENDS13:11
rburtonthere's no One True Answer, you just have to reflect reality in the packaging13:12
HyP3rSo I will look through my bunch of recpies, I guess I did it wrong13:12
*** gleikeo <gleikeo!b2143441@gateway/web/freenode/ip.> has quit IRC13:16
UlfalizerHyP3r: the latest version of the reference manual has more information by the way: http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-DEPENDS13:25
Ulfalizeri added the note because i've seen a lot of people being confused by DEPENDS vs. RDEPENDS13:26
Ulfalizerthe newer versions of the manual have a lot more stuff in general13:26
UlfalizerHyP3r: a good rule of thumb is to only use RDEPENDS if you're really sure what you're doing, and always use DEPENDS otherwise13:29
UlfalizerRDEPENDS is only needed if you have dependencies between packages that yocto can't infer by itself, e.g. if some program assumes that another program is installed because it runs it directly13:30
Ulfalizerfor library dependencies, yocto can figure it out by itself13:31
*** rcw <rcw!~rwoolley@> has joined #yocto13:35
Ulfalizer...except e.g. in the dlopen() case i just noticed rburton mentioned :P13:42
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC13:44
*** gtristan <gtristan!~tristanva@> has quit IRC13:45
*** Anticom <Anticom!~timo.m@> has quit IRC13:47
HyP3rUlfalizer: in my case the image generation recpie points with IMAGE_INSTALl to some of my packages. E.g. foo-www. This package does not use autotools or something, it has only a mkdir -p ${D}/www and cp -Rd ${S}... ${D}...13:48
HyP3rSo I'm pretty sure that can't see that this foo-www package needs python, apache, mod-wsgi, django, ...13:48
HyP3rSo I decied to add some RDEPENDS, if I understood it correct13:49
*** benjamirc <benjamirc!besquive@nat/intel/x-iutgdxdnnxjqbrmr> has joined #yocto13:50
HyP3rBut I gues I have to to a cleanall and recompile everything to make sure I have enough build dependencys13:50
Ulfalizeryeah, unless there's some relevant bbclass that adds the RDEPENDS for you, and they're not straightforward library dependencies, you'll have to declare them  yourself in RDEPENDS13:50
UlfalizerHyP3r: see http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#checking-for-missing-build-time-dependencies re. missing build dependencies13:51
*** jkridner|pd <jkridner|pd!~jkridner@c-68-61-101-211.hsd1.mi.comcast.net> has quit IRC13:52
Ulfalizertldr; $ wipe-sysroot + rebuild  should be a safe bet13:52
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:52
HyP3ryeah this tmp dir deleting sounds good,13:52
Ulfalizeror just run wipe-sysroot13:53
*** AndersD <AndersD!~anders@213-64-218-130-no126.business.telia.com> has quit IRC13:53
HyP3ryeah I like your too long didn't read :P13:54
HyP3rAnother thing I'm currently handling but I'm not sure if this way is good: deamons and programs like samba, ntp, apache2, avahi do have configuration files, and I want to insert my own configuration files. I solved that by createing bbappend recpies for all those recpies (samba, apache, ...) and appened the install phase: do_install_append(). While this routine I added (copy over) my own configuration13:56
HyP3rI this a good way?13:56
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC13:56
*** maxin <maxin!~maxin@2001:998:22:0:657c:8573:13c2:de73> has quit IRC13:57
Ulfalizerprobably not a horrible approach at least13:58
*** ntl <ntl!~nathanl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto13:58
Ulfalizercheck out the CONFFILES variable too13:58
HyP3r... not a horrible approach ... ooookay. Is there a better way?13:59
Ulfalizernot sure13:59
HyP3rwell then I think its ok, for me, third week with yocto \o/13:59
Ulfalizercan't think of anything for "global" configuration files13:59
*** lamego <lamego!~jose@> has joined #yocto14:00
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC14:02
*** qt-x <qt-x!~Thunderbi@> has quit IRC14:04
*** madisox <madisox!~madison@> has joined #yocto14:08
*** igor2 <igor2!~igor@> has joined #yocto14:08
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:09
*** igor3 <igor3!~igor@> has joined #yocto14:12
*** igor2 <igor2!~igor@> has quit IRC14:14
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:17
*** jkridner|pd <jkridner|pd!~jkridner@c-68-61-101-211.hsd1.mi.comcast.net> has joined #yocto14:18
*** nighty <nighty!~nighty@s229123.ppp.asahi-net.or.jp> has joined #yocto14:20
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC14:22
*** jkridner|pd <jkridner|pd!~jkridner@c-68-61-101-211.hsd1.mi.comcast.net> has quit IRC14:26
*** AgentElrond <AgentElrond!~ELROND@97-102-189-66.res.bhn.net> has joined #yocto14:26
*** jkridner <jkridner!~jkridner@2601:409:8500:9430:2941:9702:841e:44> has joined #yocto14:29
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:29
AgentElrondFor anyone familiar with qemu, is it normal that the last line I see is "main-loop: WARNING: I/O thread spun for 1000 iterations" when I try to run my yocto-built image on qemuarm?14:30
AgentElrondGoogle suggests some people had freezing problems for this but with other operating systems.14:30
*** maxin <maxin!~maxin@37-219-27-165.nat.bb.dnainternet.fi> has joined #yocto14:33
*** aehs29 <aehs29!aehernan@nat/intel/x-tythmdyrzoxsafcu> has joined #yocto14:34
*** visaev <visaev!~visaev@> has quit IRC14:47
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC14:47
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC14:48
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:49
*** caiortp <caiortp!~inatel@> has joined #yocto14:49
*** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has joined #yocto14:52
*** gtristan <gtristan!~tristanva@> has joined #yocto14:53
*** paulg <paulg!~paulg@OTWAON23-3096772825.sdsl.bell.ca> has quit IRC15:15
*** maxin <maxin!~maxin@37-219-27-165.nat.bb.dnainternet.fi> has quit IRC15:21
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC15:22
*** Crofton <Crofton!~Crofton@> has joined #yocto15:23
*** eduardas_m <eduardas_m!~eduardas_@> has quit IRC15:34
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:d937:3976:9319:8236> has joined #yocto15:37
*** armpit <armpit!~akuster@2601:202:4001:9ea0:94d9:eae7:71b3:4646> has quit IRC15:44
*** jbrianceau is now known as jbrianceau_away15:47
*** billr <billr!~wcrandle@> has joined #yocto15:52
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto15:58
HyP3rIs there a way to configure a recpie that way, so every build time its completely _rebuilt_?15:59
*** t0mmy <t0mmy!~tprrt@> has quit IRC15:59
*** rajm <rajm!~robertmar@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC15:59
*** Crofton <Crofton!~Crofton@> has quit IRC16:01
*** stephano <stephano!stephano@nat/intel/x-auffyyhiabmxszhk> has joined #yocto16:01
jubrHyP3r: http://www.crashcourse.ca/wiki/index.php/BitBake_task_flags16:01
jubresp [nostamp]16:01
HyP3rok, but what should I write do_install[nostamp] or do_compile[nostamp], or...?16:03
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC16:04
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto16:04
jubrDepends on how early you want it to start? At do_compile? do_configure? do_unpack?16:04
HyP3rso I can also do do_fetch[nostamp] so the package will be allways fetched, configured, compiled...16:05
CTtpollarddo_unpack is quite common16:05
* jubr made a mental note of the [dirs] flag, a bit nicer than all those `mkdir -p` in do_install16:05
HyP3rBecause I also need that this packages I always fetched16:06
CTtpollardI've used nostamp there on a few problematic recipes that don't play nice with ssate16:06
jubrCTtpollard: yep, do_unpack also ensures teh do_patch is run16:06
*** fl0v0 <fl0v0!~fvo@pD9F6B7EE.dip0.t-ipconnect.de> has quit IRC16:06
HyP3rIs this correct?16:06
CTtpollardHyP3r: yes, if you need it to fetch every time16:07
HyP3ryes :(16:07
CTtpollardso it will refetch, unpack configure etc etc16:08
HyP3rIts nice that yocto has for everythiing a solution16:08
* jubr agrees16:09
*** khem <khem!~khem@unaffiliated/khem> has quit IRC16:12
*** Crofton <Crofton!~Crofton@> has joined #yocto16:15
kergothonly downside is there's often more than one solution, and it's not always clear which is best :)16:16
kergothHyP3r: re: overriding config files via bbappend, recipetool's appendfile command automates that process, can save some time over doing so manually, in case you didn't know16:16
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC16:17
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto16:17
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto16:18
*** billr <billr!~wcrandle@> has quit IRC16:22
HyP3rkergoth: I don't even know recpietool16:23
kergothrecipetool and devtool are extremely valuable tools, really helpful and time saving16:23
*** vmesons <vmesons!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto16:23
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC16:23
AgentElrondkergoth:  I tried doing a directory rename like I mentioned yesterday16:23
AgentElrondI delete tmp but made no other changes.  Running bitbake again fails trying to find the absolute path of my layer.conf file -- any ideas?16:24
khemCTtpollard: that rpi change was from me :) but its not fixing all cases. One of these days I will nail it16:24
khemrburton: the problem is that vardepexclude does not help when DATE and TIME are used inside anonymous python snippets16:24
kergothHyP3r: recipetool appendfile meta-mylayer /etc/some-file /path/to/my/replacement/file -> writes a .bbappend tinto the meta-mylayer layer for whatever recipe provides /etc/some-file (assumign it's been built already, or you can specify the recipe with -r)16:25
khemrburton: or even names python functions16:25
khemor say I could not beat bitbake to accept it16:25
kergothkhem: anonymous python won't affect the checksums, and named functions you can use vardepsexclude on16:25
khemthats the nub of the issue I am seeing16:25
* kergoth yawns16:25
HyP3rkergoth: sound good, I'll try to find some documentation about that16:25
khemkergoth: thats what I thought but it seems base hash does account for anon python16:26
khemI have an example :016:26
kergothanonymous python code was always explicitly *not* included. the results of what the functions do can affect che ksums, but not their code16:26
jubrkergoth: Tnx! recipetool looks nice, will look into that one!16:27
AgentElrondkergoth:  Would removing build/tmp and manually updating paths in build/conf be sufficient for an overall absolute path change?16:27
kergothincluding the code would be a clear bug IMO. the whole point of anonymous python is to alter metadata, and the effects of that will affect other checksums regardless, so there'd be no point including it16:27
kergothAgentElrond: yes, altering bblayers.conf would fix yourl ayer.conf error. that + wiping tmp would do16:28
khemkergoth: see https://gist.github.com/kraj/63a3f0ac6cd6af31e8e57d4fd35a305916:28
kergothkhem: that won't work, you're putting it on the indirect thing, which doesn't work given the current implementation16:29
khemkergoth: thats a abridged snippet with intesting bits, now if I comment out stamp = assignment to be an empty string all works ok16:29
kergothkhem: tweak_image_name[vardepsexclude] += "DATE TIME"16:29
AgentElrondkergoth:  Thanks!16:31
*** phoo1234567 <phoo1234567!~phoo12345@c-75-69-172-183.hsd1.nh.comcast.net> has joined #yocto16:31
khemkergoth: see https://gist.github.com/kraj/010ac278ecb7b69b35403136935ad57116:32
*** joshuagl <joshuagl!~joshuagl@> has quit IRC16:32
khemthats with above16:32
kergothhmm, sounds like a bug in the checksumming code somewhere16:33
kergothbasehash mismatches are such a pain to diagnose16:33
kergothtaskhash too, but still16:33
jubrkergoth: crap, we're stuck with Freescale's bsp based on fido, my `recipetool --help` only lists `create` :(16:33
rburtonkergoth: can whatdepends -r show the package that i was looking for?  in the connman in core-image-sato example, it doesn't list connman.16:34
*** billr <billr!~wcrandle@> has joined #yocto16:39
khemjubr: always a good thing to move forward and upgrade16:41
jubrkhem: preaching to the choir, baby. New device needs to be up & running & into field trials first...16:43
AgentElrondkergoth:  You were of course correct.  After updating bblayers.conf and blowing away tmp, the build looks like it may finish in 20 minutes which is better than 3 hours.  :P16:47
AgentElrondkergoth:  The only notable exception is that the Linux kernel got recompiled for some reason.16:47
khemkergoth: any workarounds you can think of ?16:58
khemignoring date/time in hashes in python functions16:58
*** T_UNIX <T_UNIX!d4d3bd3c@gateway/web/freenode/ip.> has quit IRC16:58
*** grma <grma!~gruberm@> has quit IRC16:59
kergothabsolute worst case you could add both to the basehash whitelist, that should exclude it across the board, i expect16:59
*** Crofton <Crofton!~Crofton@> has quit IRC17:00
*** AgentElrond <AgentElrond!~ELROND@97-102-189-66.res.bhn.net> has quit IRC17:01
RPkergoth: thanks for the review btw, I tweaked the commit message you mentioned. I've posted the main multi-config patch now, about to put it into -next and give it wider testing on the AB17:02
sveinseWe talk alot about sharing sstate cache. But is it possible to share download dirs as well?17:02
RPkergoth: biggest worry now is whether I've missed some API changes somewhere :/17:02
RPIts a pain but could have been a lot worse17:02
ntlsveinse: yes, the conf variable is DL_DIR17:07
*** benjamirc <benjamirc!besquive@nat/intel/x-iutgdxdnnxjqbrmr> has quit IRC17:08
sveinseWill a yocto build always max out memory (and swap) regardless of how much memory you throw at it? It an impressive amount of ps which is started.17:10
neverpanicsveinse: depends on what you do with it and many threads you start17:11
neverpanictemplate-heavy C++ usually needs more memory than compiling C17:11
sveinseThe default, which is N jobs and N parallel make, IIRC17:11
neverpanicyeah, and N depends on $num_cpus, so whether your memory is maxed out depends on the relation between the number of CPUs you have and the amount of memory17:12
khemsveinse: ntl: its not safe to have same DL_DIR shared in different workspaces due to the fact that they can race against each other if building in parallel17:12
*** Crofton <Crofton!~Crofton@> has joined #yocto17:13
khembetter is to setup a source mirror in vicinity17:13
sveinseI just upped our build server from 8G to 16G, and it seems it is CPU bound, with the occasional page miss17:14
khemif you point DL_DIR to same location, it actually means you are allowing read and write operations from different workspaces17:14
sveinseI have a suspicion that if I threw 64G RAM at it, the sheer number of processes would still max out memory at some point17:14
khemsveinse: unless you build something like webkit/chromium, more memory is only going to be used as file cache, which in itself is an improvement17:15
khemsveinse: more memory is going to give you a better performance no matter what17:15
khemunless you have fast SSDs17:15
khemin which case it may be less of improvement17:15
khemlike its useless to use distcc now a days, there once was a time when we were cpu bound and distcc would be helpful, now a days the distcc distributor node becomes a bottleneck quickly17:17
sveinseWell, I have 16 core Xeon build server, running guest on a Hyper-V VM, with direct access to a SSD. Upping the memory from 8G to 16G helped (I think). If I need more, I need to have a clear rationale for it. Not just because I want it. Server RAM is expensive17:17
halfhalowebkit/chromium is plenty happy to use 72+ cores and massive amounts of memory17:18
sveinsekhem: I do share DL_DIR amongst workspaces. Luckily, the build thread is singleton, so only one bitbake is running at one given time :D17:19
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto17:20
*** adelcast <adelcast!~adelcast@> has joined #yocto17:20
khemjubr: yes thats modus operandi unfortunately for many in industry, I am a big believer in rolling releases, and moving all testing and QA to left of commit, which means if thats successful, then your master is always releasable17:21
khemdistros like archlinux are good examples17:21
khemtime bases releases are things of past CI/CD is more optimal17:22
khemsveinse: as long as you enforce that restriction you are safe17:22
*** belen <belen!~Adium@> has quit IRC17:22
khemkergoth: let me try to add it to basehash whitelist17:23
*** adelcast <adelcast!~adelcast@> has quit IRC17:25
*** MWelchUK <MWelchUK!~martyn@host81-147-3-127.range81-147.btcentralplus.com> has quit IRC17:26
sveinseHas any of you experienced problem massively parallel building uim? meta-openembedded/meta-oe/recipes-support/uim/uim_1.8.6.bb in jethro. I just had a stop on uim do_install: "/srv/builds/core-image/build/tmp/work/x86_64-linux/uim-native/1.8.6-r0/build/uim/.libs/libuim.so: file not recognized: File format not recognized". Re-run bitbake, and everyone is happy. Smells awfully like race, doesn't it?17:26
*** benjamirc <benjamirc!~besquive@> has joined #yocto17:27
*** yann <yann!~yann@85-171-21-92.rev.numericable.fr> has quit IRC17:32
*** nisha <nisha!~nisha@> has quit IRC17:33
khemsveinse: yes its a race17:35
khemsveinse: try PARALLEL_MAKEINST = "" for validating the issue17:36
khemif this works then the package has issues with parallel build17:36
khemespecially with make install target17:37
khemkergoth: whats the incantation to whitelist something from basehash something with BB_BASEHASH17:38
*** boucman_work <boucman_work!~boucman@2a02-8428-034f-f800-9e32-0c7c-b391-6223.rev.sfr.net> has joined #yocto17:38
*** nisha <nisha!~nisha@> has joined #yocto17:43
neverpanicsveinse: yeah, a gig per core is what you should have at minimum. We're running 40 core + 64GiB on our workstations and still regularly hit top RAM17:43
*** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has quit IRC17:44
*** armpit <armpit!~akuster@> has joined #yocto17:45
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-exdhkdbrwzfnrdby> has quit IRC17:49
*** davis <davis!~davis@50-76-27-165-static.hfc.comcastbusiness.net> has joined #yocto17:50
davisi'm having trouble pulling from a private repot with git. I can git clone the url from a bash prompt and I'm authenticated using keys, so I dont need to login or anything.17:51
*** zeddii_home_ <zeddii_home_!~zeddii_ho@CPEe8de27b71faa-CMbcc810032faf.cpe.net.cable.rogers.com> has joined #yocto17:51
davishowever, when I try to do it with bitbake it fails. Here is my setup and error.17:52
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC17:53
*** zeddii_home <zeddii_home!~zeddii_ho@CPEe8de27b71faa-CMbcc810032faf.cpe.net.cable.rogers.com> has quit IRC17:53
khemdavis: you may use ssh protocol17:53
*** zeddii_home_ is now known as zeddii_home17:53
davisi have protocl=ssh in the SRC_URI string17:54
davisfwiw, here is what it looks like17:55
davisSRC_URI = "git://devsupport/tfs/Linux%20PCM%20Project%20\(Reboot%20Edition\)/_git/PCMX;protocol=ssh;branch=master"17:55
khemsomething like SRC_URI = "git://git@github.com/xxxxx/arepo.git;protocol=ssh;branch=master"17:55
khemthose %20 worries me17:55
davisyeah me too17:56
davisalso the escaped ()'s17:56
khemanyway try git://git@github.com17:56
khemand this should help17:56
davisi've done things like this and it worked,17:56
davis#SRC_URI = "git://gitlab.com/netskink/cmake-tutor.git;protocol=https;branch=bitbake"17:56
davisgitlab does not have git protocol, so you need http or ssh17:57
*** radzy <radzy!~radzy@unknown-216-194.windriver.com> has quit IRC17:57
*** sujith_h <sujith_h!~toaster@> has joined #yocto17:57
davisadding a git@ to my url does not work. same error.17:59
*** radzy <radzy!~radzy@unknown-216-194.windriver.com> has joined #yocto18:01
*** willeponken <willeponken!~willeponk@diderot.campus.ltu.se> has quit IRC18:02
sveinsekhem: The way we come around that race is usually just to rerun the build. When it completes, it populates itself into the sstate cache, so usually we don't need that build any more. But it is really annoying when that happens (esp. when working on something else)18:07
*** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has joined #yocto18:10
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-182-183.telecom.by> has joined #yocto18:10
sveinseBTW, rerunning the uim recipe with all cores enables also resolves the race. It just happens from time to time18:11
*** simonl <simonl!uid6729@gateway/web/irccloud.com/x-hjggxemhqsnqyigk> has quit IRC18:16
*** Crofton <Crofton!~Crofton@> has quit IRC18:17
*** RagBal <RagBal!~RagBal@82-168-15-181.ip.open.net> has quit IRC18:23
*** Rootert <Rootert!~Rootert@82-168-15-181.ip.open.net> has quit IRC18:23
davisso here is a simpler situation. I have my own personal ssh repot here18:25
davisi did the SRC_URI like this18:26
davisSRC_URI = "git://git@gitlab.com:netskink/awesome-breakout.git"18:26
kergothif you're copying and pasting that as is, it will not work. the url based syntax uses different separators18:26
kergothyeah, that's wrong18:26
davisthat does not worki either18:26
kergoth: isn't a valid separator between host and path in a url18:26
kergothit's the separator between user and password18:26
khemdavis is it gitlab ?18:26
davisyes its gitlab in that case18:26
khemthen you might need to use :22/x/y/z18:26
khemafter url18:27
kergoth:22? interesting, that should be default for the ssh protocol, no?18:27
sveinseIs there a way to run bb up until runing a recipe (going to test parallel builds in uim)? Is do_fetch a good place to stop and then rerun using a single CPU?18:27
khemor git://git@gitlab.com:22/netskink/awesome-breakout.git;protocol=ssh18:27
khemsveinse: as suggested try to nail it at root18:28
davisSRC_URI = "git://git@gitlab.com:/netskink/awesome-breakout.git;protocol=ssh" that works18:28
*** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has quit IRC18:28
khemworkaround is to disable parallel install18:28
sveinsekhem: Yeah, and with 5300 recipes in build, you'd want to not run those with PARALLEL_MAKEINST="", right?18:29
*** sameo <sameo!~samuel@> has joined #yocto18:29
khemkergoth: looking for your help on disabling something from basehash18:29
khemsveinse: its a per recipe change18:29
khemsveinse: you just want to do it for uim18:29
khemwhich is a reasonable workaround18:29
sveinsekhem: Ah, then. thanks18:29
khemunless you want to help fixing it18:30
davishmm. so the one works with gitlab. I use that as a model for this internal Team Foundation Server and it fails. so frustrating working with a m$ server.18:30
khemdavis: so you missed protocol setting from what was suggested earlier18:30
davisi added ;protocol=ssh at the end18:31
khemdavis: yeah thats right18:31
sveinsekhem, dunno if I'm that experienced enough in yocto and am builds yet. But I am taking a look at it now18:31
davistimestmap 14:28 works18:31
khemsveinse: thats the spirit :)18:31
davissveinse: I am the biggest noob here and sometimes I even get lucky.18:31
kergothkhem: see bitabke.conf for the default bb basehash whitelist. iirc you might need to append to it with a ConfigParsed event handler, in the past it didn't like _append very much18:31
sveinsedavis: Encouraging words... I',m what, three week into yocto. A lot of things to process. (yet I've done embedded build systems for many years, so some is familiar. Its the semantics which is different.)18:33
fischermzeddii: trying to get salt-minion running on an oe target, since I pulled in meta-cloud-services root password is not empty (unknown). Ideas?18:33
*** sno <sno!~sno@> has quit IRC18:33
davisso in gitlab url, it was git@gitlab.com:/my_user_name/project-name.git;protocl=ssh18:33
davisi wonder if that my_user_name is part of the url, or is an identifier for a login? I thought the public key was all that was necessary to authenticate with the repot.18:34
davissveinse: i'm glad I can be encouraging. sometimes its all i feel i can do. lol18:34
sveinsedavis: heh, I can help you with that if you need it to. the blind leading the blind and so on... :P18:36
davisfwiw, in my case ive asked the admin to change the "cell?" name and the repot name so there aren't any spaces or parens involved.18:36
davisalso to check logs to see if its an authentication problem18:37
sveinseHow do you force rebuilding a recipe which is in the sstate cache?18:37
davissveinse: ive been working off and on with yocto a while now. "Embedded Linux Systems with the Yocto Project" is a good book.18:37
davisfor rebuild, try cleanstate18:38
khemfischerm: you might need to add EXTRA_IMAGE_FEATURES ?= "debug-tweaks" to local.conf18:38
davisgive me a second, i find the syntax18:38
khemdavis: if you are in good terms with your IT lords the life can be easier18:39
khemdavis: you can replace git://git@xx.com with git://cell@xx.com18:39
khemfor user to be cell18:39
khemsveinse: bitbake -ccleansstate <recipe>;bitbake recipe18:40
khemrecipe here is recipe name without .bb18:40
*** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has joined #yocto18:40
sveinsedavis, I didn't get the start of you URI problems, but you know you can setup username, certs and stuff in ~/.ssh/config, right?18:41
sveinseWe do that for some private repos which require login. This way we don't have to bother in SRC_URI18:41
davissveinse: no i did not know that.18:41
davisi used this as a guide18:43
sveinsedavis, heres one "live" example: http://paste.ubuntu.com/23062464/18:43
davismy clone still works.18:44
davisfrom cmd line18:44
davisahh you add an id file18:44
davisis the entry for IdentifyFile your private key or public?18:45
sveinseThis is the private, because it needs it to set up the encrypted link18:46
khemRP: kergoth https://bugzilla.yoctoproject.org/show_bug.cgi?id=1015218:46
yoctiBug 10152: normal, Undecided, ---, richard.purdie, NEW , Bitbake always gets taskhash mismatches when using DATE and TIME in python functions18:46
khemits a regression compared to 2.0 and older releases18:47
davissveinse: ok cool, still does not work though. I'll add that to my notes though.18:47
sveinse(I had to introduce the .ssh/keys/ directory, because ssh automatically tries the identities in .ssh/ and some servers kicks you out if you try too many keys)18:47
davisit would prevent me from having to pass an ident as command line when dealing with aws, i bet18:47
sveinseyes. And its convenient to setup username and stuff. "ssh buildserver"  is all I write to log in to it18:48
khemsveinse: davis if you can convince your IT overlords to expose https protocol then you can just tool the use of username/pw in ~/.netrc and it will scale into automation18:48
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto18:49
* sveinse will cry when his IT overlords starts closing down port 2218:49
sveinsewindows admins barely know what it is18:50
fischermkhem: will give a shop18:50
fischermkhem: thx18:50
daviskhem: team foundation server gives an opton to use https18:51
davisi'll look into netrc18:51
*** pohly <pohly!~pohly@dyndsl-031-150-142-006.ewe-ip-backbone.de> has joined #yocto18:54
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto18:55
khemdavis: you need something like18:56
khemmachine <machine-name> login <username> password <password>18:57
khementry in ~/.netrc18:57
*** RagBal <RagBal!~RagBal@82-168-15-181.ip.open.net> has joined #yocto18:58
khemand then you can use "git://machine-name/dir/to/repo;protocol=https"18:58
*** Rootert <Rootert!~Rootert@82-168-15-181.ip.open.net> has joined #yocto18:58
davisheh, i was just doing my netrc18:58
sveinseHmm. Been running -ccleansstate and rebuilding uim on with all available CPU without failing any single time. Perhaps a missing DEPENDS, which now is present in sysroot?18:58
davisyes, it works with http on bash level18:58
sveinse5 times I've runned it18:58
khemsveinse: thats possible18:59
sveinsewipe-sysroot and then try rebuilding uim?18:59
khemsveinse: rm -rf tmp/;bitbake uim18:59
khemwill expose DEPENDS issues18:59
sveinseok, will try18:59
khemwipe the whole tmp18:59
khemit will reuse everything from sstate on rebuild so it will be matter of few minutes to rebuild19:00
daviswhoa! that is working19:00
khemand you will also get to experience the power OE at same time :)19:00
davisit went further but failed. perhaps, PV="1.0.0+git${SRCPV}19:00
khemdavis: ofcourse it works, I use it every day19:00
davis" is a problem.19:01
khemwhats the error ?19:01
sveinseWhile I'm waiting: Our server is running Ubuntu server, so lvm is installed by default. A bad idea for yocto?19:01
davislet me gist it19:01
khemsveinse: lvm is ok. nfs has gripes19:02
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:d937:3976:9319:8236> has quit IRC19:02
sveinsestill waiting for my rm -rf tmp...19:03
davisthe top one was where i tried http19:04
davisi should have renamed it19:04
davisits renamed now to http_attempt19:04
khemdavis: you have a multiline string which is commented out, usually that has some issues with bitbake, add a new empty commented line at the end for it to notice end of commented mutliline19:06
khemline 1019:06
khemadd a # there19:07
khemand SRC_URI = "http://http://devsupport:8080 seems not ok19:07
khemSRC_URI = "http://devsupport:808019:07
khemmight be ok19:08
sveinseNope, 3 times of rm -rf tmp and rebuilding uim. No failures19:09
khemsveinse: so it might be rare then19:14
khemmay be change parallelism19:14
*** Tenhi_ <Tenhi_!~tenhi@static.> has joined #yocto19:14
khemkergoth: I added DATE and TIME to BB_HASHBASE_WHITELIST in bitbake.conf, did not help either19:15
sveinseI need more time on this, but let me observe failing a few more times, and then I can test with PARALLEL_MAKEINST="" to see if it goes away19:15
sveinseCan I configure (in local.conf) that a recipe shall never be read from sstate cache?19:16
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has joined #yocto19:18
sveinseFor CI build server, do you change the bitbake UI, or just leave it at knotty?19:19
*** Tenhi_ <Tenhi_!~tenhi@static.> has quit IRC19:19
*** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has quit IRC19:19
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto19:21
khemsveinse: yes but thats discouraged but you can add something like do_compile[nostamp] = "1" to the recipe19:27
khemas a gross hack19:27
fischermkhem: thx19:31
RPkhem: its not a regression, we just added better debugging of when there are problems19:38
*** igor3 <igor3!~igor@> has quit IRC19:56
*** yann <yann!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto19:58
*** obsrwr_ <obsrwr_!~otp-amois@> has quit IRC20:09
*** igor3 <igor3!~igor@> has joined #yocto20:10
*** rcw <rcw!~rwoolley@> has quit IRC20:10
*** berton <berton!~fabio@> has quit IRC20:28
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC20:35
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto20:36
*** pohly <pohly!~pohly@dyndsl-031-150-142-006.ewe-ip-backbone.de> has quit IRC20:37
khemRP: OK, so its catching more errors I guess, which is fine, however, I have no way to shut this20:37
khemRP: none of vardepexclude work20:37
*** Crofton <Crofton!~Crofton@> has joined #yocto20:38
khemRP: from an ignorant user's pov its a regression20:39
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC20:39
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-jexcjzmxzffyflwf> has joined #yocto20:40
*** jbrianceau_away is now known as jbrianceau_home20:40
*** MWelchUK <MWelchUK!~martyn@host81-147-3-127.range81-147.btcentralplus.com> has joined #yocto20:43
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC20:45
*** Crofton <Crofton!~Crofton@> has quit IRC20:46
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto20:47
*** caiortp <caiortp!~inatel@> has quit IRC21:02
RPkhem: vardepexclude should work21:03
khemRP: I tried to add tweak_image_name[vardepsexclude] += "DATE TIME"21:04
khemhas no effect21:04
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC21:05
*** arkver <arkver!~arkver@host81-135-58-159.range81-135.btcentralplus.com> has quit IRC21:20
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC21:22
khemRP: there seems to no way to disable this error thats my gripe21:24
*** josep <josep!~josep@c-cbe670d5.010-118-73746f7.cust.bredbandsbolaget.se> has joined #yocto21:32
*** sveinse <sveinse!~chatzilla@156.92-221-160.customer.lyse.net> has quit IRC21:33
*** hbruce <hbruce!~hbruce@> has joined #yocto21:33
*** hbruce <hbruce!~hbruce@> has left #yocto21:34
*** caiortp <caiortp!~caiortp@> has joined #yocto21:37
*** caiortp <caiortp!~caiortp@> has quit IRC21:46
*** jbrianceau_home is now known as jbrianceau_away21:55
*** caiortp <caiortp!~caiortp@> has joined #yocto22:00
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has quit IRC22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC22:01
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto22:01
*** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has quit IRC22:05
RPkhem: well, the above should work, the question is why it doesn't22:11
*** stephano <stephano!stephano@nat/intel/x-auffyyhiabmxszhk> has quit IRC22:12
*** aehs29 <aehs29!aehernan@nat/intel/x-tythmdyrzoxsafcu> has left #yocto22:16
*** boucman_work <boucman_work!~boucman@2a02-8428-034f-f800-9e32-0c7c-b391-6223.rev.sfr.net> has quit IRC22:16
*** josep <josep!~josep@c-cbe670d5.010-118-73746f7.cust.bredbandsbolaget.se> has quit IRC22:19
*** agust <agust!~agust@p4FCB4322.dip0.t-ipconnect.de> has quit IRC22:23
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC22:43
-YoctoAutoBuilder- build #216 of nightly-musl is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-musl/builds/21622:47
*** aehs29 <aehs29!aehernan@nat/intel/x-nakmqqozsshyefdu> has joined #yocto22:48
*** jynik <jynik!~bragg@cpe-67-253-219-41.rochester.res.rr.com> has quit IRC22:58
*** jynik <jynik!~bragg@cpe-67-253-219-41.rochester.res.rr.com> has joined #yocto23:00
*** lamego <lamego!~jose@> has quit IRC23:01
*** benjamirc <benjamirc!~besquive@> has quit IRC23:02
*** igor3 <igor3!~igor@> has quit IRC23:03
*** istarilucky <istarilucky!~rlucca@> has quit IRC23:06
*** aehs29 <aehs29!aehernan@nat/intel/x-nakmqqozsshyefdu> has left #yocto23:10
*** mborzecki <mborzecki!~Maciej_Bo@staticline-31-182-60-238.toya.net.pl> has quit IRC23:17
-YoctoAutoBuilder- build #620 of nightly-world-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world-lsb/builds/62023:25
*** jpeters <jpeters!c66941c5@gateway/web/freenode/ip.> has joined #yocto23:30
*** mborzecki <mborzecki!~Maciej_Bo@staticline-31-182-60-238.toya.net.pl> has joined #yocto23:31
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-182-183.telecom.by> has quit IRC23:31
jpetersI am having trouble adding a recipe to Yocto.  I have added a recipe to install the azure libraries.  It creates 3 shared libraries.  In the azure..rpm I see the libumqtt.so.1.1 libumqtt.so.1 libamqp.so.1.1 libamqp.so.1 libumock.so.1.1 libumock.so.1 files.  In the the azure-dev...rpm file I set libmqtt.so libamqp.so and libumock.so along with header files etc.23:34
jpetersA second recipe to test the installation links correctly against the libraries but when do_rootfs runs I get the message "Computing transaction...error: Can't install azure-test-1.0-r0@armv5e: no package provides libumqtt.so".23:36
jpetersAny idea what I could be doing wrong?23:36
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-jexcjzmxzffyflwf> has quit IRC23:59

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!