| *** nitink <nitink!~nitink@134.134.139.76> has joined #yocto | 00:02 | |
| *** nitink <nitink!~nitink@134.134.139.76> has quit IRC | 00:44 | |
| *** nitink <nitink!~nitink@134.134.139.76> has joined #yocto | 00:44 | |
| *** nitink <nitink!~nitink@134.134.139.76> has quit IRC | 00:58 | |
| *** sameo <sameo!~samuel@192.55.54.36> has quit IRC | 00:58 | |
| *** nitink <nitink!~nitink@134.134.139.76> has joined #yocto | 01:27 | |
| *** nitink <nitink!~nitink@134.134.139.76> has quit IRC | 01:34 | |
| *** eicordob <eicordob!~erich@187.188.64.194> has joined #yocto | 01:36 | |
| *** nitink <nitink!~nitink@134.134.139.76> has joined #yocto | 01:40 | |
| *** nitink <nitink!~nitink@134.134.139.76> has quit IRC | 01:48 | |
| -YoctoAutoBuilder- build #68 of nightly-qa-pam is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/68 | 01:52 | |
| blloyd | is there an easy way to get the tasks of a recipe (linux-yocto) and the execution order of the tasks? | 01:57 |
|---|---|---|
| *** ddom <ddom!~ddom@5.146.225.40> has quit IRC | 02:06 | |
| *** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC | 02:18 | |
| *** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto | 02:19 | |
| *** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC | 02:34 | |
| *** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto | 02:37 | |
| *** ddom <ddom!~ddom@5.146.225.40> has joined #yocto | 02:37 | |
| *** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC | 02:39 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 02:40 | |
| *** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto | 02:41 | |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 02:43 | |
| *** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC | 02:46 | |
| *** hsychla_ <hsychla_!~hsychla@pd95c9392.dip0.t-ipconnect.de> has joined #yocto | 03:00 | |
| *** Jefro <Jefro!~jefro@ip-64-134-236-180.public.wayport.net> has quit IRC | 03:03 | |
| *** hsychla__ <hsychla__!~hsychla@pd95c9392.dip0.t-ipconnect.de> has quit IRC | 03:04 | |
| *** victhor__ <victhor__!~victhor@177.158.99.146> has quit IRC | 03:17 | |
| *** Nilesh_ <Nilesh_!~minda@61.246.136.195> has joined #yocto | 03:28 | |
| -YoctoAutoBuilder- build #68 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/68 | 03:30 | |
| *** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 03:34 | |
| *** ddom <ddom!~ddom@5.146.225.40> has quit IRC | 03:37 | |
| *** blloyd <blloyd!~blloyd@dynamic30-98-142-75.dobsonteleco.com> has quit IRC | 03:49 | |
| -YoctoAutoBuilder- build #66 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/66 | 04:04 | |
| *** Jefro <Jefro!~jefro@ip-64-134-236-180.public.wayport.net> has joined #yocto | 04:06 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 04:18 | |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 04:21 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 04:26 | |
| *** e8johan <e8johan!~quassel@83.218.80.242> has joined #yocto | 04:31 | |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 04:32 | |
| -YoctoAutoBuilder- build #66 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/66 | 04:40 | |
| *** g1zer0 <g1zer0!~g1zer0@adsl-ull-58-195.46-151.net24.it> has joined #yocto | 04:51 | |
| *** eicordob <eicordob!~erich@187.188.64.194> has quit IRC | 04:55 | |
| -YoctoAutoBuilder- build #66 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/66 | 05:02 | |
| *** g1zer0 <g1zer0!~g1zer0@adsl-ull-58-195.46-151.net24.it> has quit IRC | 05:27 | |
| *** zecke <zecke!~ich@91.66.224.184> has joined #yocto | 05:32 | |
| *** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto | 05:37 | |
| -YoctoAutoBuilder- build #66 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/66 | 05:49 | |
| *** Jefro <Jefro!~jefro@ip-64-134-236-180.public.wayport.net> has quit IRC | 05:54 | |
| *** AndersD <AndersD!~anders@81-232-163-241-no29.business.telia.com> has joined #yocto | 05:57 | |
| *** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has joined #yocto | 06:05 | |
| *** agust <agust!~agust@p4FDE648D.dip0.t-ipconnect.de> has joined #yocto | 06:10 | |
| *** pohly <pohly!~pohly@p5DE8E98D.dip0.t-ipconnect.de> has joined #yocto | 06:15 | |
| *** stiandre <stiandre!~stiandre@109.247.13.242> has joined #yocto | 06:22 | |
| -YoctoAutoBuilder- build #66 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/66 | 06:24 | |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has quit IRC | 06:26 | |
| *** b00^wk <b00^wk!~dry@port-92-196-62-96.dynamic.qsc.de> has joined #yocto | 06:31 | |
| b00^wk | hello, how do I install that graphical tool that the app builder image uses ? | 06:32 |
| b00^wk | Hob, or Hub | 06:32 |
| b00^wk | for generating images | 06:32 |
| LetoThe2nd | um... bitbake hob? | 06:33 |
| b00^wk | yea i think so | 06:34 |
| b00^wk | also, what does "sato" mean? | 06:34 |
| b00^wk | if i don't have hob, how do I get a list of possible image configurations ? | 06:34 |
| b00^wk | like , core-image-sato/minimal, etc ... | 06:34 |
| LetoThe2nd | sato is just the name of a generic grahical environment for demo/testing purposes. | 06:35 |
| b00^wk | graphical environment inside the image ? | 06:35 |
| LetoThe2nd | you can for example run a find -iname "*-image-*" through your layers (assuming all image recipes have been named properly) | 06:35 |
| LetoThe2nd | yes, sato is a package group that goes *into* the iamge | 06:36 |
| b00^wk | LetoThe2nd, i've git 'ed it all as in quick start, and modified nothing, so | 06:36 |
| b00^wk | find should work | 06:36 |
| b00^wk | i guess | 06:36 |
| LetoThe2nd | or grep for "image.bbclass" | 06:36 |
| b00^wk | ok | 06:36 |
| b00^wk | if i add dev tools, does bitbake create two images ? | 06:37 |
| LetoThe2nd | no. | 06:37 |
| b00^wk | i want one for target, one for dev | 06:37 |
| LetoThe2nd | bitbake creates what you tell it to do | 06:37 |
| b00^wk | so obviously compiler must not go to target | 06:37 |
| LetoThe2nd | so you have to make two image recipes, and tell bitbake to tell each of them seperately | 06:38 |
| b00^wk | LetoThe2nd, but with Hub its probably easy quick config or not .. ? | 06:38 |
| LetoThe2nd | a) its called hob b) no idea, i don't use it | 06:38 |
| b00^wk | Ok, Hob :) | 06:38 |
| LetoThe2nd | the standard way is that you create your product image, and then a second image that extends it for demo purposes, e.g. depends on it. | 06:39 |
| LetoThe2nd | s/demo/development/ | 06:39 |
| b00^wk | I see | 06:39 |
| b00^wk | if i would to draw it, it would be [ general big image with tools [ target image] ] . so target is a subset of general bit one :) . So i would start with the bigger one. | 06:40 |
| b00^wk | LetoThe2nd, is it possible to generate two images same time, with two recipes ? | 06:41 |
| *** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 06:41 | |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 06:41 | |
| LetoThe2nd | its easier the other way round, because if you start with the bigger one you eventually have to tear apart a long list afterwards | 06:41 |
| b00^wk | LetoThe2nd, yea, ok | 06:42 |
| LetoThe2nd | (at least from my experience) | 06:42 |
| * LetoThe2nd is gone for a sec | 06:42 | |
| b00^wk | LetoThe2nd, as long as I back up original 'minimal' setup | 06:42 |
| *** [Sno] <[Sno]!~Sno]@p578b540c.dip0.t-ipconnect.de> has quit IRC | 06:55 | |
| LetoThe2nd | b00^wk: just have a look at the meta/recipes-core/images/core-image-minimal{.bb,-dev.bb} | 06:57 |
| LetoThe2nd | b00^wk: they give a good idea of how a dev recipe extends the base/product image for development purposes | 06:58 |
| b00^wk | LetoThe2nd, yea, the minimal is where i thought, i start. i didn't know that extends anything, when i tried it it just had busybox in it | 06:58 |
| LetoThe2nd | b00^wk: the -dev extends the minimal | 06:58 |
| LetoThe2nd | so you can see the general mechanism | 06:59 |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-qcxxwllziuxqsfab> has joined #yocto | 07:01 | |
| *** jbrianceau_away is now known as jbrianceau | 07:02 | |
| *** olani` <olani`!user@nat/axis/x-gamdbqyyxcotkskc> has quit IRC | 07:03 | |
| *** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC | 07:05 | |
| *** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto | 07:06 | |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has joined #yocto | 07:09 | |
| *** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto | 07:10 | |
| *** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC | 07:10 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 07:10 | |
| *** mckoan|away is now known as mckoan | 07:12 | |
| mckoan | good morning | 07:13 |
| *** sameo <sameo!~samuel@192.55.54.40> has joined #yocto | 07:13 | |
| b00^wk | Ah, so there is a dev already for core-minimal ? | 07:13 |
| b00^wk | me check | 07:13 |
| bluelightning | morning all | 07:14 |
| LetoThe2nd | mourns too (UMT) | 07:14 |
| *** fabo <fabo!~fabo@linaro/fabo> has quit IRC | 07:18 | |
| *** seiron <seiron!~jaborek@dslb-188-109-218-153.188.109.pools.vodafone-ip.de> has joined #yocto | 07:20 | |
| *** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto | 07:24 | |
| *** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 07:35 | |
| *** florian_kc is now known as florian | 07:35 | |
| *** seiron <seiron!~jaborek@dslb-188-109-218-153.188.109.pools.vodafone-ip.de> has quit IRC | 07:51 | |
| -YoctoAutoBuilder- build #67 of nightly-rpm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/67 | 07:57 | |
| *** vignatti_ is now known as vignatti | 08:00 | |
| *** melonipoika <melonipoika!~quassel@91-158-65-146.elisa-laajakaista.fi> has joined #yocto | 08:01 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 08:10 | |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has quit IRC | 08:14 | |
| pev | Hey all, anyone seen an issue building where GCC has an internal segfault? This is building an OMAP2 board under 1.5... | 08:47 |
| *** phantoxe <phantoxe!~destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 08:58 | |
| *** dse <dse!~d.s.e@2001:a60:1468:d601:c924:9137:a0dc:bbea> has joined #yocto | 08:59 | |
| *** belen <belen!Adium@nat/intel/x-wjhihmhmvwekjflt> has joined #yocto | 09:03 | |
| *** pev <pev!~pev@2.31.101.4> has left #yocto | 09:11 | |
| *** pev <pev!~pev@2.31.101.4> has joined #yocto | 09:20 | |
| pev | Hm, found it. GCC needs https://gcc.gnu.org/viewcvs/gcc/branches/gcc-4_7-branch/gcc/ira-int.h?view=patch&r1=191605&r2=191604&pathrev=191605 for it not to bork. Guessing this is an ubuntu 14.04 thing... | 09:21 |
| pev | For reference / google, the error it kicked up was "../../../../libgcc/../gcc/libgcc2.c:72:1: internal compiler error: Segmentation fault" | 09:22 |
| *** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 09:23 | |
| *** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto | 09:27 | |
| *** belen <belen!Adium@nat/intel/x-wjhihmhmvwekjflt> has quit IRC | 09:32 | |
| *** belen <belen!Adium@nat/intel/x-clblzjmzuzufmbgk> has joined #yocto | 09:59 | |
| *** belen <belen!Adium@nat/intel/x-clblzjmzuzufmbgk> has quit IRC | 10:03 | |
| *** jackmitchell <jackmitchell!~Thunderbi@cbnluk-gw0.cambridgebroadband.com> has quit IRC | 10:04 | |
| *** belen <belen!~Adium@192.198.151.36> has joined #yocto | 10:09 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 10:10 | |
| *** jackmitchell <jackmitchell!~Thunderbi@cbnluk-gw0.cambridgebroadband.com> has joined #yocto | 10:11 | |
| *** Crofton|work <Crofton|work!~balister@pool-108-44-87-238.ronkva.east.verizon.net> has joined #yocto | 10:18 | |
| *** Nilesh_ <Nilesh_!~minda@61.246.136.195> has quit IRC | 10:20 | |
| *** frsc <frsc!~frsc@host-89-242-133-32.as13285.net> has joined #yocto | 10:27 | |
| *** [Sno] <[Sno]!~Sno]@ip150.99.69.80.in-addr.arpa> has joined #yocto | 10:30 | |
| *** frsc1 <frsc1!~frsc@host-2-99-139-203.as13285.net> has joined #yocto | 10:31 | |
| *** frsc <frsc!~frsc@host-89-242-133-32.as13285.net> has quit IRC | 10:33 | |
| *** tmpsantos <tmpsantos!~tmpsantos@a88-115-214-114.elisa-laajakaista.fi> has joined #yocto | 10:35 | |
| *** Nilesh_ <Nilesh_!~minda@61.246.136.195> has joined #yocto | 10:35 | |
| *** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has quit IRC | 10:40 | |
| *** blitz00 <blitz00!~stefans@192.198.151.44> has joined #yocto | 10:45 | |
| *** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto | 10:45 | |
| *** hsychla <hsychla!~hsychla@77-64-175-89.dynamic.primacom.net> has joined #yocto | 10:46 | |
| *** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has joined #yocto | 11:00 | |
| *** jluisn <jluisn!~quassel@187.115.172.24> has joined #yocto | 11:04 | |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has joined #yocto | 11:07 | |
| *** ddalex <ddalex!~ddalex@83.217.123.106> has quit IRC | 11:08 | |
| *** ddalex <ddalex!~ddalex@83.217.123.106> has joined #yocto | 11:10 | |
| b00^wk | can I source oe-init-build-env again ? | 11:11 |
| b00^wk | won't loose anything ? . i had to re-login | 11:11 |
| LetoThe2nd | why not, its basically jsut setting a bunch of env vars | 11:11 |
| b00^wk | i didn't check it, thought it also creates build dir | 11:12 |
| b00^wk | not sure if it wipes it clean first :) | 11:12 |
| bluelightning | nope, if the config files already exist they won't be touched | 11:12 |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has quit IRC | 11:12 | |
| *** victhor__ <victhor__!~victhor@177.158.99.146> has joined #yocto | 11:19 | |
| *** ddom <ddom!~ddom@p4FFD9663.dip0.t-ipconnect.de> has joined #yocto | 11:22 | |
| *** michaelw <michaelw!~michael@thos.me.uk> has quit IRC | 11:45 | |
| *** michaelw <michaelw!~michael@thos.me.uk> has joined #yocto | 11:51 | |
| b00^wk | al'right, qemu running first time on my non Build Appliance yocot .. | 11:52 |
| b00^wk | yocto | 11:52 |
| b00^wk | where do I modify the image size ? | 11:52 |
| b00^wk | with Hob there was a nice little menu ... | 11:53 |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has joined #yocto | 11:53 | |
| *** kbouhara <kbouhara!~kbouhara@hyperion.atermes.fr> has joined #yocto | 12:04 | |
| kbouhara | How do we include Qt when generating sdk with "bitbake my-image -c populate_sdk" ? | 12:06 |
| *** gvy <gvy!~mike@altlinux/developer/mike> has joined #yocto | 12:09 | |
| mckoan | kbouhara: does your image recipe include Qt ? | 12:10 |
| *** tomz_ <tomz_!~tomz@134.134.139.76> has quit IRC | 12:13 | |
| *** Siecje <Siecje!~Siecje@CPEbc1401239133-CMbc1401239130.cpe.net.cable.rogers.com> has joined #yocto | 12:17 | |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has quit IRC | 12:17 | |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 12:26 | |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-0319.bb.online.no> has joined #yocto | 12:27 | |
| kbouhara | mkoan: yes it does | 12:28 |
| *** tomz_ <tomz_!~tomz@134.134.139.76> has joined #yocto | 12:29 | |
| kbouhara | I have IMAGE_INSTALL += "\ packagegroup-core-qt4e" defined | 12:34 |
| *** frsc_ <frsc_!~frsc@host-2-99-139-203.as13285.net> has joined #yocto | 12:41 | |
| *** frsc1 <frsc1!~frsc@host-2-99-139-203.as13285.net> has quit IRC | 12:45 | |
| *** ntl <ntl!~ntl@99-127-49-21.lightspeed.austtx.sbcglobal.net> has quit IRC | 12:47 | |
| mckoan | kbouhara: so -c populate_sdk does the magic | 12:52 |
| *** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 12:54 | |
| *** rwoolley <rwoolley!~rwoolley@128.224.252.2> has joined #yocto | 13:08 | |
| *** olani <olani!user@nat/axis/x-amgwgtapetujspzq> has joined #yocto | 13:12 | |
| kbouhara | mkoan: no it doesn't work for me when I install the SDK and source the environment script, If I do "which qmake" it says /usr/bin/qmake not /opt/poky/... | 13:23 |
| bluelightning | just having Qt in your image won't make the SDK have the tools in it | 13:25 |
| bluelightning | try adding this to your image: TOOLCHAIN_HOST_TASK_append = " nativesdk-packagegroup-qte-toolchain-host" | 13:26 |
| kbouhara | bluelightning: ok will try it and see it does the work | 13:27 |
| xerent | what could cause kernel configuration flags to disappear in the do_kernel_configcheck step? | 13:33 |
| *** dmoseley <dmoseley!~dmoseley@cpe-174-096-222-251.carolina.res.rr.com> has joined #yocto | 13:33 | |
| xerent | the only clue I have is from the log, which points to the missing_required.txt log file, which simply says "Required value for CONFIG_FOO not in final ".config" | 13:34 |
| ant_work | you can read in the machine-config log the steps leading to it | 13:36 |
| ant_work | it is maybe reset by some other fragment/feature? | 13:37 |
| *** Crofton <Crofton!~balister@pool-108-44-87-238.ronkva.east.verizon.net> has joined #yocto | 13:37 | |
| xerent | thanks, where's the machine-config log? | 13:40 |
| ant_work | in the same dir under meta where required.txt is | 13:41 |
| *** ntl <ntl!~ntl@67-198-70-33.dyn.grandenetworks.net> has joined #yocto | 13:41 | |
| ant_work | it is -defconfig in my case | 13:41 |
| b00^wk | where do I get the (desired) max size of the target hdd image ? | 13:42 |
| ant_work | (I'm away from build machine, can't check precisely right now) | 13:42 |
| b00^wk | i found IMAGE_ROOTFS_SIZE, but don't see hdd img size | 13:42 |
| *** AndersD <AndersD!~anders@81-232-163-241-no29.business.telia.com> has quit IRC | 13:59 | |
| *** AndersD <AndersD!~anders@81-232-163-241-no29.business.telia.com> has joined #yocto | 13:59 | |
| xerent | where does the bitbake binary go, I'm looking for it. I can run it through makefiles but not from the commandline :) | 14:12 |
| xerent | or I suppose I am running bitbake somehow because I can produce images through Yocto :P | 14:13 |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 14:15 | |
| *** Nilesh_ <Nilesh_!~minda@61.246.136.195> has quit IRC | 14:15 | |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has joined #yocto | 14:15 | |
| *** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 14:16 | |
| *** stiandre <stiandre!~stiandre@109.247.13.242> has quit IRC | 14:20 | |
| xerent | found it, but | 14:21 |
| xerent | ERROR: An uncaught exception occured in runqueue, please see the failure below: | 14:22 |
| *** staylor <staylor!~staylor@S0106602ad0901f12.cg.shawcable.net> has joined #yocto | 14:22 | |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-0319.bb.online.no> has quit IRC | 14:24 | |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC | 14:28 | |
| *** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has joined #yocto | 14:33 | |
| xerent | bitbake can't open runqueue.py | 14:33 |
| bluelightning | xerent: what are you attempting to do? | 14:37 |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 14:38 | |
| *** b00^wk <b00^wk!~dry@port-92-196-62-96.dynamic.qsc.de> has quit IRC | 14:39 | |
| *** sjolley <sjolley!~sjolley@134.134.137.75> has quit IRC | 14:43 | |
| *** belen <belen!~Adium@192.198.151.36> has quit IRC | 14:43 | |
| *** [Sno] <[Sno]!~Sno]@ip150.99.69.80.in-addr.arpa> has quit IRC | 14:45 | |
| *** belen <belen!Adium@nat/intel/x-ypvszktzeuofyxkk> has joined #yocto | 14:45 | |
| *** adelcast <adelcast!~adelcast@130.164.62.224> has quit IRC | 14:48 | |
| *** munch_ <munch_!~mark@184.95.43.170> has joined #yocto | 14:50 | |
| *** munch_ is now known as Guest83425 | 14:50 | |
| *** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC | 14:51 | |
| *** sarahsharp <sarahsharp!~sarah@192.55.54.42> has joined #yocto | 14:52 | |
| *** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC | 14:54 | |
| *** belen <belen!Adium@nat/intel/x-ypvszktzeuofyxkk> has quit IRC | 14:56 | |
| *** e8johan <e8johan!~quassel@83.218.80.242> has quit IRC | 14:57 | |
| *** belen <belen!Adium@nat/intel/x-iqnyihjkpdnwqmxb> has joined #yocto | 14:59 | |
| *** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has quit IRC | 15:00 | |
| *** sjolley <sjolley!~sjolley@134.134.137.73> has joined #yocto | 15:10 | |
| *** sarahsharp <sarahsharp!~sarah@192.55.54.42> has quit IRC | 15:15 | |
| *** munch <munch!~mark@93.115.83.243> has joined #yocto | 15:25 | |
| *** Guest83425 <Guest83425!~mark@184.95.43.170> has quit IRC | 15:26 | |
| *** sarahsharp <sarahsharp!sarah@nat/intel/x-djtmcubxizlbahaz> has joined #yocto | 15:28 | |
| xerent | bitbake linux-yocto -c kernel_configcheck -f | 15:32 |
| xerent | from build folder | 15:32 |
| *** shoragan <shoragan!~shoragan@debian/developer/shoragan> has quit IRC | 15:33 | |
| bluelightning | xerent: after sourcing oe-init-build-env ? | 15:33 |
| xerent | don't know exactly, but I have built complete images using that kernel | 15:34 |
| xerent | based on linux-yocto_3.10.17.bb | 15:35 |
| *** armpit <armpit!~akuster@2601:c:9380:601:9047:eb81:1abf:5be> has joined #yocto | 15:37 | |
| bluelightning | I'm confused | 15:39 |
| xerent | so am I, but I think I know what you're getting at | 15:39 |
| xerent | and yes, I'm missing something | 15:39 |
| bluelightning | surely you know if you have run oe-init-build-env within the current shell or not? | 15:39 |
| xerent | and the answer to that question is "no" because I didn't know about it | 15:40 |
| xerent | but looking at the Makefiles I can figure out what you're talking about | 15:40 |
| xerent | OK, now I got it working, thanks | 15:42 |
| *** [Sno] <[Sno]!~Sno]@p578b540c.dip0.t-ipconnect.de> has joined #yocto | 15:44 | |
| *** ddom <ddom!~ddom@p4FFD9663.dip0.t-ipconnect.de> has quit IRC | 15:45 | |
| xerent | though it gave me no more useful information, I'm trying to find out why my "CONFIG_REGMAP=y" is set to "" but the logs are most unhelpful | 15:50 |
| ant_work | how is the final config assembled? by which fragments? | 15:57 |
| ant_work | previously you found missing_required.txt | 15:59 |
| *** belen <belen!Adium@nat/intel/x-iqnyihjkpdnwqmxb> has quit IRC | 15:59 | |
| ant_work | check in the same dir, read it all ;) | 15:59 |
| ant_work | here under 'meta' subdir are the artifacts produced by yocto kernel tools | 16:00 |
| *** mckoan is now known as mckoan|away | 16:01 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 16:02 | |
| xerent | I thought I had read it all, if I grep all the files for the config flag I only get the message that 1. it's included in the config going in, from my fragment, but 2. not included in my final .config | 16:03 |
| xerent | and inbetween, I've found no reference to the darn thing :) | 16:04 |
| *** belen <belen!Adium@nat/intel/x-qlnkyzmbcsoqwblc> has joined #yocto | 16:14 | |
| ant_work | how did you add your fragment? | 16:16 |
| xerent | from files/ folder in recipe folder I added regmap.cfg, and | 16:17 |
| xerent | in recipe .bbappend file I added SRC_URI_append_machinename = " file://regmap.cfg" | 16:17 |
| ant_work | and is your fragment processed? | 16:18 |
| kergoth | RP: any tips for diagnosing sstate reuse problems when neither bitbake -S printdiff nor bitbake-whatchanged show any delta whatsoever? | 16:18 |
| xerent | ant_work: I think so, the same thing worked fine for other configuration flags, such as when I set CONFIG_INPUt_stuff | 16:19 |
| ant_work | see, there are cdases where you might want to use an .scc and set i.e. kconf hardware yourfrag.cfg | 16:20 |
| ant_work | setting it as hardware fragment will preserve it | 16:21 |
| xerent | o_O | 16:22 |
| *** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC | 16:22 | |
| ant_work | I'm sorry but I'm away of my pc and cannot help you much | 16:22 |
| ant_work | however you should find fine examples in the manual | 16:22 |
| ant_work | (s) | 16:22 |
| xerent | I'll look for that | 16:22 |
| xerent | :) | 16:22 |
| ant_work | ...or a very comples example of mine... | 16:22 |
| ant_work | see this and its dir | 16:23 |
| ant_work | http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.10.bbappend | 16:23 |
| ant_work | the machines using feature-top.scc are fully composed by fragments | 16:24 |
| ant_work | the ones using 'defconfig' are kept unchanged | 16:24 |
| ant_work | (that was explaining it in a few words...) | 16:24 |
| *** munch <munch!~mark@93.115.83.243> has quit IRC | 16:24 | |
| *** jluisn <jluisn!~quassel@187.115.172.24> has quit IRC | 16:25 | |
| *** jluisn <jluisn!~quassel@187.115.172.24> has joined #yocto | 16:26 | |
| RP | kergoth: resort to bitbake-diffsigs ? | 16:30 |
| kergoth | hmm, yeah, might be best | 16:33 |
| *** Jefro <Jefro!~Jefro@ip-64-134-236-180.public.wayport.net> has joined #yocto | 16:34 | |
| *** victhor__ <victhor__!~victhor@177.158.99.146> has quit IRC | 16:35 | |
| *** victhor__ <victhor__!~victhor@177.41.4.157> has joined #yocto | 16:35 | |
| *** belen <belen!Adium@nat/intel/x-qlnkyzmbcsoqwblc> has quit IRC | 16:35 | |
| fray | maybe someone can help.. where [code wise] does the system compress (or create the image) from the IMAGE_ROOTFS after or part of the do_rootfs command? | 16:35 |
| *** belen <belen!Adium@nat/intel/x-gxupkgggbgbrodqj> has joined #yocto | 16:36 | |
| *** blloyd <blloyd!~blloyd@COX-66-210-177-72-static.coxinet.net> has joined #yocto | 16:39 | |
| bluelightning | fray: definitions in meta/classes/image_types.bbclass, code that reads them in meta/lib/oe/image.py | 16:39 |
| fray | I've been looking through oe/image.py and can't figure out where the connection is between the IMAGE_ROOTFS and the output.. | 16:39 |
| fray | I'm trying to make the system do this action against another directory (not IMAGE_ROOTFS) as part of the rootfs process... | 16:40 |
| fray | in the old code, [pre-python] you could do this within the IMAGE_POSTPROCESS_CMD... [still happens to work here], but I'm having to manually run the tar and such commands.. | 16:40 |
| fray | I'd rather re-use what teh system is already doing | 16:40 |
| bluelightning | fray: see _get_imagecmds | 16:41 |
| bluelightning | that grabs the values defined in image_types.bbclass | 16:42 |
| fray | so is that the for fstype_group in fstype_groups? | 16:42 |
| fray | ok.. and then it just uses the IMAGE_ROOTFS as passed into the function.. | 16:44 |
| *** darknighte <darknighte!~darknight@darknighte.xen.prgmr.com> has joined #yocto | 16:44 | |
| RP | kergoth: when you do figure it out, can you document a test case as a bug please? Makes it great to try and improve printdiff | 16:45 |
| *** darknighte is now known as Guest38870 | 16:45 | |
| fray | ok.. I think I'm getting it now.. so the 'create' in image.py, gets back a set of image cmd groups, which can then be run in paralle (provided it's allowed).. and the commands themsevles know how to read the IMAGE_ROOTFS, so it's never passed through the functions.. | 16:45 |
| fray | ok | 16:45 |
| *** Guest38870 <Guest38870!~darknight@darknighte.xen.prgmr.com> has quit IRC | 16:45 | |
| bluelightning | fray: right | 16:46 |
| fray | that connection is what I was missing.. thanks | 16:46 |
| *** victhor__ <victhor__!~victhor@177.41.4.157> has quit IRC | 16:46 | |
| *** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 16:46 | |
| bluelightning | fray: you could cheat and use a copy of the datastore and set IMAGE_ROOTFS etc. to whatever you want it to be | 16:46 |
| fray | so likely the only way for me to reuse that would be t change the definition of IMAGE_ROOTFS (temporarily) and then call through at that point | 16:47 |
| *** darknighte_ <darknighte_!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto | 16:47 | |
| bluelightning | right, that's basically the same thing, except modifying a copy of the datastore is going to be less fragile | 16:47 |
| fray | thats what I'm trying to figure out now.. would I have to change self.d (temporarily) then? what I don't see is what value of 'd' is used by the bb.utils.multiprocessingpool / pool.impa | 16:47 |
| fray | 'er.. pool.imap | 16:47 |
| fray | (what I'm working on is a parallel 'debug filesystem' that only contains the associated -dbg package contents...) that way you end up with a product and 'debug' filesystem.. if you want to merge them you can debug on the target.. | 16:49 |
| fray | I have generation working (I think) | 16:49 |
| fray | [mhatle@msp-dhcp23 1.0-r0]$ du -s rootfs* | 16:49 |
| fray | 6948 rootfs | 16:49 |
| fray | 89304 rootfs-dbg | 16:49 |
| *** j6V6t <j6V6t!~jvanderpo@rrcs-24-97-209-160.nys.biz.rr.com> has left #yocto | 16:49 | |
| fray | but it's exporting them out thats tricky.. and due to us moving all of this into the image.py, I'm having to actually modify it.. there aren't any hooks to do this dynamicall | 16:49 |
| fray | y | 16:49 |
| bluelightning | fray: you would not want to set self.d, no. you'll probably have to change the structure of the code | 16:50 |
| fray | pool = bb.utils.multiprocessingpool(nproc) | 16:50 |
| fray | results = list(pool.imap(generate_image, image_cmds)) | 16:50 |
| fray | it's that part that I'm trying to figure out if I can modify in some way to pass an alternative datastore.. | 16:50 |
| fray | OR if the image_cmds were expanded earlier, if so I could do it there.. | 16:51 |
| fray | perhaps: | 16:51 |
| fray | image_cmd_groups = self._get_imagecmds() | 16:51 |
| fray | ahh.. yes they were expanded there.. I see now how | 16:52 |
| fray | but they were expanded using 'self.d' as the origin.. | 16:52 |
| fray | ok.. I think I have a plan.. allow the system to pass an alternative datastoer into the _get_imagecmds()... then I can set IMAGE_ROOTFS to whatever I want temproarily without messing with self.d | 16:53 |
| kergoth | that reminds me, it'd be lovely to implement some form of ASSUME_RPROVIDED for this, to explictly bypass certain deps without having to force bypass all dependencies. course i don tknow if all our package managers would support such a thing, or how much work it'd be.. | 16:54 |
| fray | I agree. | 16:55 |
| fray | I'm working on generating and SDK as well, and it would be nice to throw out specific target dependencies I don't care about.. | 16:55 |
| fray | i.e. I don't want bash or perl in the SDK.. :P even if glibc says it needs them | 16:55 |
| kergoth | indeed | 16:55 |
| fray | we could do that before things went to python (at least for rpm) by seeding the provides file.. | 16:55 |
| *** phantoxe <phantoxe!~destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 16:56 | |
| kergoth | we hit the perl one a while back trying to add git-submodule to the buildtools-tarball (needs git-perltools) | 16:56 |
| * kergoth nods | 16:56 | |
| kergoth | i figured opkg would be similar, hack the status if necessary | 16:56 |
| fray | (my hack, for now, is to disable all of the automatic dep generation during packaging for the special SDK builds.. but that isn't exactly 'general purpose') | 16:56 |
| *** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC | 16:57 | |
| *** ntl <ntl!~ntl@67-198-70-33.dyn.grandenetworks.net> has quit IRC | 16:58 | |
| kergoth | RP: I'm hitting a situation trying to share sstate between two hosts. All the signatures are the same, only the native filenames are differnet due to the different nativelsbstring, so the native setscenes can't be run. It seems it ends up rebuilding certain target recipes from scratch after the natives get built from scratch, even though all the signatures, native and target, are the same. Any ideas on that? | 16:59 |
| *** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto | 17:01 | |
| *** jonmasters <jonmasters!~jcm@edison.jonmasters.org> has quit IRC | 17:01 | |
| kergoth | Of course bitbake -S and bitbake-whatchanged can't tell me why anything is building from scratch, since the signatures haven't changed. and afaik there's no detailed log of bitbake's decisions wrt sstate usage | 17:03 |
| *** Jefro1 <Jefro1!~jefro@ip-64-134-236-180.public.wayport.net> has joined #yocto | 17:04 | |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 17:06 | |
| *** Jefro <Jefro!~Jefro@ip-64-134-236-180.public.wayport.net> has quit IRC | 17:07 | |
| RP | kergoth: bitbake -DDDv does log some of its decisions about sstate iirc, at least what it looks for and did/didn't find. If the sigs are the same, it has to be something in the lsbstring matching part? | 17:11 |
| kergoth | RP: i know the nativelsbstring doesn't match, these are two different distros. but there's no reason it couldn't reuse the target stuff, it used to, but it doesn't seem to now. Presumably after it rebuilt the natives it wanted to rebuild the bits that depended on them, but it shouldn't need to, since the checksums *and* filenames for the target sstates match up, all thats changed is some of its dependencies were built from scratch. I'll do some -DDDv | 17:15 |
| kergoth | builds and see if I can pick up anything useful. thanks for the assistance | 17:15 |
| *** sameo <sameo!~samuel@192.55.54.40> has quit IRC | 17:18 | |
| *** ntl <ntl!~ntl@99-127-49-21.lightspeed.austtx.sbcglobal.net> has joined #yocto | 17:25 | |
| *** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 17:33 | |
| *** gvy <gvy!~mike@altlinux/developer/mike> has quit IRC | 17:41 | |
| *** sgw_ <sgw_!~sgw@c-67-171-230-40.hsd1.wa.comcast.net> has quit IRC | 17:42 | |
| *** Jefro1 <Jefro1!~jefro@ip-64-134-236-180.public.wayport.net> has quit IRC | 17:45 | |
| *** sgw_ <sgw_!~sgw@c-67-171-230-40.hsd1.wa.comcast.net> has joined #yocto | 17:45 | |
| *** sarahsharp <sarahsharp!sarah@nat/intel/x-djtmcubxizlbahaz> has quit IRC | 17:46 | |
| *** Jefro <Jefro!~jefro@ip-64-134-236-180.public.wayport.net> has joined #yocto | 17:48 | |
| *** Jefro <Jefro!~jefro@ip-64-134-236-180.public.wayport.net> has quit IRC | 17:51 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 18:01 | |
| *** sarahsharp <sarahsharp!~sarah@134.134.139.70> has joined #yocto | 18:09 | |
| *** Jefro <Jefro!~jefro@ip-64-134-236-180.public.wayport.net> has joined #yocto | 18:09 | |
| *** fusman <fusman!~fahad@39.55.167.110> has joined #yocto | 18:09 | |
| *** behanw <behanw!~behanw@S0106dc9fdb80cffd.gv.shawcable.net> has quit IRC | 18:09 | |
| blloyd | I'm trying to get a better understanding of linux-yocto kernel configuration. I had 3.4 working nicely for two CPUs. A vortex86 and a Geode LX2. But moving forward to 3.14 is driving me crazy. How do I figure out what the baseline is on which the fragments will be applied? More apptly, how can I choose which branch to base off of? I used to use the atom-pc which was almost exactly what both of those needed. No other patches nee | 18:15 |
| blloyd | ded and only a very small handful of changes via .scc | 18:15 |
| *** belen <belen!Adium@nat/intel/x-gxupkgggbgbrodqj> has quit IRC | 18:18 | |
| kergoth | we should really add a bitbake argument to exit after the runqueue is prepared and the sstates were fetched / checked | 18:29 |
| kergoth | ala -p | 18:29 |
| *** behanw <behanw!~behanw@S0106dc9fdb80cffd.gv.shawcable.net> has joined #yocto | 18:32 | |
| *** Jefro <Jefro!~jefro@ip-64-134-236-180.public.wayport.net> has quit IRC | 18:40 | |
| *** jbrianceau <jbrianceau!uid10952@gateway/web/irccloud.com/x-qcxxwllziuxqsfab> has quit IRC | 18:52 | |
| *** fusman <fusman!~fahad@39.55.167.110> has quit IRC | 18:53 | |
| fray | Exception: File "/home/mhatle/git/oss/poky/meta/lib/oe/rootfs.py", line 90 | 18:55 |
| fray | os.rename(self.image_rootfs + '-orig', self.image_rootfs) | 18:55 |
| fray | ^ | 18:55 |
| fray | SyntaxError: invalid syntax | 18:55 |
| fray | any idea what is causing that (yes thats a line I wrote).. | 18:55 |
| fray | but I'm getting zero context as to why the system things it's 'invalid' | 18:55 |
| fray | d'oh.. missing closing ) about 5 lines up | 18:56 |
| *** g1zer0 <g1zer0!~g1zer0@adsl-ull-211-56.48-151.net24.it> has joined #yocto | 19:04 | |
| *** tmpsantos <tmpsantos!~tmpsantos@a88-115-214-114.elisa-laajakaista.fi> has quit IRC | 19:18 | |
| *** Siecje <Siecje!~Siecje@CPEbc1401239133-CMbc1401239130.cpe.net.cable.rogers.com> has left #yocto | 19:19 | |
| fray | kergoth: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=mhatle/debugfs&id=232acd506ec2edd5c12314ef10acb5316bd10602 | 19:27 |
| fray | thats my -second- pass at the change.. | 19:27 |
| *** blitz00 <blitz00!~stefans@2a02:2f0a:8012:700:5d51:4da8:1886:2ed8> has joined #yocto | 19:28 | |
| *** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto | 19:28 | |
| *** g1zer0 <g1zer0!~g1zer0@adsl-ull-211-56.48-151.net24.it> has quit IRC | 19:31 | |
| fray | something must still not be quite right, since the ext3 image didn't get generated.. but the tar.bz2 did | 19:31 |
| *** belen <belen!~Adium@190.227.187.81.in-addr.arpa> has joined #yocto | 19:34 | |
| *** sarahsharp <sarahsharp!~sarah@134.134.139.70> has quit IRC | 19:42 | |
| *** sarahsharp <sarahsharp!~sarah@134.134.139.76> has joined #yocto | 19:50 | |
| *** armpit <armpit!~akuster@2601:c:9380:601:9047:eb81:1abf:5be> has left #yocto | 19:53 | |
| *** belen <belen!~Adium@190.227.187.81.in-addr.arpa> has quit IRC | 19:59 | |
| RP | kergoth: thinking a bit more about it, if the natives were not available, I can see how it may then want to rebuild the targets :/ | 20:03 |
| RP | kergoth: there is probably some fine tuning of the dependencies there that could be needed | 20:04 |
| *** sullical <sullical!sullical@nat/intel/x-agpvswosrvdnoqly> has joined #yocto | 20:12 | |
| *** staylor <staylor!~staylor@S0106602ad0901f12.cg.shawcable.net> has quit IRC | 20:12 | |
| *** Siecje <Siecje!~Siecje@CPEbc1401239133-CMbc1401239130.cpe.net.cable.rogers.com> has joined #yocto | 20:18 | |
| blloyd | I'm trying to get a better understanding of linux-yocto kernel configuration. I had 3.4 working nicely for two CPUs. A vortex86 and a Geode LX2. But moving forward to 3.14 is driving me crazy. How do I figure out what the baseline is on which the fragments will be applied? More apptly, how can I choose which branch to base off of? I used to use the atom-pc which was almost exactly what both of those needed. | 20:26 |
| rburton | blloyd: genericx86 is the new atom-pc, fwiw | 20:27 |
| rburton | oh but those machines are probably too special for that bsp | 20:27 |
| *** pohly <pohly!~pohly@p5DE8E98D.dip0.t-ipconnect.de> has quit IRC | 20:27 | |
| *** hbruce_ <hbruce_!hbruce@nat/intel/x-ewxhgfatfliozfvz> has quit IRC | 20:28 | |
| blloyd | rburton: thanks, but figured that. However genericx86 seems to have a lot more modules turned on than I had from atom-pc baseline. So I'm trying to figure out how to pick my baseline without having to compile each one and just see what the .config looks like. | 20:44 |
| blloyd | and trying to avoid doing a defconfig, but that defconfig is looking more and more promising. | 20:45 |
| *** Jefro <Jefro!~jefro@50.250.166.177> has joined #yocto | 20:45 | |
| blloyd | I also figured better understanding of the tools is never a bad thing. I've already tried reading the code and I wasn't able to make headway on where the base config comes from. | 20:46 |
| *** Crofton|work <Crofton|work!~balister@pool-108-44-87-238.ronkva.east.verizon.net> has quit IRC | 20:48 | |
| rburton | blloyd: you want to speak to bruce really, zedd when he's on here. i think i saw holiday photos on facebook though... | 20:51 |
| fray | I can't remember if he's back tomorrow or next week | 20:52 |
| blloyd | oh, well. Thanks fray. I've got several xf86 driver maintainers interested in my use of their drivers in yocto-project. One actually seems interested in using it himself if I can get the rest of the bugs worked out. | 20:53 |
| rburton | oh? | 20:55 |
| rburton | what are you doing that's awesome? | 20:55 |
| *** behanw <behanw!~behanw@S0106dc9fdb80cffd.gv.shawcable.net> has quit IRC | 20:56 | |
| rburton | fray: did you see the "package_manager.py: ignore failed smart install with --attempt" mail you got cc'd on (oe-core) | 20:56 |
| *** gizero <gizero!~g1zer0@adsl-ull-211-56.48-151.net24.it> has joined #yocto | 20:57 | |
| *** Siecje <Siecje!~Siecje@CPEbc1401239133-CMbc1401239130.cpe.net.cable.rogers.com> has left #yocto | 20:57 | |
| *** rwoolley <rwoolley!~rwoolley@128.224.252.2> has quit IRC | 21:05 | |
| *** Jefro <Jefro!~jefro@50.250.166.177> has quit IRC | 21:07 | |
| *** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC | 21:07 | |
| *** jluisn <jluisn!~quassel@187.115.172.24> has quit IRC | 21:08 | |
| *** behanw <behanw!~behanw@S0106dc9fdb80cffd.gv.shawcable.net> has joined #yocto | 21:10 | |
| *** sameo <sameo!~samuel@192.55.54.42> has joined #yocto | 21:15 | |
| kergoth | fray: looks promising, quite a bit cleaner than our approach. needs a default IMAGE_FSTYPES_DEBUGFS definition, but that's minor. it's slightly odd that we pass in the -dbg suffix into _get_imagecmds, but had to append the suffix to the various vars ourselves before calling it anyway. seems like either _get_imagecmds should handle it, or it should be handled by the caller, rather than both, but that's debatable. | 21:18 |
| *** gizero <gizero!~g1zer0@adsl-ull-211-56.48-151.net24.it> has quit IRC | 21:23 | |
| *** Crofton|work <Crofton|work!~balister@pool-108-44-87-238.ronkva.east.verizon.net> has joined #yocto | 21:28 | |
| *** Jefro <Jefro!~jefro@50.250.166.177> has joined #yocto | 21:28 | |
| *** Jefro1 <Jefro1!~jefro@207.183.242.99> has joined #yocto | 21:29 | |
| kergoth | RP: indeed, https://gist.github.com/kergoth/3cd1c0cd6862882b3b58 seems to show this behavior. not ideal, means there's no reuse at all between host distros. too late in the cycle to do much about it, of course. i'll open a bug for post-1.7 | 21:29 |
| blloyd | rburton: I didn't think it was very awesome. I was kinda surprised that he was interested. However, seems Geode LX hasn't worked well with Yocto in the past. | 21:30 |
| gebreselaisi | hi guys | 21:32 |
| gebreselaisi | who should provide libasound_module_pcm_pulse.so ? | 21:32 |
| *** frsc_ <frsc_!~frsc@host-2-99-139-203.as13285.net> has quit IRC | 21:32 | |
| blloyd | anyone know if there is a package in yocto that provides the setterm program? Or if there is a better way to control things like screen blanking? | 21:32 |
| *** Jefro <Jefro!~jefro@50.250.166.177> has quit IRC | 21:33 | |
| *** RP2 <RP2!~RP@5751f4a1.skybroadband.com> has joined #yocto | 21:34 | |
| RP | kergoth: ah, this does explain it. THe trouble is it can't even unpack that sstate file without pseudo since the users may get messed up :( | 21:34 |
| kergoth | ah! that makes sense | 21:35 |
| kergoth | time to poke at uninative, methinks :) | 21:35 |
| * kergoth has that on the todo already to play with it | 21:35 | |
| RP | kergoth: well, it kind of makes sense, if it were shadow-native rather than pseudo-native but the general idea applies... | 21:35 |
| kergoth | i trimmed the log, it's both shadow and pseudo | 21:36 |
| * kergoth nods | 21:36 | |
| RP | or it were avahi:do_package which does need pseudp-native | 21:36 |
| RP | but yes, uninative is our hope here | 21:36 |
| gebreselaisi | Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so | 21:36 |
| gebreselaisi | anybody knows what package should provide that lib? | 21:36 |
| rburton | ge | 21:37 |
| rburton | whoops | 21:37 |
| rburton | gebreselaisi: is it saying it can't find that module, or that module is linking to something else that doesn't exist? | 21:37 |
| gebreselaisi | rburton, I do not have that library in my rootfs | 21:38 |
| gebreselaisi | and the rror is that from above: Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so | 21:39 |
| gebreselaisi | so I guess it means that it cannot find the module | 21:39 |
| gebreselaisi | I've googled around and apparently that should come from some alsa-plugins package | 21:39 |
| gebreselaisi | which I do not find in yocto | 21:39 |
| *** Crofton|work <Crofton|work!~balister@pool-108-44-87-238.ronkva.east.verizon.net> has quit IRC | 21:40 | |
| rburton | gebreselaisi: feel free to steal https://github.com/Guacamayo/meta-guacamayo/blob/master/meta-guacamayo/recipes-multimedia/alsa/alsa-plugins_1.0.26.bb | 21:43 |
| rburton | (hooray layers.openembedded.org) | 21:43 |
| *** sarahsharp <sarahsharp!~sarah@134.134.139.76> has quit IRC | 21:44 | |
| *** Crofton|work <Crofton|work!~balister@pool-108-44-87-238.ronkva.east.verizon.net> has joined #yocto | 21:45 | |
| gebreselaisi | rburton, thanks | 21:46 |
| *** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC | 21:47 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 21:48 | |
| JaMa|Off | RP: would it make sense to change populate-sysroot conflicts to use package_qa_handle_error function so it would be fatal QA error (by default) with option to disable it? | 21:51 |
| JaMa|Off | RP: I think part of this problem was that normal bb.warn messages are less visible than QA messages (which are also collected in qa.log) so easy to check after the build | 21:52 |
| RP | JaMa|Off: To be honest, I don't want people to turn that on off. The issues are too nasty | 21:54 |
| RP | s/on/one/ | 21:55 |
| JaMa|Off | OK, fair enough, I agree it's nasty | 21:55 |
| JaMa|Off | it's last 6 failures in world builds (after including all my pending fixes), I've sent the list earlier today | 21:56 |
| RP | JaMa|Off: if it stops there and then, the issue can usually be recovered. If you continue past that you no longer know what in the sysroot is corrupted | 21:56 |
| JaMa|Off | the problem is that if I go with PNBLACKLIST (to blacklist one from the conflicting duo) then I'm blacklisting something which alone is fine (unless you're building the other recipe as well) | 21:57 |
| JaMa|Off | e.g. Paul won't be happy if I blacklist modphp, just because it conflicts with php and vice-versa | 21:58 |
| *** Jefro1 <Jefro1!~jefro@207.183.242.99> has quit IRC | 21:58 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
| *** Jefro <Jefro!~jefro@50.250.166.177> has joined #yocto | 22:03 | |
| *** zecke <zecke!~ich@91.66.224.184> has quit IRC | 22:04 | |
| *** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto | 22:07 | |
| *** sarahsharp <sarahsharp!~sarah@134.134.139.70> has joined #yocto | 22:09 | |
| rburton | JaMa|Off: blacklisting both php and modphp is clearly the answer, and improves the world | 22:19 |
| JaMa|Off | should I send patch for oe-core to blacklist xz and lzma as well? :) | 22:21 |
| *** agust <agust!~agust@p4FDE648D.dip0.t-ipconnect.de> has quit IRC | 22:39 | |
| *** sjolley <sjolley!~sjolley@134.134.137.73> has quit IRC | 22:47 | |
| *** hsychla <hsychla!~hsychla@77-64-175-89.dynamic.primacom.net> has quit IRC | 22:57 | |
| *** dse <dse!~d.s.e@2001:a60:1468:d601:c924:9137:a0dc:bbea> has quit IRC | 23:02 | |
| *** RP2 <RP2!~RP@5751f4a1.skybroadband.com> has quit IRC | 23:09 | |
| *** tomz_ <tomz_!~tomz@134.134.139.76> has quit IRC | 23:11 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-gvusmqjnpdsvyvsi> has joined #yocto | 23:14 | |
| *** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC | 23:42 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!