Thursday, 2015-04-09

bk_lsrkergoth: thanks, i'll check those out00:00
-YoctoAutoBuilder- build #252 of nightly-qa-systemd is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/25200:01
*** sjolley <sjolley!sjolley@nat/intel/x-rqvwizakjafbeytj> has quit IRC00:02
-YoctoAutoBuilder- build #254 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/25400:05
bk_lsrkergoth: got it working. what i needed & couldn't find was the destsuffix param. thanks!00:10
kergothah, np00:10
-YoctoAutoBuilder- build #254 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/25400:23
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has quit IRC00:24
-YoctoAutoBuilder- build #250 of nightly-fsl-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/25000:25
*** tlwoerner_ <tlwoerner_!~tlwoerner@unaffiliated/tlwoerner> has joined #yocto00:29
*** bzb <bzb!~bzb@198-48-196-219.cpe.pppoe.ca> has joined #yocto00:31
-YoctoAutoBuilder- build #257 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/25700:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:50
-YoctoAutoBuilder- build #256 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/25600:51
*** bzb <bzb!~bzb@198-48-196-219.cpe.pppoe.ca> has quit IRC00:53
-YoctoAutoBuilder- build #246 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/24601:07
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto01:23
-YoctoAutoBuilder- build #253 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/25301:33
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC01:36
*** khem` is now known as khem[away]01:40
*** khem[away] is now known as khem`01:41
*** khem` is now known as khem[away]01:41
*** khem[away] is now known as khem`01:42
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto01:50
-YoctoAutoBuilder- build #255 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/25501:52
*** hsychla <hsychla!~hsychla@2001:6f8:12d9:13:6deb:b865:8f43:874e> has quit IRC02:04
*** sarahsharp <sarahsharp!~sarah@134.134.139.74> has quit IRC02:05
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has joined #yocto02:12
*** redengin <redengin!~redengin@c-73-193-21-136.hsd1.wa.comcast.net> has joined #yocto02:13
-YoctoAutoBuilder- build #255 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/25502:15
*** hsychla <hsychla!~hsychla@2001:6f8:12d9:13:e12d:fc12:5d78:a7e7> has joined #yocto02:17
*** Guest66260 <Guest66260!~gary@pool-98-114-34-165.phlapa.fios.verizon.net> has joined #yocto02:28
Guest66260Would someone have information on including a Windows version of QEMU in the nativesdk built including the mingw compiler?02:31
redenginGuest66260, what do you mean?  are you trying to do poky builds under mingw/cygwin?02:36
khem`kergoth: yt?02:37
Guest66260I have a requirement to use windows for building applications on top of the root file system.02:38
Guest66260I want to build the SDK for windows including a version of QEMU that can run in windows using the poky image.02:39
Guest66260the meta-mingw builds the GCC cross compiler for windows but I haven't found a way to get QEMU yet.02:40
kergothjust use the standard yocto sdk mechanisms with SDKMACHINE set to one of the sdkmachines provided by meta-mingw02:40
kergothe.g. SDKMACHINE="i686-mingw32" bitbake -c populate_sdk core-image-base02:40
kergoththen if that doesn't already include qemu, which i think it does, at least for the qemu machines, you can always add nativesdk-qemu to TOOLCHAIN_HOST_TASK02:41
kergothkhem`: somewhat, whats up02:41
Guest66260Hmmm. This is what I did and I didn't find a Windows based QEMU in the SDK output. Sorry I'm rather new to Yocto.02:42
khem`kergoth: I am seeing one issue where I change S and sstate for do_install gets invalidated02:45
khem`since in do_install I use ${S}02:45
khem`now this change in S is due to externalsrc02:45
khem`are there any good ways to avoid this invalidation ?02:46
kergothnot terribly surprising, not many of our path variables are excluded. just mos tof hte time it doesnt' matter, since it's including their unexpanded values, and those don't include full paths02:46
kergothe.g. ${WORKDIR}/foo02:46
kergothdo_install[vardepsexclude] += "S" is probably your best bet02:46
Guest66260My MACHINE is qemuarm and SDKMACHINE is X86_64-mingw32. Output is only the mingw toolchain, no QEMU. I have not done the TOOLCHAIN_HOST_TASK02:47
* kergoth rather liked his checksumming implementation better than the current one in some ways.. it checksummed expanded variables, but kept blacklisted variables as unexpanded02:47
kergothGuest66260: output of *what*?02:47
kergothyou haven't said what your'e building02:47
Guest66260Thanks for the suggestion. I will try it.02:47
kergoththe yocto sdk includes quite a lot more than just a toolchain, so it sounds like you're not building with -c populate_sdk02:48
redenginGuest66260, wouldn't it just be easier to run a virtual machine of the poky SDK image?  I'm not sure I'd trust mingw02:49
Guest66260I thought it looked rather sparse. But I also thought I used -c. Guess I should re-run to make sure.02:49
*** khem` is now known as khem[away]02:50
*** khem[away] is now known as khem`02:50
Guest66260It pains me to be in Windows but it's not really my call. Just trying to make the best of it.02:50
* kergoth shrugs, hasn't personally targeted mingw, but it should work just like other sdkmachines02:50
redenginGuest66260, are you forced to do all the native compilation using mingw or can you simply run a linux virtual machine under windows?02:51
kergothA VM does sound like it'd be a lot more pleasant, but not always an option02:51
Guest66260Our formal build team can't use a Linux VM ... yet.02:54
Guest66260I can use a VM but at the end of the day Windows still needs to get involved. We are pushing but it goes slow.02:55
* kergoth nods02:57
Guest66260So I was just reviewing what I previously did. I actually ran bitbake -c populate_sdk core-image-minimal02:57
Guest66260But I had thought that was referring to a minimal root file system, not SDK.02:57
Guest66260I'm re-running now with core-image-base02:58
redenginGuest66260, what type of image are you trying to build?03:03
Guest66260redengin, the target is a small arm device that can run a minimal busybox root file system only. We launch an app and thats it.03:11
Guest66260So QEMU is nice to test out that small system on the desktop.03:11
redenginah, so you don't want an arm toolchain in the device image03:12
redenginwhich arm boot loader are you using?03:13
kergothdoes qemu even run on windows?03:14
Guest66260we have a simple hand written boot loader and also looking to see if u-boot will fit.03:14
Guest66260I've built qemu for windows by myself a couple of times. A little annoying. They also have full pre-built packages for download.03:15
kergothah, cool03:16
Guest66260It was more the idea of a one stop full SDK rather than an absolute must that Yocto build the windows QEMU.03:16
redenginso what does your bootloader expect to find in order to boot?03:17
Guest66260Actually I had thought if it wasn't already done I might try it as a learning exercise since I already have built it by hand.03:17
Guest66260We partition the flash into a number of sections. kernel, device tree, squashfs RFS and app partition.03:19
Guest66260so the boot loader copies kernel and RFS to RAM and jumps.03:19
Guest66260we have it working on an older device but it's pretty limited. u-boot would offer some nice debug features.03:20
redenginyour bitbake output doens't include the kernel and a rfs?03:20
Guest66260it puts the zImage and RFS under deploy/images03:22
Guest66260we also want the SDK which is under deploy/SDK03:22
Guest66260the image actually does not contain a compiler as the device is not big enough.03:23
Guest66260the goal is only for the app partition to be built in Windows as the Yocto image is built obviously in Linux.03:24
Guest66260But the build team wants the app build in Windows. Such a pain.03:24
Guest66260And it would help to provide simple test qemu support in windows as well.03:25
nrossiGuest66260: I've been able to build QEMU with the meta-mingw layer before, there were some minor issues.03:31
Guest66260nrossi, did you have to add extra configuration options to have the meta-mingw layer build qemu?03:34
nrossiit seems i had some patches for ncurses as well as hacks for dtc (although if you dont need fdt support in qemu you can just disable that)03:34
Guest66260I just got done with a re-run of bitbake -c populate_sdk core-image-base and still no qemu in the SDK.03:35
nrossitry building "nativesdk-qemu" and see how far you get first.03:35
Guest66260ya, when I actually built qemu on a Windows mingw environment, getting device tree support was a bear.03:36
Guest66260I had to hack that build but it worked.03:37
Guest66260I was hoping Windows qemu build done in Linux would actually not require that hack.03:37
nrossiand to get the populate_sdk to include qemu i think you need to add it to "TOOLCHAIN_HOST_TASK"03:37
nrossiif i remember correctly the hack was due to posix compliance of dtc03:38
nrossiand it was in the actual compiler and no in libfdt03:38
Guest66260hmm, could be on the right path. It was trying to build a mingw qemu but died on an Xorg task. Bummer, I want to run nographics.03:42
redenginah I see you're trying to do a qemu build using the bitbake native toolchain03:42
nrossiOh one other thing, you cant build qemu for mingw64, you have to target 32-bit. QEMU has a hard limitation on that one03:43
Guest66260I can live with 32-bit, I did specify 64-bit but suspected it would cause trouble.03:44
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has quit IRC03:47
*** sjolley <sjolley!~sjolley@134.134.137.71> has joined #yocto03:59
*** Guest66260 <Guest66260!~gary@pool-98-114-34-165.phlapa.fios.verizon.net> has quit IRC04:31
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto04:54
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC05:02
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto05:11
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto05:11
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has joined #yocto05:21
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC05:22
*** ScarEye <ScarEye!~scareye@static-64-61-84-232.isp.broadviewnet.net> has quit IRC05:24
*** ScarEye <ScarEye!~scareye@static-64-61-84-232.isp.broadviewnet.net> has joined #yocto05:25
*** Crofton <Crofton!~balister@pool-108-44-109-154.ronkva.east.verizon.net> has quit IRC05:32
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has quit IRC05:33
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has joined #yocto05:34
*** Crofton|work <Crofton|work!~balister@pool-108-44-109-154.ronkva.east.verizon.net> has quit IRC05:35
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has joined #yocto05:41
*** agust <agust!~agust@pD9E2FD0A.dip0.t-ipconnect.de> has joined #yocto05:44
*** Crofton|work <Crofton|work!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has joined #yocto05:48
*** Crofton <Crofton!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has joined #yocto05:48
*** Crofton <Crofton!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has quit IRC05:59
*** Crofton|work <Crofton|work!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has quit IRC05:59
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto06:06
*** Crofton|work <Crofton|work!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has joined #yocto06:12
*** Crofton <Crofton!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has joined #yocto06:12
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto06:18
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto06:19
*** wadim_ <wadim_!~egorov@mail.x-arc.co.uk> has joined #yocto06:23
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC06:38
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto06:38
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC06:38
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto06:40
*** pohly <pohly!~pohly@p5DE8CDA6.dip0.t-ipconnect.de> has joined #yocto06:42
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto06:50
*** RP <RP!~richard@5751f4a1.skybroadband.com> has quit IRC06:58
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC06:58
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC06:59
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto06:59
*** smustafa <smustafa!~mustafa@110.93.212.98> has joined #yocto07:04
*** RP <RP!~richard@5751f4a1.skybroadband.com> has joined #yocto07:07
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC07:19
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:30
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto07:30
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto07:31
*** _valle_ <_valle_!~valle@195.198.200.72> has quit IRC07:41
*** sameo <sameo!~samuel@192.55.55.41> has joined #yocto07:41
*** _valle_ <_valle_!~valle@195-198-200-72.customer.telia.com> has joined #yocto07:42
*** Crofton <Crofton!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has quit IRC07:45
*** Crofton|work <Crofton|work!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has quit IRC07:45
*** belen <belen!~Adium@192.198.151.44> has joined #yocto07:57
*** Crofton|work <Crofton|work!~balister@pool-71-171-11-220.ronkva.east.verizon.net> has joined #yocto07:58
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC08:00
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has joined #yocto08:01
*** sameo <sameo!~samuel@192.55.55.41> has quit IRC08:07
*** belen <belen!~Adium@192.198.151.44> has quit IRC08:07
*** sameo <sameo!~samuel@192.55.55.41> has joined #yocto08:07
*** volker_123456 <volker_123456!~quassel@host-80-81-19-29.customer.m-online.net> has quit IRC08:07
*** tmpsantos <tmpsantos!~tmpsantos@a88-115-217-160.elisa-laajakaista.fi> has joined #yocto08:07
*** volker_123456 <volker_123456!~quassel@host-188-174-253-51.customer.m-online.net> has joined #yocto08:08
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:09
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto08:14
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC08:14
*** jku <jku!jku@nat/intel/x-axevksualktrxcin> has joined #yocto08:17
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has joined #yocto08:18
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC08:24
*** rahc <rahc!rah@pasanda.collabora.co.uk> has joined #yocto08:24
bluelightningmorning all08:27
rahcmorning08:28
rahcI'm a bit confused by the runqemu and runqemu-internal scripts08:28
rahchttp://codepad.org/wlSiwUQP08:28
nrossirahc: yer they are not much fun :P08:29
rahcrunqemu-internal has support for a "qemuarmv7" MACHINE but runqemu does not08:29
rahcnrossi: would you accept patches to make runqemu support "qemuarmv7"?08:29
rahcor even make it a bit more nuanced, like being able to specify appropriate options for "-cpu", like cortex-a8 or cortex-a908:30
rahcI want to emulate a cortex-a908:30
nrossiim not the maintainer, i've just had many a war with those runqemu scripts :P08:31
rahcmaintainers: would you accept patches to make runqemu support "qemuarmv7"? :-)08:31
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto08:31
nrossiyou can always submit it, i dont see any particular reason for it not being accepted08:31
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC08:35
*** ddom <ddom!~ddom@p4FFDA393.dip0.t-ipconnect.de> has joined #yocto08:36
bluelightningI think we'd probably accept it08:38
bluelightningwe're probably overdue to implement a proper extension mechanism for runqemu though08:38
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has joined #yocto08:39
bluelightninghaving said that, qemuarmv7 would probably be most appropriately supported within OE-Core even if that were in place08:39
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has quit IRC08:43
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto08:47
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has joined #yocto08:48
*** pev <pev!~pev@2.31.101.83> has joined #yocto08:56
*** belen <belen!Adium@nat/intel/x-dqxiudqcwbiihhkl> has joined #yocto09:01
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC09:01
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has joined #yocto09:14
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has quit IRC09:17
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto09:18
*** jmleo <jmleo!~jmleo@LDijon-156-64-30-180.w80-15.abo.wanadoo.fr> has joined #yocto09:22
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC09:28
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto09:53
ericbuttersping kergoth09:55
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has quit IRC10:04
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has joined #yocto10:06
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has quit IRC10:19
*** Crofton <Crofton!~balister@pool-71-171-11-220.ronkva.east.verizon.net> has joined #yocto10:23
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has joined #yocto10:25
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:29
lpapphi, can I get some help with "oe-init-build-env-memres"? I do not know the use case for it and it does not seem to be documented either.10:30
lpapphttp://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#structure-memres-core-script -> it is sort of explaining what it does, but it does not explain why.10:30
*** belen1 <belen1!Adium@nat/intel/x-vwkboioeafwkhcwd> has joined #yocto10:35
*** belen <belen!Adium@nat/intel/x-dqxiudqcwbiihhkl> has quit IRC10:36
bluelightninglpapp: you save a bit of time on repeated bitbake invocations because it's in memory10:46
bluelightninglpapp: there are issues with detecting metadata changes while running it though (until recent fixes in master, which *may* be backported to dizzy)10:47
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC10:48
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto10:53
*** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC10:59
*** ccube <ccube!ccube@nx.mindrunner.de> has joined #yocto11:00
*** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC11:01
*** ccube <ccube!ccube@nx.mindrunner.de> has joined #yocto11:03
lpappbluelightning: ok, I am updating from dylan to daisy11:05
lpappand this memres turned up, but then we possibly do not need it as memory is not a big deal on powerful build machines, is it11:05
bluelightningwell, it's not about that, it's about whether you are bothered by the time bitbake normally takes to start up11:06
bluelightningpersonally I put up with it11:06
*** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC11:07
bluelightningbut to be honest I would advise against using memres until 1.8 (fido)11:07
bluelightning(or when the inotify patches get merged to dizzy, if that happens)11:07
*** ccube <ccube!ccube@nx.mindrunner.de> has joined #yocto11:07
lpappok, thanks.11:10
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has joined #yocto11:11
cart_manHey whats the recepy name for Yocto-KERNEL-HEADERS?11:11
cart_manor Core-Devel-Tools11:11
cart_man?11:11
cart_manalso...is there a Yocto apt-get recepy I can add?11:12
*** jku <jku!jku@nat/intel/x-axevksualktrxcin> has quit IRC11:18
*** jku <jku!jku@nat/intel/x-dkfihqgijuevowae> has joined #yocto11:20
*** mag0 <mag0!~mago@88.131.56.168> has quit IRC11:26
*** radhus <radhus!~radhus@sevh.radhuset.org> has quit IRC11:35
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC11:37
-YoctoAutoBuilder- build #250 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/25011:37
*** radhus <radhus!~radhus@sevh.radhuset.org> has joined #yocto11:38
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto11:40
*** wCPO <wCPO!~kristian@188.228.31.139> has joined #yocto11:40
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has joined #yocto11:40
jaeckelI know I can find out the dependencies of a package with the bitbake -g option, can I also somehow find out how this dependency is introduced? I have several recipes that are always rebuilt when I change something in one specific recipe, but I don't know where this dependency comes from11:41
*** jchonig <jchonig!~quassel@firewall.honig.net> has quit IRC11:43
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC11:50
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has joined #yocto11:51
*** jchonig <jchonig!~quassel@firewall.honig.net> has joined #yocto11:52
lpappare you looking for a dependency graph?11:54
jaeckelno, I am looking for the step after having the dependency graph, to find where this dependency originates11:55
lpappok, so that you do not have to anything more than just reading a chain. I doubt that as it is quite specific need, but cannot you cook a simple script?11:56
-YoctoAutoBuilder- build #253 of nightly-qa-logrotate is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/25312:00
*** zaman1 <zaman1!~zaman@192.198.151.44> has joined #yocto12:03
*** zaman <zaman!~zaman@192.198.151.44> has quit IRC12:06
jaeckelsorry for beeing unclear, I know that a bunch of recipes depend somehow on recipe2, but I have no clue where this is introduced in my layers12:07
jaeckelnow I'd like to find out what creates that dependency12:07
*** mago_ <mago_!~mago@88.131.56.168> has joined #yocto12:10
bluelightningjaeckel: I usually search the graph for '-> the-dependency-name'12:21
jaeckelyeah I searched where the discovery came from12:21
jaeckelnow I saw that this is caused by VIRTUAL-RUNTIME_initscripts = "recipe2"12:22
jaeckeland this variable is automatically used in DEPENDS12:22
cart_manHey guys how can I download the Yocto kernel headers?12:24
jaeckelis there some documentation where I can see what VIRTUAL-RUNTIME_initscripts is intended to be used for?12:26
bluelightningcart_man: can you explain the context of the question? what are you trying to do?12:26
bluelightningjaeckel: I don't believe we have that documented, but basically it's a placeholder for what the initscripts package normally contains - if you don't need it, just set it to nothing12:27
cart_manbluelightning,Im trying to write PCI drivers12:28
jaeckelso if I make sure that this recipe is included somewhere else in the build process there is no need to set it there?12:28
cart_manand I need the Kernel headers12:28
cart_manusually in Ubuntu it will be apt-get install kernel-headers12:28
cart_manbut I cant get apt-get in Yocto so I have no idea how getting then is possible12:29
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto12:29
bluelightningcart_man: kernel-dev would be the package name but to be honest I wouldn't have thought doing this kind of development on the target would be the way to do it...12:30
bluelightningcart_man: it's also going to depend on what machine you are targeting12:31
*** frsc <frsc!~frsc@x5d84120c.dyn.telefonica.de> has joined #yocto12:31
cart_manWell the chipset determines the sort of kernel right?12:32
cart_manGhez I have idea where to even begin searching for it12:33
bluelightningcart_man: my advice would be to find the appropriate BSP for the machine you are targeting (BSP = Board Support Package, i.e. how our build system knows how to support a particular piece of hardware)12:35
bluelightningthen, build the kernel and you will get the kernel headers as part of that process12:35
bluelightningwe have a kernel development manual: http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html12:36
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has joined #yocto12:42
-YoctoAutoBuilder- build #255 of nightly-non-gpl3 is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/25512:45
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has left #yocto12:49
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has joined #yocto12:49
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has left #yocto12:49
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has quit IRC12:53
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has quit IRC12:59
*** Levi <Levi!~vlevidas@134.134.137.71> has joined #yocto13:03
-YoctoAutoBuilder- build #254 of nightly-qa-pam is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/25413:04
-YoctoAutoBuilder- build #254 of nightly-qa-skeleton is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/builds/25413:04
*** tlwoerner_ <tlwoerner_!~tlwoerner@unaffiliated/tlwoerner> has quit IRC13:05
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto13:17
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has joined #yocto13:22
*** tsramos <tsramos!~tsramos@134.134.139.76> has joined #yocto13:24
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC13:25
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto13:25
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC13:28
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto13:28
*** manuel__ <manuel__!~manuel@209.6.175.242> has joined #yocto13:32
*** anselmolsm <anselmolsm!~anselmo@192.55.54.40> has joined #yocto13:36
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC13:38
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto13:38
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has quit IRC13:42
*** belen2 <belen2!Adium@nat/intel/x-erpnaqyyipmctuoq> has joined #yocto13:45
*** belen1 <belen1!Adium@nat/intel/x-vwkboioeafwkhcwd> has quit IRC13:46
-YoctoAutoBuilder- build #253 of nightly-x32 is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/25313:47
-YoctoAutoBuilder- build #250 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/25013:48
*** wadim_ <wadim_!~egorov@mail.x-arc.co.uk> has quit IRC13:51
-YoctoAutoBuilder- build #258 of nightly-x86-64-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/25813:57
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC14:02
*** frsc <frsc!~frsc@x5d84120c.dyn.telefonica.de> has quit IRC14:03
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC14:05
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC14:07
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has quit IRC14:08
lpappbluelightning: are you still about?14:13
lpappbluelightning: I am getting this after copying the daisy directories over, TEMPLATECONF=meta-foo/conf . oe-init-build-env14:14
lpapp/home/lpapp/Projects/foo/Yocto/poky-dylan-9.0.1/scripts/oe-setup-builddir: 44: .: Can't open /home/lpapp/Projects/foo/Yocto/poky-dylan-9.0.1/.templateconf14:14
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has quit IRC14:15
*** belen1 <belen1!Adium@nat/intel/x-lxxgckntypkzzqvj> has joined #yocto14:16
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has joined #yocto14:17
bluelightninglpapp: not sure, it's not a known bug AFAIK14:18
*** belen2 <belen2!Adium@nat/intel/x-erpnaqyyipmctuoq> has quit IRC14:18
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto14:18
*** belen1 <belen1!Adium@nat/intel/x-lxxgckntypkzzqvj> has quit IRC14:20
*** belen1 <belen1!Adium@nat/intel/x-lmvbsedfwxnvyrfi> has joined #yocto14:20
*** jku <jku!jku@nat/intel/x-dkfihqgijuevowae> has quit IRC14:22
*** belen1 <belen1!Adium@nat/intel/x-lmvbsedfwxnvyrfi> has quit IRC14:22
*** belen1 <belen1!Adium@nat/intel/x-qzvfbhpjtaresijp> has joined #yocto14:24
*** jku <jku!~jku@85-76-53-19-nat.elisa-mobile.fi> has joined #yocto14:24
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto14:26
lpappbluelightning: sure, it is pebkac, thanks.14:27
lpappI did not copy that file over, I thought oe-... bitbake, meta and scripts would be enough14:27
lpappapparently, I need that "hidden" file, too.14:27
lpappis there any other files that I forgot to copy over?14:30
bluelightningnot that I am aware of14:30
lpappbluelightning: thanks, this is odd for bitbake myimage, https://paste.kde.org/pmw3pqiyf14:32
bluelightningproxy settings set correctly?14:34
lpappour network is working with dylan.14:34
bluelightningall that check does is try to fetch some dummy data from yoctoproject.org14:35
bluelightningusing bitbake's fetcher14:35
*** dmoseley1 <dmoseley1!~dmoseley@cpe-174-96-222-251.carolina.res.rr.com> has quit IRC14:36
lpappstrange.14:37
lpappbecause there are no problems with dylan, only now with daisy.14:37
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto14:37
lpappdoes this operation depend on some config?14:40
*** hugovs <hugovs!~hugo@177.159.144.73> has joined #yocto14:41
-YoctoAutoBuilder- build #255 of nightly-x86-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/25514:46
bluelightninglpapp: nothing that the fetcher doesn't use - the implementation is check_connectivity() in meta/classes/sanity.bbclass14:52
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC15:01
lpapphas that changed between dylan and daisy?15:01
*** jku <jku!~jku@85-76-53-19-nat.elisa-mobile.fi> has quit IRC15:01
*** adelcast <adelcast!~adelcast@130.164.62.82> has left #yocto15:01
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC15:01
bluelightninggit blame says that function itself hasn't changed materially since 201115:02
bluelightningit's a bit annoying that it doesn't actually report the failure15:04
*** neur0Fuzzy <neur0Fuzzy!~neur0Fuzz@p239.net182021249.tokai.or.jp> has quit IRC15:04
lpappyaeh :/15:04
lpappperhaps you can patch that?15:04
*** sameo <sameo!~samuel@192.55.55.41> has quit IRC15:05
*** Levi <Levi!~vlevidas@134.134.137.71> has quit IRC15:05
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto15:05
-YoctoAutoBuilder- build #255 of nightly-multilib is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2 BuildImages_3 Running Sanity Tests_3 BuildImages_4] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/25515:06
lpappbluelightning: I guess I will need to put debug statements into that file then or shall I try something simpler?15:07
bluelightninglpapp: that's really the only way to determine what's going wrong at this point15:08
*** sjolley <sjolley!~sjolley@134.134.137.71> has quit IRC15:12
*** sarahsharp <sarahsharp!~sarah@134.134.137.75> has joined #yocto15:22
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:23
lpappbluelightning: shall I raise a report for making the error reporting better for this?15:25
*** sarahsharp <sarahsharp!~sarah@134.134.137.75> has quit IRC15:27
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC15:28
lpappbluelightning: we have some internal mirrors for downloading the software should that be an isuse.15:32
lpappissue*15:32
*** aehs29 <aehs29!~aehernan@134.134.139.76> has joined #yocto15:33
bluelightninglpapp: yes please file a bug for the error message15:34
lpappbluelightning: ok, but have you checked it in the latest version? It is from daisy.15:35
bluelightninglpapp: I doubt I would have experienced the same issue here, so it's not something I can test - I suspect it's specific to your setup15:35
lpappseems the latest is verbatim15:36
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC15:37
*** sjolley <sjolley!sjolley@nat/intel/x-blikxjjqlhzasifn> has joined #yocto15:40
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has quit IRC15:41
*** wCPO <wCPO!~kristian@188.228.31.139> has joined #yocto15:41
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has joined #yocto15:41
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC15:43
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto15:45
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto15:52
lpappbluelightning: we have our own SOURCE_MIRROR_URL = "http://foo/yocto/downloads"15:52
lpappcould that be  the issue?15:52
*** sarahsharp <sarahsharp!sarah@nat/intel/x-oeepswbjxrmflxza> has joined #yocto15:54
lpappit is in our distro/foo.conf15:54
*** manuel__ <manuel__!~manuel@209.6.175.242> has quit IRC15:56
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC15:56
lpappbluelightning: I also have CONNECTIVITY_CHECK_URIS15:58
bluelightninglpapp: wouldn't have thought so, SOURCE_MIRROR_URL sets (PRE)MIRRORS, but that check function unsets PREMIRRORS and MIRRORS in order to really test whether network connectivity is working15:58
lpapphttps://paste.kde.org/pjspf8spa15:59
*** ebolton <ebolton!~ebolton@208.93.135.69> has joined #yocto15:59
bluelightninglpapp: right, that's the default value...16:00
*** sarahsharp <sarahsharp!sarah@nat/intel/x-oeepswbjxrmflxza> has quit IRC16:00
lpappyes16:00
*** belen1 <belen1!Adium@nat/intel/x-qzvfbhpjtaresijp> has quit IRC16:02
*** belen1 <belen1!Adium@nat/intel/x-qnffndtmgebuskkc> has joined #yocto16:02
*** blitz00 <blitz00!stefans@nat/intel/x-ixstbdgmnxoqvoki> has joined #yocto16:03
eboltonhey all, I'm having issues with a Python error in the SDK...I've installed nativesdk-python-modules, but I still get this error everytime I source the env script and try to run a python script (or run a program that doesn't exist, for some reason)16:03
eboltonFile "/opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/sysconfig.py", line 10, in <module>16:03
ebolton    'stdlib': '{base}/'+sys.lib+'/python{py_version_short}',16:03
eboltonAttributeError: 'module' object has no attribute 'lib'16:03
*** blitz00 <blitz00!stefans@nat/intel/x-ixstbdgmnxoqvoki> has quit IRC16:03
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto16:03
eboltonthe strange thing is, the line that generates the error calls "sys.lib", which was added in multilib.patch...and the patch is being applied correctly....is very strange16:04
bluelightningebolton: I meant to reply to your email - I honestly don't know what could be going wrong there :(16:05
bluelightningebolton: is nativesdk-python-modules *definitely* part of the SDK now? your email was suggesting that that wasn't working16:08
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has quit IRC16:08
eboltonbluelightning: yea, I realized after I wrote that email that nativesdk-python-modules was actually an empty package that the python recipe generates as a "catch all" for the rest of the module packages....so I was looking for a dir in the workdir that didn't exist....so I checked the SDK sysroot after I installed it and all the modules are in /usr/lib/python2.716:11
bluelightningebolton: ah ok, at least that's dealt with16:12
ebolton@bluelightning: what's weird is the error itself isn't in a module....that multilib patch touches the core Python code directly...all the code its looking for is there, and as far as I can tell PYTHONHOME is set correctly16:15
bluelightningyeah... I'm assuming "sys" is not actually meant to be the sys module at that point in the code16:16
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC16:16
-YoctoAutoBuilder- build #257 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/25716:16
lpappbluelightning: https://bugzilla.yoctoproject.org/show_bug.cgi?id=759216:17
yoctiBug 7592: normal, Undecided, ---, cristian.iorga, NEW , No detailed explanation of a sanity checker connectivity issue16:17
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC16:17
*** sarahsharp <sarahsharp!~sarah@134.134.137.73> has joined #yocto16:17
eboltonwell, "import sys" is used in the code...so sys is technically a module I think....but just part of core Python....it's not in the extra modules packages16:18
lpappbluelightning: I could probably get along by wiping that list out?16:18
lpappor just simply disabling the sanity check?16:19
bluelightninglpapp: did you put the debug message in to find out which URL was failing to fetch and how?16:19
-YoctoAutoBuilder- build #256 of nightly-fsl-arm-lsb is complete: Failure [failed BuildImages BuildImages_1 BuildImages_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/25616:20
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:20
lpappbluelightning: nope, I guess I would need to put that into Fetch?16:21
*** pev <pev!~pev@2.31.101.83> has quit IRC16:21
bluelightninglpapp: I would have thought you could just print the exception or not catch it16:21
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC16:22
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:24
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC16:26
lpappbluelightning: Fetcher failure for URL: 'git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=HEAD'. The command git ls-remote git://git.yoctoproject.org/yocto-firewall-test refs/heads/HEAD refs/tags/HEAD^{} gave empty output unexpectedly16:27
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:28
bluelightninglpapp: which version of git are you using?16:28
lpappgit version 1.7.10.416:29
bluelightningebolton: hmm, so it looks like sys.lib should be valid for the patched python that we build but isn't part of the standard python API16:30
bluelightningebolton: maybe some kind of mixture of the system python and the libs within the SDK is happening?16:31
eboltonebolton@debian:~/yocto/outbacks4$ which python16:32
eboltonebolton@debian:~/yocto/outbacks4$ env | grep PYTHON16:32
eboltonPYTHONHOME=/opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr16:32
eboltonebolton@debian:~/yocto/outbacks4$16:32
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto16:33
lpappgit version 2.3.5 on my Archlinux, but that is irrelevant now as I run Yocto on Debian 7.7.16:33
*** ddom <ddom!~ddom@p4FFDA393.dip0.t-ipconnect.de> has quit IRC16:33
eboltonbluelightning: sorry, copy/paste spam :) PYTHONHOME looks correct, and it's using the SDK python, not the system one16:33
eboltonbluelightning: not sure what else to check16:34
bluelightninglpapp: hmm, that's odd... that git ls-remote command here returns empty16:34
bluelightningand yet the sanity check passes...16:34
lpappbluelightning: odd16:35
lpappso what can I do to proceed?16:35
bluelightningebolton: "which python" returns nothing?16:36
eboltonbluelightning: no, not sure why that happened16:36
eboltonebolton@debian:~/yocto/outbacks4$ which python16:36
lpappbluelightning: I do not even see a sanity (insane) option for disabling this. I am checking the YRM.16:36
lpapphttp://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-insane16:36
ebolton"/opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr/bin/python"16:37
bluelightninglpapp: that's insane.bbclass, not sanity.bbclass, two different thing16:37
bluelightnings16:37
lpappfair enough, thanks.16:37
eboltonbluelightning: apparently HexChat doesn't like lines starting with a slash :)16:37
lpappso what are my options with this to get along?16:38
bluelightningebolton: oh, right - yeah IRC wouldn't, those are assumed to be commands16:38
lpappremove that entry for the uris variable?16:38
bluelightninglpapp: you could try that, sure16:38
lpappit is not a nice "solution" though.16:38
lpappit would be nice to know what and why exactly it fails.16:38
bluelightningit would be16:39
bluelightningwithout a reproducer though there's not a lot I can do on my end, if you could help track it down that would be very helpful16:39
kergothwe should really enhance sanity.bbclass to support insane-like control over what tests are run, like ERROR_QA & friends16:39
bluelightningkergoth: it's not quite the same situation though... tests that fail there should never fail unless there is something really wrong16:39
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC16:40
bluelightningwhereas insane tests are applied across a wide variety of recipes and can often false-positive16:40
kergothhmm, true16:41
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:41
bluelightningebolton: are you building from the dizzy-1.7.1 release or a recent version of the dizzy branch?16:41
eboltonbluelightning: I "git pull" from dizzy every week or so....not building from the tagged 1.7.1 release16:42
lpappbluelightning: can you help me with tracking it down? I do not even know where to start, but I can follow any hints if they are not very time consuming.16:43
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC16:45
bluelightninglpapp: AFAIK the only parts of the code involved with this failure ought to be the function in sanity.bbclass, and the fetcher i.e. bitbake/lib/bb/fetch2/__init__.py and bitbake/lib/bb/fetch2/git.py16:46
*** manuel__ <manuel__!~manuel@209.6.175.242> has joined #yocto16:46
lpappdo you know which command exactly it runs underneath or is that something to be figured out yet?16:48
bluelightningin theory it's the one called out in the error, i.e. git ls-remote git://git.yoctoproject.org/yocto-firewall-test refs/heads/HEAD refs/tags/HEAD^{}16:49
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:50
*** Levi <Levi!vlevidas@nat/intel/x-slroxyukywwmxqde> has joined #yocto16:50
lpappperhaps I should run that manually?16:52
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-58-76.ip43.fastwebnet.it> has quit IRC16:56
-YoctoAutoBuilder- build #250 of nightly-mips-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/25016:58
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-58-76.ip43.fastwebnet.it> has joined #yocto16:58
bluelightningyou could certainly try16:58
lpappempty output16:59
*** Aethenelle_ <Aethenelle_!~Aethenell@199.15.128.75> has joined #yocto16:59
lpappreturn code is zero, which indicates success16:59
lpappso what is Yocto's issue?16:59
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC17:00
*** Aethenelle_ is now known as Aethenelle17:00
lpappI guess I will need to understand how exactly Fetch works?17:01
bluelightninghave a look at the git fetcher, specifically the bit that's actually doing the ls-remote17:05
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC17:07
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto17:07
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC17:08
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto17:11
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC17:12
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto17:13
-YoctoAutoBuilder- build #247 of nightly-arm-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/24717:17
*** belen2 <belen2!Adium@nat/intel/x-pevlgevzpjskfshz> has joined #yocto17:17
-YoctoAutoBuilder- build #255 of nightly-arm is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/25517:19
*** belen1 <belen1!Adium@nat/intel/x-qnffndtmgebuskkc> has quit IRC17:19
-YoctoAutoBuilder- build #253 of nightly-qa-systemd is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/25317:27
*** vicky <vicky!~androirc@106.213.105.207> has joined #yocto17:29
*** vicky is now known as Guest5808417:29
Guest58084Is there any way to keep two version of shared library in filesystem using yocto17:31
Guest58084When using package revision only one library which is updated will present in fs.17:33
Guest58084But i wanna keep both old and new libs in fs17:33
Guest58084Any ideas?17:33
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto17:36
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has quit IRC17:36
bluelightningGuest58084: you'd need two separately named recipes producing packages that did not install conflicting files in order to achieve that17:36
Guest58084Thanks. But the old lib i am not going to update. Only the new lib is get update in git source.17:40
Guest58084I will compile the first lib at some fixed git tag and new lib from latest git tag.17:41
*** ddom <ddom!~ddom@ip-37-24-103-185.hsi14.unitymediagroup.de> has joined #yocto17:41
bluelightningsure, but you still need two recipes producing separate packages for that17:43
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC17:44
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto17:45
*** tlwoerner <tlwoerner!~trevor@unaffiliated/tlwoerner> has quit IRC17:47
*** belen2 <belen2!Adium@nat/intel/x-pevlgevzpjskfshz> has quit IRC17:48
lpappbluelightning: well, perhaps if the command returns empty output for you, you could print out the output variable in the git.py function?17:50
lpappto see what it returns to you? It returns empty for me just as on the command line, manually.17:51
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has quit IRC17:51
lpappthis line: output = runfetchcmd(cmd, d, True)17:51
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has joined #yocto17:52
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has left #yocto17:54
*** smustafa <smustafa!~mustafa@110.93.212.98> has quit IRC17:54
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has joined #yocto17:55
-YoctoAutoBuilder- build #256 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/25618:00
lpappbluelightning: and anyway, is that command supposed to return empty output or some valid content?18:06
*** Aethenelle_ <Aethenelle_!~Aethenell@199.15.128.78> has joined #yocto18:09
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.75> has quit IRC18:09
*** Aethenelle_ is now known as Aethenelle18:09
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has quit IRC18:13
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC18:13
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto18:14
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC18:20
lpappbluelightning: it makes me think that you do not get the same cmd in the code as I do.18:20
lpappas my command  returns empty for everyone that I talked to.18:20
lpappwould it be possible for you to print out your command?18:21
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has joined #yocto18:21
bluelightninglpapp: ok, so finally I just found that the git URL was removed from CONNECTIVITY_CHECK_URIS back in 201218:22
lpappbut daisy was coming out later, no?18:23
bluelightningyeah18:23
lpappso I do not get the issue then.18:24
bluelightningdid you by chance copy an older poky.conf and then modify it, hence you have the old value?18:24
lpappyes, from the dylan times.18:24
lpappbut even that was released only two years ago18:25
lpappI wonder if it is an inheritage from our early denzil variant.18:25
bluelightningmost likely18:25
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC18:25
lpappit seems that we need to update the config at each release based on how poky proceeds.18:25
lpappyeah, I am unsure because I thought that I redid this for dylan.18:26
lpappnot using any of denzil during the migration.18:26
bluelightningwell, I wouldn't necessarily say that, if you follow the migration guide that ought to be enough18:26
bluelightningin this instance it appears something broke with how that particular URL is handled in that context and since we dropped it from the checked list nobody noticed18:26
lpappwas this mentioned in the migration guide?18:26
bluelightningno, see above18:27
lpapphmm18:27
bluelightningI strongly suspect this is a bug rather than something that needs to be worked around18:27
bluelightningthe key is probably the rev=18:27
lpappoh?18:27
bluelightningI don't think that's commonly used in normal usages of the git fetcher (i.e. SRC_URI within recipes)18:28
lpappok, well, would you like to see another report? And as for the time being, I guess I could just remove that url.18:29
bluelightningif you don't mind filing it, sure18:31
*** seebs_ <seebs_!~seebs@74.122.98.108> has joined #yocto18:31
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC18:31
bluelightningthough if you do it would be worth adding a clarifying comment to the earlier bug that the actual issue is covered by the new one18:31
lpappI think it is still useful to print the exceptions as a separate issue.18:32
*** adelcast1 <adelcast1!~adelcast@130.164.62.224> has joined #yocto18:33
bluelightningyeah I agree, it's just that reading over the report it kind of reads as if it's about both fixing the error and the error message (which I guess it was at the time)18:34
lpappok, hmm, now I am getting this >_< https://paste.kde.org/pqcvlfle518:36
bluelightninghave you done anything to that recipe?18:40
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto18:40
lpappnothing18:40
lpappI copied meta over from the poky daisy release into our repository.18:41
lpappso it oughta be verbatim.18:41
lpappbut I can paste the content just in case if you like.18:41
bluelightningit's probably old... that is covered in the migration guide btw (bb.which -> bb.utils.which)18:41
bluelightningwhereever you have that, that is18:41
lpappstrange.18:42
lpappI thought the meta layer in daisy was supposed to just work?18:42
bluelightningI guarantee that reference was not part of the daisy metadata, it must come from something you have left over18:43
lpappwhere exactly? How can I pin that down?18:43
*** aehs291 <aehs291!aehernan@nat/intel/x-sbgoqmsuprzppwvy> has joined #yocto18:43
bluelightninggrep for it?18:43
*** aehs29 <aehs29!~aehernan@134.134.139.76> has quit IRC18:43
lpappwhere can I find the migration guide? https://www.yoctoproject.org/downloads/core/daisy16118:44
lpappI cannot seem to find the YRM in there.18:44
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC18:44
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto18:45
acidfuhello ! I have a recipe, with a git URI, and I'd like know in what directory the the git is cloned, thank you !18:46
lpapphttp://www.yoctoproject.org/docs/1.6.1/mega-manual/mega-manual.html18:47
lpappnvm, I have just looked for the word "migration" in the mega manual.18:47
bluelightninghttp://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#migration18:49
bluelightningacidfu: ${WORKDIR}/git18:49
bluelightningat least, that's where it's finally cloned to18:50
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:53
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto18:55
acidfuok great !18:57
*** deception <deception!~deception@unaffiliated/deception> has quit IRC18:59
*** sarahsharp <sarahsharp!~sarah@134.134.137.73> has quit IRC18:59
*** sarahsharp <sarahsharp!sarah@nat/intel/x-mkfrpqidxyulaste> has joined #yocto19:00
*** deception <deception!~deception@unaffiliated/deception> has joined #yocto19:01
*** aehs291 <aehs291!aehernan@nat/intel/x-sbgoqmsuprzppwvy> has left #yocto19:06
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto19:08
khem`bluelightning: Is there wiki doc on how to use locked sstate practically19:08
*** seebs_ is now known as seebs19:09
*** dmoseley <dmoseley!~dmoseley@cpe-174-96-222-251.carolina.res.rr.com> has joined #yocto19:09
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC19:10
*** CromFr <CromFr!~CromFr@146.185.162.164> has joined #yocto19:17
*** aehs29 <aehs29!aehernan@nat/intel/x-hyggicsuyujqyajg> has joined #yocto19:17
*** tsramos <tsramos!~tsramos@134.134.139.76> has quit IRC19:22
*** tsramos <tsramos!~tsramos@192.55.55.37> has joined #yocto19:23
*** aehs29 <aehs29!aehernan@nat/intel/x-hyggicsuyujqyajg> has quit IRC19:26
*** aehs29 <aehs29!~aehernan@134.134.137.75> has joined #yocto19:28
*** aehs29 <aehs29!~aehernan@134.134.137.75> has left #yocto19:29
*** pohly <pohly!~pohly@p5DE8CDA6.dip0.t-ipconnect.de> has quit IRC19:29
*** aehs29 <aehs29!~aehernan@134.134.137.75> has joined #yocto19:30
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC19:42
*** khem` is now known as khem[away]19:47
*** khem[away] is now known as khem`19:47
*** aehs29 <aehs29!~aehernan@134.134.137.75> has left #yocto19:47
*** khem` is now known as khem[away]19:49
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has joined #yocto19:49
*** khem[away] is now known as khem`19:50
*** sjolley <sjolley!sjolley@nat/intel/x-blikxjjqlhzasifn> has quit IRC20:01
*** grma <grma!~gruberm@chello213047201250.tirol.surfer.at> has quit IRC20:01
*** onoffon <onoffon!~khem@unaffiliated/khem> has joined #yocto20:10
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC20:14
*** sjolley <sjolley!sjolley@nat/intel/x-bolbtnbgxmjwtexk> has joined #yocto20:27
*** sarahsharp <sarahsharp!sarah@nat/intel/x-mkfrpqidxyulaste> has quit IRC20:28
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC20:29
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto20:31
*** sjolley <sjolley!sjolley@nat/intel/x-bolbtnbgxmjwtexk> has quit IRC20:34
*** sjolley <sjolley!sjolley@nat/intel/x-cnzkoadeghmmhnoi> has joined #yocto20:36
*** ant_home <ant_home!~ant__@host185-253-dynamic.48-82-r.retail.telecomitalia.it> has joined #yocto20:37
*** sjolley <sjolley!sjolley@nat/intel/x-cnzkoadeghmmhnoi> has quit IRC20:43
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has joined #yocto20:45
*** sjolley <sjolley!sjolley@nat/intel/x-lrbzurvxjlfnipsj> has joined #yocto20:45
-YoctoAutoBuilder- build #254 of nightly-fsl-arm is complete: Failure [failed BuildImages_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/25420:51
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has quit IRC20:55
eboltonhey all, is there any way to add a build time dependency to a recipe from local.conf? I'm building Qt, which depends on the OpenGL ES headers, which are being provided by a separate recipe for the graphics driver...20:57
eboltonthe driver is listed as the provider for virtual/opengles2, but it's not being built before Qt for some reason20:58
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has quit IRC20:59
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC20:59
-YoctoAutoBuilder- build #251 of nightly-ipk is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/25121:12
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has quit IRC21:16
*** sarahsharp <sarahsharp!~sarah@192.55.54.42> has joined #yocto21:17
-YoctoAutoBuilder- build #254 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/25421:17
*** sameo <sameo!samuel@nat/intel/x-xzeejzrmhzqmkqvx> has joined #yocto21:17
*** sarahsharp <sarahsharp!~sarah@192.55.54.42> has quit IRC21:23
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC21:33
otaviopidge: I made the fido branch for meta-fsl-arm21:35
pidgeotavio, ty!21:35
*** sarahsharp <sarahsharp!sarah@nat/intel/x-vkghdyqmbdjfythk> has joined #yocto21:37
-YoctoAutoBuilder- build #256 of nightly-non-gpl3 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/25621:37
*** tsramos <tsramos!~tsramos@192.55.55.37> has quit IRC21:41
-YoctoAutoBuilder- build #255 of nightly-qa-skeleton is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/builds/25521:46
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has quit IRC21:51
*** ebolton <ebolton!~ebolton@208.93.135.69> has quit IRC21:54
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto22:01
*** sarahsharp <sarahsharp!sarah@nat/intel/x-vkghdyqmbdjfythk> has quit IRC22:03
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto22:04
*** onoffon <onoffon!~khem@unaffiliated/khem> has quit IRC22:06
*** sjolley <sjolley!sjolley@nat/intel/x-lrbzurvxjlfnipsj> has quit IRC22:06
*** ddom <ddom!~ddom@ip-37-24-103-185.hsi14.unitymediagroup.de> has quit IRC22:07
-YoctoAutoBuilder- build #254 of nightly-qa-logrotate is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/25422:08
-YoctoAutoBuilder- build #259 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/25922:10
*** fignew <fignew!~woowoo@unaffiliated/fignew> has quit IRC22:13
*** manuel__ <manuel__!~manuel@209.6.175.242> has quit IRC22:15
*** ant_home <ant_home!~ant__@host185-253-dynamic.48-82-r.retail.telecomitalia.it> has quit IRC22:20
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has joined #yocto22:20
*** sjolley <sjolley!sjolley@nat/intel/x-loaxzgescnzmjrnx> has joined #yocto22:25
-YoctoAutoBuilder- build #255 of nightly-qa-pam is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/25522:25
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has quit IRC22:29
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has quit IRC22:37
*** sarahsharp <sarahsharp!sarah@nat/intel/x-gcmzoxxkreowrstr> has joined #yocto22:38
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto22:40
*** anselmolsm <anselmolsm!~anselmo@192.55.54.40> has quit IRC22:42
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC22:44
-YoctoAutoBuilder- build #256 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/25622:45
-YoctoAutoBuilder- build #251 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/25122:46
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC22:57
-YoctoAutoBuilder- build #256 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/25623:02
-YoctoAutoBuilder- build #251 of build-appliance is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/25123:03
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto23:17
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC23:17
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto23:17
*** sameo <sameo!samuel@nat/intel/x-xzeejzrmhzqmkqvx> has quit IRC23:18
*** agust <agust!~agust@pD9E2FD0A.dip0.t-ipconnect.de> has quit IRC23:18
*** Levi <Levi!vlevidas@nat/intel/x-slroxyukywwmxqde> has quit IRC23:20
*** sjolley <sjolley!sjolley@nat/intel/x-loaxzgescnzmjrnx> has quit IRC23:24
-YoctoAutoBuilder- build #257 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/25723:30
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has quit IRC23:35
-YoctoAutoBuilder- build #254 of nightly-qa-systemd is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/25423:42
*** sjolley <sjolley!sjolley@nat/intel/x-eggvpxihpmderngd> has joined #yocto23:51
*** sarahsharp <sarahsharp!sarah@nat/intel/x-gcmzoxxkreowrstr> has quit IRC23:52
-YoctoAutoBuilder- build #248 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/24823:52
-YoctoAutoBuilder- build #255 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/25523:52

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