bk_lsr | kergoth: thanks, i'll check those out | 00: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/252 | 00:01 | |
*** sjolley <sjolley!sjolley@nat/intel/x-rqvwizakjafbeytj> has quit IRC | 00: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/254 | 00:05 | |
bk_lsr | kergoth: got it working. what i needed & couldn't find was the destsuffix param. thanks! | 00:10 |
kergoth | ah, np | 00: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/254 | 00:23 | |
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has quit IRC | 00: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/250 | 00:25 | |
*** tlwoerner_ <tlwoerner_!~tlwoerner@unaffiliated/tlwoerner> has joined #yocto | 00:29 | |
*** bzb <bzb!~bzb@198-48-196-219.cpe.pppoe.ca> has joined #yocto | 00: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/257 | 00:38 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 00: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/256 | 00:51 | |
*** bzb <bzb!~bzb@198-48-196-219.cpe.pppoe.ca> has quit IRC | 00: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/246 | 01:07 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 01: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/253 | 01:33 | |
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC | 01: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 #yocto | 01: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/255 | 01:52 | |
*** hsychla <hsychla!~hsychla@2001:6f8:12d9:13:6deb:b865:8f43:874e> has quit IRC | 02:04 | |
*** sarahsharp <sarahsharp!~sarah@134.134.139.74> has quit IRC | 02:05 | |
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has joined #yocto | 02:12 | |
*** redengin <redengin!~redengin@c-73-193-21-136.hsd1.wa.comcast.net> has joined #yocto | 02: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/255 | 02:15 | |
*** hsychla <hsychla!~hsychla@2001:6f8:12d9:13:e12d:fc12:5d78:a7e7> has joined #yocto | 02:17 | |
*** Guest66260 <Guest66260!~gary@pool-98-114-34-165.phlapa.fios.verizon.net> has joined #yocto | 02:28 | |
Guest66260 | Would someone have information on including a Windows version of QEMU in the nativesdk built including the mingw compiler? | 02:31 |
redengin | Guest66260, what do you mean? are you trying to do poky builds under mingw/cygwin? | 02:36 |
khem` | kergoth: yt? | 02:37 |
Guest66260 | I have a requirement to use windows for building applications on top of the root file system. | 02:38 |
Guest66260 | I want to build the SDK for windows including a version of QEMU that can run in windows using the poky image. | 02:39 |
Guest66260 | the meta-mingw builds the GCC cross compiler for windows but I haven't found a way to get QEMU yet. | 02:40 |
kergoth | just use the standard yocto sdk mechanisms with SDKMACHINE set to one of the sdkmachines provided by meta-mingw | 02:40 |
kergoth | e.g. SDKMACHINE="i686-mingw32" bitbake -c populate_sdk core-image-base | 02:40 |
kergoth | then 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_TASK | 02:41 |
kergoth | khem`: somewhat, whats up | 02:41 |
Guest66260 | Hmmm. 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 invalidated | 02:45 |
khem` | since in do_install I use ${S} | 02:45 |
khem` | now this change in S is due to externalsrc | 02:45 |
khem` | are there any good ways to avoid this invalidation ? | 02:46 |
kergoth | not 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 paths | 02:46 |
kergoth | e.g. ${WORKDIR}/foo | 02:46 |
kergoth | do_install[vardepsexclude] += "S" is probably your best bet | 02:46 |
Guest66260 | My MACHINE is qemuarm and SDKMACHINE is X86_64-mingw32. Output is only the mingw toolchain, no QEMU. I have not done the TOOLCHAIN_HOST_TASK | 02:47 |
* kergoth rather liked his checksumming implementation better than the current one in some ways.. it checksummed expanded variables, but kept blacklisted variables as unexpanded | 02:47 | |
kergoth | Guest66260: output of *what*? | 02:47 |
kergoth | you haven't said what your'e building | 02:47 |
Guest66260 | Thanks for the suggestion. I will try it. | 02:47 |
kergoth | the yocto sdk includes quite a lot more than just a toolchain, so it sounds like you're not building with -c populate_sdk | 02:48 |
redengin | Guest66260, wouldn't it just be easier to run a virtual machine of the poky SDK image? I'm not sure I'd trust mingw | 02:49 |
Guest66260 | I 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 | |
Guest66260 | It 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 sdkmachines | 02:50 | |
redengin | Guest66260, are you forced to do all the native compilation using mingw or can you simply run a linux virtual machine under windows? | 02:51 |
kergoth | A VM does sound like it'd be a lot more pleasant, but not always an option | 02:51 |
Guest66260 | Our formal build team can't use a Linux VM ... yet. | 02:54 |
Guest66260 | I 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 nods | 02:57 | |
Guest66260 | So I was just reviewing what I previously did. I actually ran bitbake -c populate_sdk core-image-minimal | 02:57 |
Guest66260 | But I had thought that was referring to a minimal root file system, not SDK. | 02:57 |
Guest66260 | I'm re-running now with core-image-base | 02:58 |
redengin | Guest66260, what type of image are you trying to build? | 03:03 |
Guest66260 | redengin, 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 |
Guest66260 | So QEMU is nice to test out that small system on the desktop. | 03:11 |
redengin | ah, so you don't want an arm toolchain in the device image | 03:12 |
redengin | which arm boot loader are you using? | 03:13 |
kergoth | does qemu even run on windows? | 03:14 |
Guest66260 | we have a simple hand written boot loader and also looking to see if u-boot will fit. | 03:14 |
Guest66260 | I'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 |
kergoth | ah, cool | 03:16 |
Guest66260 | It was more the idea of a one stop full SDK rather than an absolute must that Yocto build the windows QEMU. | 03:16 |
redengin | so what does your bootloader expect to find in order to boot? | 03:17 |
Guest66260 | Actually 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 |
Guest66260 | We partition the flash into a number of sections. kernel, device tree, squashfs RFS and app partition. | 03:19 |
Guest66260 | so the boot loader copies kernel and RFS to RAM and jumps. | 03:19 |
Guest66260 | we have it working on an older device but it's pretty limited. u-boot would offer some nice debug features. | 03:20 |
redengin | your bitbake output doens't include the kernel and a rfs? | 03:20 |
Guest66260 | it puts the zImage and RFS under deploy/images | 03:22 |
Guest66260 | we also want the SDK which is under deploy/SDK | 03:22 |
Guest66260 | the image actually does not contain a compiler as the device is not big enough. | 03:23 |
Guest66260 | the goal is only for the app partition to be built in Windows as the Yocto image is built obviously in Linux. | 03:24 |
Guest66260 | But the build team wants the app build in Windows. Such a pain. | 03:24 |
Guest66260 | And it would help to provide simple test qemu support in windows as well. | 03:25 |
nrossi | Guest66260: I've been able to build QEMU with the meta-mingw layer before, there were some minor issues. | 03:31 |
Guest66260 | nrossi, did you have to add extra configuration options to have the meta-mingw layer build qemu? | 03:34 |
nrossi | it 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 |
Guest66260 | I just got done with a re-run of bitbake -c populate_sdk core-image-base and still no qemu in the SDK. | 03:35 |
nrossi | try building "nativesdk-qemu" and see how far you get first. | 03:35 |
Guest66260 | ya, when I actually built qemu on a Windows mingw environment, getting device tree support was a bear. | 03:36 |
Guest66260 | I had to hack that build but it worked. | 03:37 |
Guest66260 | I was hoping Windows qemu build done in Linux would actually not require that hack. | 03:37 |
nrossi | and to get the populate_sdk to include qemu i think you need to add it to "TOOLCHAIN_HOST_TASK" | 03:37 |
nrossi | if i remember correctly the hack was due to posix compliance of dtc | 03:38 |
nrossi | and it was in the actual compiler and no in libfdt | 03:38 |
Guest66260 | hmm, 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 |
redengin | ah I see you're trying to do a qemu build using the bitbake native toolchain | 03:42 |
nrossi | Oh one other thing, you cant build qemu for mingw64, you have to target 32-bit. QEMU has a hard limitation on that one | 03:43 |
Guest66260 | I 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 IRC | 03:47 | |
*** sjolley <sjolley!~sjolley@134.134.137.71> has joined #yocto | 03:59 | |
*** Guest66260 <Guest66260!~gary@pool-98-114-34-165.phlapa.fios.verizon.net> has quit IRC | 04:31 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto | 04:54 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC | 05:02 | |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto | 05:11 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto | 05:11 | |
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has joined #yocto | 05:21 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC | 05:22 | |
*** ScarEye <ScarEye!~scareye@static-64-61-84-232.isp.broadviewnet.net> has quit IRC | 05:24 | |
*** ScarEye <ScarEye!~scareye@static-64-61-84-232.isp.broadviewnet.net> has joined #yocto | 05:25 | |
*** Crofton <Crofton!~balister@pool-108-44-109-154.ronkva.east.verizon.net> has quit IRC | 05:32 | |
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has quit IRC | 05:33 | |
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has joined #yocto | 05:34 | |
*** Crofton|work <Crofton|work!~balister@pool-108-44-109-154.ronkva.east.verizon.net> has quit IRC | 05:35 | |
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has joined #yocto | 05:41 | |
*** agust <agust!~agust@pD9E2FD0A.dip0.t-ipconnect.de> has joined #yocto | 05:44 | |
*** Crofton|work <Crofton|work!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has joined #yocto | 05:48 | |
*** Crofton <Crofton!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has joined #yocto | 05:48 | |
*** Crofton <Crofton!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has quit IRC | 05:59 | |
*** Crofton|work <Crofton|work!~balister@pool-71-171-11-120.ronkva.east.verizon.net> has quit IRC | 05:59 | |
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto | 06:06 | |
*** Crofton|work <Crofton|work!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has joined #yocto | 06:12 | |
*** Crofton <Crofton!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has joined #yocto | 06:12 | |
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto | 06:18 | |
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto | 06:19 | |
*** wadim_ <wadim_!~egorov@mail.x-arc.co.uk> has joined #yocto | 06:23 | |
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC | 06:38 | |
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto | 06:38 | |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC | 06:38 | |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto | 06:40 | |
*** pohly <pohly!~pohly@p5DE8CDA6.dip0.t-ipconnect.de> has joined #yocto | 06:42 | |
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto | 06:50 | |
*** RP <RP!~richard@5751f4a1.skybroadband.com> has quit IRC | 06:58 | |
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC | 06:58 | |
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC | 06:59 | |
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto | 06:59 | |
*** smustafa <smustafa!~mustafa@110.93.212.98> has joined #yocto | 07:04 | |
*** RP <RP!~richard@5751f4a1.skybroadband.com> has joined #yocto | 07:07 | |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 07:19 | |
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 07:30 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 07:30 | |
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto | 07:31 | |
*** _valle_ <_valle_!~valle@195.198.200.72> has quit IRC | 07:41 | |
*** sameo <sameo!~samuel@192.55.55.41> has joined #yocto | 07:41 | |
*** _valle_ <_valle_!~valle@195-198-200-72.customer.telia.com> has joined #yocto | 07:42 | |
*** Crofton <Crofton!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has quit IRC | 07:45 | |
*** Crofton|work <Crofton|work!~balister@pool-108-44-111-180.ronkva.east.verizon.net> has quit IRC | 07:45 | |
*** belen <belen!~Adium@192.198.151.44> has joined #yocto | 07:57 | |
*** Crofton|work <Crofton|work!~balister@pool-71-171-11-220.ronkva.east.verizon.net> has joined #yocto | 07:58 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC | 08:00 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has joined #yocto | 08:01 | |
*** sameo <sameo!~samuel@192.55.55.41> has quit IRC | 08:07 | |
*** belen <belen!~Adium@192.198.151.44> has quit IRC | 08:07 | |
*** sameo <sameo!~samuel@192.55.55.41> has joined #yocto | 08:07 | |
*** volker_123456 <volker_123456!~quassel@host-80-81-19-29.customer.m-online.net> has quit IRC | 08:07 | |
*** tmpsantos <tmpsantos!~tmpsantos@a88-115-217-160.elisa-laajakaista.fi> has joined #yocto | 08:07 | |
*** volker_123456 <volker_123456!~quassel@host-188-174-253-51.customer.m-online.net> has joined #yocto | 08:08 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 08:09 | |
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto | 08:14 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC | 08:14 | |
*** jku <jku!jku@nat/intel/x-axevksualktrxcin> has joined #yocto | 08:17 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has joined #yocto | 08:18 | |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 08:24 | |
*** rahc <rahc!rah@pasanda.collabora.co.uk> has joined #yocto | 08:24 | |
bluelightning | morning all | 08:27 |
rahc | morning | 08:28 |
rahc | I'm a bit confused by the runqemu and runqemu-internal scripts | 08:28 |
rahc | http://codepad.org/wlSiwUQP | 08:28 |
nrossi | rahc: yer they are not much fun :P | 08:29 |
rahc | runqemu-internal has support for a "qemuarmv7" MACHINE but runqemu does not | 08:29 |
rahc | nrossi: would you accept patches to make runqemu support "qemuarmv7"? | 08:29 |
rahc | or even make it a bit more nuanced, like being able to specify appropriate options for "-cpu", like cortex-a8 or cortex-a9 | 08:30 |
rahc | I want to emulate a cortex-a9 | 08:30 |
nrossi | im not the maintainer, i've just had many a war with those runqemu scripts :P | 08:31 |
rahc | maintainers: would you accept patches to make runqemu support "qemuarmv7"? :-) | 08:31 |
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto | 08:31 | |
nrossi | you can always submit it, i dont see any particular reason for it not being accepted | 08:31 |
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC | 08:35 | |
*** ddom <ddom!~ddom@p4FFDA393.dip0.t-ipconnect.de> has joined #yocto | 08:36 | |
bluelightning | I think we'd probably accept it | 08:38 |
bluelightning | we're probably overdue to implement a proper extension mechanism for runqemu though | 08:38 |
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has joined #yocto | 08:39 | |
bluelightning | having said that, qemuarmv7 would probably be most appropriately supported within OE-Core even if that were in place | 08:39 |
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has quit IRC | 08:43 | |
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto | 08:47 | |
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has joined #yocto | 08:48 | |
*** pev <pev!~pev@2.31.101.83> has joined #yocto | 08:56 | |
*** belen <belen!Adium@nat/intel/x-dqxiudqcwbiihhkl> has joined #yocto | 09:01 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC | 09:01 | |
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has joined #yocto | 09:14 | |
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has quit IRC | 09:17 | |
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 09:18 | |
*** jmleo <jmleo!~jmleo@LDijon-156-64-30-180.w80-15.abo.wanadoo.fr> has joined #yocto | 09:22 | |
*** ssk <ssk!~ssk@183.82.4.49> has quit IRC | 09:28 | |
*** ssk <ssk!~ssk@183.82.4.49> has joined #yocto | 09:53 | |
ericbutters | ping kergoth | 09:55 |
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has quit IRC | 10:04 | |
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has joined #yocto | 10:06 | |
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has quit IRC | 10:19 | |
*** Crofton <Crofton!~balister@pool-71-171-11-220.ronkva.east.verizon.net> has joined #yocto | 10:23 | |
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has joined #yocto | 10:25 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto | 10:29 | |
lpapp | hi, 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 |
lpapp | http://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 #yocto | 10:35 | |
*** belen <belen!Adium@nat/intel/x-dqxiudqcwbiihhkl> has quit IRC | 10:36 | |
bluelightning | lpapp: you save a bit of time on repeated bitbake invocations because it's in memory | 10:46 |
bluelightning | lpapp: 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 IRC | 10:48 | |
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto | 10:53 | |
*** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC | 10:59 | |
*** ccube <ccube!ccube@nx.mindrunner.de> has joined #yocto | 11:00 | |
*** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC | 11:01 | |
*** ccube <ccube!ccube@nx.mindrunner.de> has joined #yocto | 11:03 | |
lpapp | bluelightning: ok, I am updating from dylan to daisy | 11:05 |
lpapp | and this memres turned up, but then we possibly do not need it as memory is not a big deal on powerful build machines, is it | 11:05 |
bluelightning | well, it's not about that, it's about whether you are bothered by the time bitbake normally takes to start up | 11:06 |
bluelightning | personally I put up with it | 11:06 |
*** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC | 11:07 | |
bluelightning | but 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 #yocto | 11:07 | |
lpapp | ok, thanks. | 11:10 |
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has joined #yocto | 11:11 | |
cart_man | Hey whats the recepy name for Yocto-KERNEL-HEADERS? | 11:11 |
cart_man | or Core-Devel-Tools | 11:11 |
cart_man | ? | 11:11 |
cart_man | also...is there a Yocto apt-get recepy I can add? | 11:12 |
*** jku <jku!jku@nat/intel/x-axevksualktrxcin> has quit IRC | 11:18 | |
*** jku <jku!jku@nat/intel/x-dkfihqgijuevowae> has joined #yocto | 11:20 | |
*** mag0 <mag0!~mago@88.131.56.168> has quit IRC | 11:26 | |
*** radhus <radhus!~radhus@sevh.radhuset.org> has quit IRC | 11:35 | |
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC | 11: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/250 | 11:37 | |
*** radhus <radhus!~radhus@sevh.radhuset.org> has joined #yocto | 11:38 | |
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto | 11:40 | |
*** wCPO <wCPO!~kristian@188.228.31.139> has joined #yocto | 11:40 | |
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has joined #yocto | 11:40 | |
jaeckel | I 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 from | 11:41 |
*** jchonig <jchonig!~quassel@firewall.honig.net> has quit IRC | 11:43 | |
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 11:50 | |
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has joined #yocto | 11:51 | |
*** jchonig <jchonig!~quassel@firewall.honig.net> has joined #yocto | 11:52 | |
lpapp | are you looking for a dependency graph? | 11:54 |
jaeckel | no, I am looking for the step after having the dependency graph, to find where this dependency originates | 11:55 |
lpapp | ok, 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/253 | 12:00 | |
*** zaman1 <zaman1!~zaman@192.198.151.44> has joined #yocto | 12:03 | |
*** zaman <zaman!~zaman@192.198.151.44> has quit IRC | 12:06 | |
jaeckel | sorry 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 layers | 12:07 |
jaeckel | now I'd like to find out what creates that dependency | 12:07 |
*** mago_ <mago_!~mago@88.131.56.168> has joined #yocto | 12:10 | |
bluelightning | jaeckel: I usually search the graph for '-> the-dependency-name' | 12:21 |
jaeckel | yeah I searched where the discovery came from | 12:21 |
jaeckel | now I saw that this is caused by VIRTUAL-RUNTIME_initscripts = "recipe2" | 12:22 |
jaeckel | and this variable is automatically used in DEPENDS | 12:22 |
cart_man | Hey guys how can I download the Yocto kernel headers? | 12:24 |
jaeckel | is there some documentation where I can see what VIRTUAL-RUNTIME_initscripts is intended to be used for? | 12:26 |
bluelightning | cart_man: can you explain the context of the question? what are you trying to do? | 12:26 |
bluelightning | jaeckel: 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 nothing | 12:27 |
cart_man | bluelightning,Im trying to write PCI drivers | 12:28 |
jaeckel | so 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_man | and I need the Kernel headers | 12:28 |
cart_man | usually in Ubuntu it will be apt-get install kernel-headers | 12:28 |
cart_man | but I cant get apt-get in Yocto so I have no idea how getting then is possible | 12:29 |
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto | 12:29 | |
bluelightning | cart_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 |
bluelightning | cart_man: it's also going to depend on what machine you are targeting | 12:31 |
*** frsc <frsc!~frsc@x5d84120c.dyn.telefonica.de> has joined #yocto | 12:31 | |
cart_man | Well the chipset determines the sort of kernel right? | 12:32 |
cart_man | Ghez I have idea where to even begin searching for it | 12:33 |
bluelightning | cart_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 |
bluelightning | then, build the kernel and you will get the kernel headers as part of that process | 12:35 |
bluelightning | we have a kernel development manual: http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html | 12:36 |
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has joined #yocto | 12: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/255 | 12:45 | |
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has left #yocto | 12:49 | |
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has joined #yocto | 12:49 | |
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has left #yocto | 12:49 | |
*** manuel__ <manuel__!~manuel@c-73-16-8-100.hsd1.ma.comcast.net> has quit IRC | 12:53 | |
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has quit IRC | 12:59 | |
*** Levi <Levi!~vlevidas@134.134.137.71> has joined #yocto | 13: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/254 | 13: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/254 | 13:04 | |
*** tlwoerner_ <tlwoerner_!~tlwoerner@unaffiliated/tlwoerner> has quit IRC | 13:05 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 13:17 | |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has joined #yocto | 13:22 | |
*** tsramos <tsramos!~tsramos@134.134.139.76> has joined #yocto | 13:24 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 13:25 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 13:25 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 13:28 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 13:28 | |
*** manuel__ <manuel__!~manuel@209.6.175.242> has joined #yocto | 13:32 | |
*** anselmolsm <anselmolsm!~anselmo@192.55.54.40> has joined #yocto | 13:36 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 13:38 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 13:38 | |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has quit IRC | 13:42 | |
*** belen2 <belen2!Adium@nat/intel/x-erpnaqyyipmctuoq> has joined #yocto | 13:45 | |
*** belen1 <belen1!Adium@nat/intel/x-vwkboioeafwkhcwd> has quit IRC | 13: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/253 | 13: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/250 | 13:48 | |
*** wadim_ <wadim_!~egorov@mail.x-arc.co.uk> has quit IRC | 13: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/258 | 13:57 | |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC | 14:02 | |
*** frsc <frsc!~frsc@x5d84120c.dyn.telefonica.de> has quit IRC | 14:03 | |
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC | 14:05 | |
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC | 14:07 | |
*** cart_man <cart_man!~cart_man@gwise.truvelo.co.za> has quit IRC | 14:08 | |
lpapp | bluelightning: are you still about? | 14:13 |
lpapp | bluelightning: I am getting this after copying the daisy directories over, TEMPLATECONF=meta-foo/conf . oe-init-build-env | 14: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/.templateconf | 14:14 |
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has quit IRC | 14:15 | |
*** belen1 <belen1!Adium@nat/intel/x-lxxgckntypkzzqvj> has joined #yocto | 14:16 | |
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has joined #yocto | 14:17 | |
bluelightning | lpapp: not sure, it's not a known bug AFAIK | 14:18 |
*** belen2 <belen2!Adium@nat/intel/x-erpnaqyyipmctuoq> has quit IRC | 14:18 | |
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 14:18 | |
*** belen1 <belen1!Adium@nat/intel/x-lxxgckntypkzzqvj> has quit IRC | 14:20 | |
*** belen1 <belen1!Adium@nat/intel/x-lmvbsedfwxnvyrfi> has joined #yocto | 14:20 | |
*** jku <jku!jku@nat/intel/x-dkfihqgijuevowae> has quit IRC | 14:22 | |
*** belen1 <belen1!Adium@nat/intel/x-lmvbsedfwxnvyrfi> has quit IRC | 14:22 | |
*** belen1 <belen1!Adium@nat/intel/x-qzvfbhpjtaresijp> has joined #yocto | 14:24 | |
*** jku <jku!~jku@85-76-53-19-nat.elisa-mobile.fi> has joined #yocto | 14:24 | |
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto | 14:26 | |
lpapp | bluelightning: sure, it is pebkac, thanks. | 14:27 |
lpapp | I did not copy that file over, I thought oe-... bitbake, meta and scripts would be enough | 14:27 |
lpapp | apparently, I need that "hidden" file, too. | 14:27 |
lpapp | is there any other files that I forgot to copy over? | 14:30 |
bluelightning | not that I am aware of | 14:30 |
lpapp | bluelightning: thanks, this is odd for bitbake myimage, https://paste.kde.org/pmw3pqiyf | 14:32 |
bluelightning | proxy settings set correctly? | 14:34 |
lpapp | our network is working with dylan. | 14:34 |
bluelightning | all that check does is try to fetch some dummy data from yoctoproject.org | 14:35 |
bluelightning | using bitbake's fetcher | 14:35 |
*** dmoseley1 <dmoseley1!~dmoseley@cpe-174-96-222-251.carolina.res.rr.com> has quit IRC | 14:36 | |
lpapp | strange. | 14:37 |
lpapp | because there are no problems with dylan, only now with daisy. | 14:37 |
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto | 14:37 | |
lpapp | does this operation depend on some config? | 14:40 |
*** hugovs <hugovs!~hugo@177.159.144.73> has joined #yocto | 14: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/255 | 14:46 | |
bluelightning | lpapp: nothing that the fetcher doesn't use - the implementation is check_connectivity() in meta/classes/sanity.bbclass | 14:52 |
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC | 15:01 | |
lpapp | has that changed between dylan and daisy? | 15:01 |
*** jku <jku!~jku@85-76-53-19-nat.elisa-mobile.fi> has quit IRC | 15:01 | |
*** adelcast <adelcast!~adelcast@130.164.62.82> has left #yocto | 15:01 | |
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC | 15:01 | |
bluelightning | git blame says that function itself hasn't changed materially since 2011 | 15:02 |
bluelightning | it's a bit annoying that it doesn't actually report the failure | 15:04 |
*** neur0Fuzzy <neur0Fuzzy!~neur0Fuzz@p239.net182021249.tokai.or.jp> has quit IRC | 15:04 | |
lpapp | yaeh :/ | 15:04 |
lpapp | perhaps you can patch that? | 15:04 |
*** sameo <sameo!~samuel@192.55.55.41> has quit IRC | 15:05 | |
*** Levi <Levi!~vlevidas@134.134.137.71> has quit IRC | 15:05 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto | 15: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/255 | 15:06 | |
lpapp | bluelightning: I guess I will need to put debug statements into that file then or shall I try something simpler? | 15:07 |
bluelightning | lpapp: that's really the only way to determine what's going wrong at this point | 15:08 |
*** sjolley <sjolley!~sjolley@134.134.137.71> has quit IRC | 15:12 | |
*** sarahsharp <sarahsharp!~sarah@134.134.137.75> has joined #yocto | 15:22 | |
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 15:23 | |
lpapp | bluelightning: shall I raise a report for making the error reporting better for this? | 15:25 |
*** sarahsharp <sarahsharp!~sarah@134.134.137.75> has quit IRC | 15:27 | |
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC | 15:28 | |
lpapp | bluelightning: we have some internal mirrors for downloading the software should that be an isuse. | 15:32 |
lpapp | issue* | 15:32 |
*** aehs29 <aehs29!~aehernan@134.134.139.76> has joined #yocto | 15:33 | |
bluelightning | lpapp: yes please file a bug for the error message | 15:34 |
lpapp | bluelightning: ok, but have you checked it in the latest version? It is from daisy. | 15:35 |
bluelightning | lpapp: 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 setup | 15:35 |
lpapp | seems the latest is verbatim | 15:36 |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC | 15:37 | |
*** sjolley <sjolley!sjolley@nat/intel/x-blikxjjqlhzasifn> has joined #yocto | 15:40 | |
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has quit IRC | 15:41 | |
*** wCPO <wCPO!~kristian@188.228.31.139> has joined #yocto | 15:41 | |
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has joined #yocto | 15:41 | |
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC | 15:43 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 15:45 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto | 15:52 | |
lpapp | bluelightning: we have our own SOURCE_MIRROR_URL = "http://foo/yocto/downloads" | 15:52 |
lpapp | could that be the issue? | 15:52 |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-oeepswbjxrmflxza> has joined #yocto | 15:54 | |
lpapp | it is in our distro/foo.conf | 15:54 |
*** manuel__ <manuel__!~manuel@209.6.175.242> has quit IRC | 15:56 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 15:56 | |
lpapp | bluelightning: I also have CONNECTIVITY_CHECK_URIS | 15:58 |
bluelightning | lpapp: 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 working | 15:58 |
lpapp | https://paste.kde.org/pjspf8spa | 15:59 |
*** ebolton <ebolton!~ebolton@208.93.135.69> has joined #yocto | 15:59 | |
bluelightning | lpapp: right, that's the default value... | 16:00 |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-oeepswbjxrmflxza> has quit IRC | 16:00 | |
lpapp | yes | 16:00 |
*** belen1 <belen1!Adium@nat/intel/x-qzvfbhpjtaresijp> has quit IRC | 16:02 | |
*** belen1 <belen1!Adium@nat/intel/x-qnffndtmgebuskkc> has joined #yocto | 16:02 | |
*** blitz00 <blitz00!stefans@nat/intel/x-ixstbdgmnxoqvoki> has joined #yocto | 16:03 | |
ebolton | hey 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 |
ebolton | File "/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 |
ebolton | AttributeError: 'module' object has no attribute 'lib' | 16:03 |
*** blitz00 <blitz00!stefans@nat/intel/x-ixstbdgmnxoqvoki> has quit IRC | 16:03 | |
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto | 16:03 | |
ebolton | the 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 strange | 16:04 |
bluelightning | ebolton: I meant to reply to your email - I honestly don't know what could be going wrong there :( | 16:05 |
bluelightning | ebolton: is nativesdk-python-modules *definitely* part of the SDK now? your email was suggesting that that wasn't working | 16:08 |
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has quit IRC | 16:08 | |
ebolton | bluelightning: 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.7 | 16:11 |
bluelightning | ebolton: ah ok, at least that's dealt with | 16: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 correctly | 16:15 |
bluelightning | yeah... I'm assuming "sys" is not actually meant to be the sys module at that point in the code | 16:16 |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC | 16: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/257 | 16:16 | |
lpapp | bluelightning: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7592 | 16:17 |
yocti | Bug 7592: normal, Undecided, ---, cristian.iorga, NEW , No detailed explanation of a sanity checker connectivity issue | 16:17 |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 16:17 | |
*** sarahsharp <sarahsharp!~sarah@134.134.137.73> has joined #yocto | 16:17 | |
ebolton | well, "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 packages | 16:18 |
lpapp | bluelightning: I could probably get along by wiping that list out? | 16:18 |
lpapp | or just simply disabling the sanity check? | 16:19 |
bluelightning | lpapp: 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/256 | 16:20 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 16:20 | |
lpapp | bluelightning: nope, I guess I would need to put that into Fetch? | 16:21 |
*** pev <pev!~pev@2.31.101.83> has quit IRC | 16:21 | |
bluelightning | lpapp: I would have thought you could just print the exception or not catch it | 16:21 |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 16:22 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 16:24 | |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 16:26 | |
lpapp | bluelightning: 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 unexpectedly | 16:27 |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 16:28 | |
bluelightning | lpapp: which version of git are you using? | 16:28 |
lpapp | git version 1.7.10.4 | 16:29 |
bluelightning | ebolton: 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 API | 16:30 |
bluelightning | ebolton: maybe some kind of mixture of the system python and the libs within the SDK is happening? | 16:31 |
ebolton | ebolton@debian:~/yocto/outbacks4$ which python | 16:32 |
ebolton | ebolton@debian:~/yocto/outbacks4$ env | grep PYTHON | 16:32 |
ebolton | PYTHONHOME=/opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr | 16:32 |
ebolton | ebolton@debian:~/yocto/outbacks4$ | 16:32 |
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto | 16:33 | |
lpapp | git 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 IRC | 16:33 | |
ebolton | bluelightning: sorry, copy/paste spam :) PYTHONHOME looks correct, and it's using the SDK python, not the system one | 16:33 |
ebolton | bluelightning: not sure what else to check | 16:34 |
bluelightning | lpapp: hmm, that's odd... that git ls-remote command here returns empty | 16:34 |
bluelightning | and yet the sanity check passes... | 16:34 |
lpapp | bluelightning: odd | 16:35 |
lpapp | so what can I do to proceed? | 16:35 |
bluelightning | ebolton: "which python" returns nothing? | 16:36 |
ebolton | bluelightning: no, not sure why that happened | 16:36 |
ebolton | ebolton@debian:~/yocto/outbacks4$ which python | 16:36 |
lpapp | bluelightning: I do not even see a sanity (insane) option for disabling this. I am checking the YRM. | 16:36 |
lpapp | http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-insane | 16:36 |
ebolton | "/opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr/bin/python" | 16:37 |
bluelightning | lpapp: that's insane.bbclass, not sanity.bbclass, two different thing | 16:37 |
bluelightning | s | 16:37 |
lpapp | fair enough, thanks. | 16:37 |
ebolton | bluelightning: apparently HexChat doesn't like lines starting with a slash :) | 16:37 |
lpapp | so what are my options with this to get along? | 16:38 |
bluelightning | ebolton: oh, right - yeah IRC wouldn't, those are assumed to be commands | 16:38 |
lpapp | remove that entry for the uris variable? | 16:38 |
bluelightning | lpapp: you could try that, sure | 16:38 |
lpapp | it is not a nice "solution" though. | 16:38 |
lpapp | it would be nice to know what and why exactly it fails. | 16:38 |
bluelightning | it would be | 16:39 |
bluelightning | without 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 helpful | 16:39 |
kergoth | we should really enhance sanity.bbclass to support insane-like control over what tests are run, like ERROR_QA & friends | 16:39 |
bluelightning | kergoth: it's not quite the same situation though... tests that fail there should never fail unless there is something really wrong | 16:39 |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 16:40 | |
bluelightning | whereas insane tests are applied across a wide variety of recipes and can often false-positive | 16:40 |
kergoth | hmm, true | 16:41 |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 16:41 | |
bluelightning | ebolton: are you building from the dizzy-1.7.1 release or a recent version of the dizzy branch? | 16:41 |
ebolton | bluelightning: I "git pull" from dizzy every week or so....not building from the tagged 1.7.1 release | 16:42 |
lpapp | bluelightning: 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 IRC | 16:45 | |
bluelightning | lpapp: 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.py | 16:46 |
*** manuel__ <manuel__!~manuel@209.6.175.242> has joined #yocto | 16:46 | |
lpapp | do you know which command exactly it runs underneath or is that something to be figured out yet? | 16:48 |
bluelightning | in 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 #yocto | 16:50 | |
*** Levi <Levi!vlevidas@nat/intel/x-slroxyukywwmxqde> has joined #yocto | 16:50 | |
lpapp | perhaps I should run that manually? | 16:52 |
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-58-76.ip43.fastwebnet.it> has quit IRC | 16: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/250 | 16:58 | |
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-58-76.ip43.fastwebnet.it> has joined #yocto | 16:58 | |
bluelightning | you could certainly try | 16:58 |
lpapp | empty output | 16:59 |
*** Aethenelle_ <Aethenelle_!~Aethenell@199.15.128.75> has joined #yocto | 16:59 | |
lpapp | return code is zero, which indicates success | 16:59 |
lpapp | so what is Yocto's issue? | 16:59 |
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC | 17:00 | |
*** Aethenelle_ is now known as Aethenelle | 17:00 | |
lpapp | I guess I will need to understand how exactly Fetch works? | 17:01 |
bluelightning | have a look at the git fetcher, specifically the bit that's actually doing the ls-remote | 17:05 |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 17:07 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 17:07 | |
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 17:08 | |
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 17:11 | |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 17:12 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 17: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/247 | 17:17 | |
*** belen2 <belen2!Adium@nat/intel/x-pevlgevzpjskfshz> has joined #yocto | 17: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/255 | 17:19 | |
*** belen1 <belen1!Adium@nat/intel/x-qnffndtmgebuskkc> has quit IRC | 17: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/253 | 17:27 | |
*** vicky <vicky!~androirc@106.213.105.207> has joined #yocto | 17:29 | |
*** vicky is now known as Guest58084 | 17:29 | |
Guest58084 | Is there any way to keep two version of shared library in filesystem using yocto | 17:31 |
Guest58084 | When using package revision only one library which is updated will present in fs. | 17:33 |
Guest58084 | But i wanna keep both old and new libs in fs | 17:33 |
Guest58084 | Any ideas? | 17:33 |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto | 17:36 | |
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has quit IRC | 17:36 | |
bluelightning | Guest58084: you'd need two separately named recipes producing packages that did not install conflicting files in order to achieve that | 17:36 |
Guest58084 | Thanks. But the old lib i am not going to update. Only the new lib is get update in git source. | 17:40 |
Guest58084 | I 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 #yocto | 17:41 | |
bluelightning | sure, but you still need two recipes producing separate packages for that | 17:43 |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 17:44 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 17:45 | |
*** tlwoerner <tlwoerner!~trevor@unaffiliated/tlwoerner> has quit IRC | 17:47 | |
*** belen2 <belen2!Adium@nat/intel/x-pevlgevzpjskfshz> has quit IRC | 17:48 | |
lpapp | bluelightning: well, perhaps if the command returns empty output for you, you could print out the output variable in the git.py function? | 17:50 |
lpapp | to 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 IRC | 17:51 | |
lpapp | this line: output = runfetchcmd(cmd, d, True) | 17:51 |
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has joined #yocto | 17:52 | |
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has left #yocto | 17:54 | |
*** smustafa <smustafa!~mustafa@110.93.212.98> has quit IRC | 17:54 | |
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has joined #yocto | 17: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/256 | 18:00 | |
lpapp | bluelightning: 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 #yocto | 18:09 | |
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.75> has quit IRC | 18:09 | |
*** Aethenelle_ is now known as Aethenelle | 18:09 | |
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has quit IRC | 18:13 | |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 18:13 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 18:14 | |
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC | 18:20 | |
lpapp | bluelightning: it makes me think that you do not get the same cmd in the code as I do. | 18:20 |
lpapp | as my command returns empty for everyone that I talked to. | 18:20 |
lpapp | would it be possible for you to print out your command? | 18:21 |
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has joined #yocto | 18:21 | |
bluelightning | lpapp: ok, so finally I just found that the git URL was removed from CONNECTIVITY_CHECK_URIS back in 2012 | 18:22 |
lpapp | but daisy was coming out later, no? | 18:23 |
bluelightning | yeah | 18:23 |
lpapp | so I do not get the issue then. | 18:24 |
bluelightning | did you by chance copy an older poky.conf and then modify it, hence you have the old value? | 18:24 |
lpapp | yes, from the dylan times. | 18:24 |
lpapp | but even that was released only two years ago | 18:25 |
lpapp | I wonder if it is an inheritage from our early denzil variant. | 18:25 |
bluelightning | most likely | 18:25 |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 18:25 | |
lpapp | it seems that we need to update the config at each release based on how poky proceeds. | 18:25 |
lpapp | yeah, I am unsure because I thought that I redid this for dylan. | 18:26 |
lpapp | not using any of denzil during the migration. | 18:26 |
bluelightning | well, I wouldn't necessarily say that, if you follow the migration guide that ought to be enough | 18:26 |
bluelightning | in 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 noticed | 18:26 |
lpapp | was this mentioned in the migration guide? | 18:26 |
bluelightning | no, see above | 18:27 |
lpapp | hmm | 18:27 |
bluelightning | I strongly suspect this is a bug rather than something that needs to be worked around | 18:27 |
bluelightning | the key is probably the rev= | 18:27 |
lpapp | oh? | 18:27 |
bluelightning | I don't think that's commonly used in normal usages of the git fetcher (i.e. SRC_URI within recipes) | 18:28 |
lpapp | ok, well, would you like to see another report? And as for the time being, I guess I could just remove that url. | 18:29 |
bluelightning | if you don't mind filing it, sure | 18:31 |
*** seebs_ <seebs_!~seebs@74.122.98.108> has joined #yocto | 18:31 | |
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 18:31 | |
bluelightning | though if you do it would be worth adding a clarifying comment to the earlier bug that the actual issue is covered by the new one | 18:31 |
lpapp | I think it is still useful to print the exceptions as a separate issue. | 18:32 |
*** adelcast1 <adelcast1!~adelcast@130.164.62.224> has joined #yocto | 18:33 | |
bluelightning | yeah 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 |
lpapp | ok, hmm, now I am getting this >_< https://paste.kde.org/pqcvlfle5 | 18:36 |
bluelightning | have you done anything to that recipe? | 18:40 |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 18:40 | |
lpapp | nothing | 18:40 |
lpapp | I copied meta over from the poky daisy release into our repository. | 18:41 |
lpapp | so it oughta be verbatim. | 18:41 |
lpapp | but I can paste the content just in case if you like. | 18:41 |
bluelightning | it's probably old... that is covered in the migration guide btw (bb.which -> bb.utils.which) | 18:41 |
bluelightning | whereever you have that, that is | 18:41 |
lpapp | strange. | 18:42 |
lpapp | I thought the meta layer in daisy was supposed to just work? | 18:42 |
bluelightning | I guarantee that reference was not part of the daisy metadata, it must come from something you have left over | 18:43 |
lpapp | where exactly? How can I pin that down? | 18:43 |
*** aehs291 <aehs291!aehernan@nat/intel/x-sbgoqmsuprzppwvy> has joined #yocto | 18:43 | |
bluelightning | grep for it? | 18:43 |
*** aehs29 <aehs29!~aehernan@134.134.139.76> has quit IRC | 18:43 | |
lpapp | where can I find the migration guide? https://www.yoctoproject.org/downloads/core/daisy161 | 18:44 |
lpapp | I cannot seem to find the YRM in there. | 18:44 |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 18:44 | |
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto | 18:45 | |
acidfu | hello ! 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 |
lpapp | http://www.yoctoproject.org/docs/1.6.1/mega-manual/mega-manual.html | 18:47 |
lpapp | nvm, I have just looked for the word "migration" in the mega manual. | 18:47 |
bluelightning | http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#migration | 18:49 |
bluelightning | acidfu: ${WORKDIR}/git | 18:49 |
bluelightning | at least, that's where it's finally cloned to | 18:50 |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 18:53 | |
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 18:55 | |
acidfu | ok great ! | 18:57 |
*** deception <deception!~deception@unaffiliated/deception> has quit IRC | 18:59 | |
*** sarahsharp <sarahsharp!~sarah@134.134.137.73> has quit IRC | 18:59 | |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-mkfrpqidxyulaste> has joined #yocto | 19:00 | |
*** deception <deception!~deception@unaffiliated/deception> has joined #yocto | 19:01 | |
*** aehs291 <aehs291!aehernan@nat/intel/x-sbgoqmsuprzppwvy> has left #yocto | 19:06 | |
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 19:08 | |
khem` | bluelightning: Is there wiki doc on how to use locked sstate practically | 19:08 |
*** seebs_ is now known as seebs | 19:09 | |
*** dmoseley <dmoseley!~dmoseley@cpe-174-96-222-251.carolina.res.rr.com> has joined #yocto | 19:09 | |
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 19:10 | |
*** CromFr <CromFr!~CromFr@146.185.162.164> has joined #yocto | 19:17 | |
*** aehs29 <aehs29!aehernan@nat/intel/x-hyggicsuyujqyajg> has joined #yocto | 19:17 | |
*** tsramos <tsramos!~tsramos@134.134.139.76> has quit IRC | 19:22 | |
*** tsramos <tsramos!~tsramos@192.55.55.37> has joined #yocto | 19:23 | |
*** aehs29 <aehs29!aehernan@nat/intel/x-hyggicsuyujqyajg> has quit IRC | 19:26 | |
*** aehs29 <aehs29!~aehernan@134.134.137.75> has joined #yocto | 19:28 | |
*** aehs29 <aehs29!~aehernan@134.134.137.75> has left #yocto | 19:29 | |
*** pohly <pohly!~pohly@p5DE8CDA6.dip0.t-ipconnect.de> has quit IRC | 19:29 | |
*** aehs29 <aehs29!~aehernan@134.134.137.75> has joined #yocto | 19:30 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC | 19: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 #yocto | 19:47 | |
*** khem` is now known as khem[away] | 19:49 | |
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has joined #yocto | 19:49 | |
*** khem[away] is now known as khem` | 19:50 | |
*** sjolley <sjolley!sjolley@nat/intel/x-blikxjjqlhzasifn> has quit IRC | 20:01 | |
*** grma <grma!~gruberm@chello213047201250.tirol.surfer.at> has quit IRC | 20:01 | |
*** onoffon <onoffon!~khem@unaffiliated/khem> has joined #yocto | 20:10 | |
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 20:14 | |
*** sjolley <sjolley!sjolley@nat/intel/x-bolbtnbgxmjwtexk> has joined #yocto | 20:27 | |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-mkfrpqidxyulaste> has quit IRC | 20:28 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC | 20:29 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto | 20:31 | |
*** sjolley <sjolley!sjolley@nat/intel/x-bolbtnbgxmjwtexk> has quit IRC | 20:34 | |
*** sjolley <sjolley!sjolley@nat/intel/x-cnzkoadeghmmhnoi> has joined #yocto | 20:36 | |
*** ant_home <ant_home!~ant__@host185-253-dynamic.48-82-r.retail.telecomitalia.it> has joined #yocto | 20:37 | |
*** sjolley <sjolley!sjolley@nat/intel/x-cnzkoadeghmmhnoi> has quit IRC | 20:43 | |
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has joined #yocto | 20:45 | |
*** sjolley <sjolley!sjolley@nat/intel/x-lrbzurvxjlfnipsj> has joined #yocto | 20: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/254 | 20:51 | |
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has quit IRC | 20:55 | |
ebolton | hey 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 |
ebolton | the driver is listed as the provider for virtual/opengles2, but it's not being built before Qt for some reason | 20:58 |
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has quit IRC | 20:59 | |
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC | 20: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/251 | 21:12 | |
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has quit IRC | 21:16 | |
*** sarahsharp <sarahsharp!~sarah@192.55.54.42> has joined #yocto | 21: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/254 | 21:17 | |
*** sameo <sameo!samuel@nat/intel/x-xzeejzrmhzqmkqvx> has joined #yocto | 21:17 | |
*** sarahsharp <sarahsharp!~sarah@192.55.54.42> has quit IRC | 21:23 | |
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC | 21:33 | |
otavio | pidge: I made the fido branch for meta-fsl-arm | 21:35 |
pidge | otavio, ty! | 21:35 |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-vkghdyqmbdjfythk> has joined #yocto | 21: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/256 | 21:37 | |
*** tsramos <tsramos!~tsramos@192.55.55.37> has quit IRC | 21: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/255 | 21:46 | |
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has quit IRC | 21:51 | |
*** ebolton <ebolton!~ebolton@208.93.135.69> has quit IRC | 21:54 | |
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-vkghdyqmbdjfythk> has quit IRC | 22:03 | |
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto | 22:04 | |
*** onoffon <onoffon!~khem@unaffiliated/khem> has quit IRC | 22:06 | |
*** sjolley <sjolley!sjolley@nat/intel/x-lrbzurvxjlfnipsj> has quit IRC | 22:06 | |
*** ddom <ddom!~ddom@ip-37-24-103-185.hsi14.unitymediagroup.de> has quit IRC | 22: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/254 | 22: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/259 | 22:10 | |
*** fignew <fignew!~woowoo@unaffiliated/fignew> has quit IRC | 22:13 | |
*** manuel__ <manuel__!~manuel@209.6.175.242> has quit IRC | 22:15 | |
*** ant_home <ant_home!~ant__@host185-253-dynamic.48-82-r.retail.telecomitalia.it> has quit IRC | 22:20 | |
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has joined #yocto | 22:20 | |
*** sjolley <sjolley!sjolley@nat/intel/x-loaxzgescnzmjrnx> has joined #yocto | 22: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/255 | 22:25 | |
*** wCPO <wCPO!~kristian@unaffiliated/wcpo> has quit IRC | 22:29 | |
*** sarahsharp <sarahsharp!~sarah@134.134.139.76> has quit IRC | 22:37 | |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-gcmzoxxkreowrstr> has joined #yocto | 22:38 | |
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 22:40 | |
*** anselmolsm <anselmolsm!~anselmo@192.55.54.40> has quit IRC | 22:42 | |
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC | 22: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/256 | 22: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/251 | 22:46 | |
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 22: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/256 | 23: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/251 | 23:03 | |
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto | 23:17 | |
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC | 23:17 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 23:17 | |
*** sameo <sameo!samuel@nat/intel/x-xzeejzrmhzqmkqvx> has quit IRC | 23:18 | |
*** agust <agust!~agust@pD9E2FD0A.dip0.t-ipconnect.de> has quit IRC | 23:18 | |
*** Levi <Levi!vlevidas@nat/intel/x-slroxyukywwmxqde> has quit IRC | 23:20 | |
*** sjolley <sjolley!sjolley@nat/intel/x-loaxzgescnzmjrnx> has quit IRC | 23: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/257 | 23:30 | |
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has quit IRC | 23: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/254 | 23:42 | |
*** sjolley <sjolley!sjolley@nat/intel/x-eggvpxihpmderngd> has joined #yocto | 23:51 | |
*** sarahsharp <sarahsharp!sarah@nat/intel/x-gcmzoxxkreowrstr> has quit IRC | 23: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/248 | 23: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/255 | 23:52 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!