| -YoctoAutoBuilder- build #303 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x32/builds/303 | 00:13 | |
| kergoth | hmmmmm | 00:17 |
|---|---|---|
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 00:21 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 00:21 | |
| *** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC | 00:23 | |
| *** drasko_ <drasko_!~drasko@seg75-7-88-164-183-180.fbx.proxad.net> has quit IRC | 00:24 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 00:24 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 00:26 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 00:37 | |
| -YoctoAutoBuilder- build #294 of nightly-non-gpl3 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-non-gpl3/builds/294 | 00:42 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 00:44 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 00:47 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 00:49 | |
| *** scot_ <scot_!~scot@130.164.62.183> has quit IRC | 00:49 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has joined #yocto | 00:50 | |
| *** vmeson <vmeson!~quassel@128.224.252.2> has quit IRC | 00:50 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 00:53 | |
| *** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC | 00:59 | |
| *** Jefro <Jefro!~jefro@205.154.64.43> has quit IRC | 01:00 | |
| *** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto | 01:00 | |
| -YoctoAutoBuilder- build #297 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-lsb/builds/297 | 01:00 | |
| *** vmeson <vmeson!~quassel@128.224.252.2> has joined #yocto | 01:00 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 01:01 | |
| *** _alex_kag_ <_alex_kag_!~alex_kag@178.126.178.164> has quit IRC | 01:02 | |
| -YoctoAutoBuilder- build #150 of minnow is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow/builds/150 | 01:16 | |
| *** ausjke <ausjke!~xxiao@72.14.179.126> has quit IRC | 01:20 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 01:38 | |
| *** ka6sox is now known as zz_ka6sox | 01:39 | |
| *** notinreallife <notinreallife!~notinreal@108-91-142-36.lightspeed.wlfrct.sbcglobal.net> has quit IRC | 01:40 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 01:44 | |
| *** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto | 01:51 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 01:58 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 01:59 | |
| *** silviof3 <silviof3!~silviof@ppp-188-174-72-34.dynamic.mnet-online.de> has joined #yocto | 02:01 | |
| *** silviof2 <silviof2!~silviof@ppp-188-174-79-136.dynamic.mnet-online.de> has quit IRC | 02:03 | |
| -YoctoAutoBuilder- build #293 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm-lsb/builds/293 | 02:09 | |
| nerdboy | yo | 02:16 |
| -YoctoAutoBuilder- build #292 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-multilib/builds/292 | 02:19 | |
| -YoctoAutoBuilder- build #134 of minnow-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow-lsb/builds/134 | 02:30 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has joined #yocto | 02:37 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has quit IRC | 02:38 | |
| *** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC | 02:39 | |
| *** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto | 02:40 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has joined #yocto | 02:46 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has joined #yocto | 02:50 | |
| *** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC | 02:51 | |
| -YoctoAutoBuilder- build #292 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc-lsb/builds/292 | 02:58 | |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 03:04 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 03:06 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has quit IRC | 03:09 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 03:11 | |
| *** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto | 03:11 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 03:11 | |
| *** Jay7x <Jay7x!jay@2.94.242.252> has joined #yocto | 03:11 | |
| *** forcev <forcev!~quassel@wafaa.eu> has joined #yocto | 03:12 | |
| *** pidge_ <pidge_!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has joined #yocto | 03:13 | |
| *** jjardon_ <jjardon_!uid723@gateway/web/irccloud.com/x-lgkwvxfwkdlmwzor> has joined #yocto | 03:13 | |
| *** roxell_ <roxell_!~roxell@c-853670d5.07-21-73746f28.cust.bredbandsbolaget.se> has joined #yocto | 03:13 | |
| *** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has quit IRC | 03:13 | |
| *** Jay7 <Jay7!jay@2.94.242.252> has quit IRC | 03:13 | |
| *** challinan_ <challinan_!~challinan@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC | 03:13 | |
| *** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has quit IRC | 03:13 | |
| *** roxell <roxell!~roxell@linaro/roxell> has quit IRC | 03:13 | |
| *** erbo <erbo!~erik@host.62.65.125.245.bitcom.se> has quit IRC | 03:13 | |
| *** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC | 03:13 | |
| *** jjardon <jjardon!uid723@gateway/web/irccloud.com/x-xswjxxwatqksedjd> has quit IRC | 03:13 | |
| *** erbo <erbo!~erik@host.62.65.125.245.bitcom.se> has joined #yocto | 03:14 | |
| *** jjardon_ is now known as jjardon | 03:14 | |
| *** mitz__ <mitz__!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has joined #yocto | 03:14 | |
| *** ftonello <ftonello!~felipe@wsip-70-183-20-162.oc.oc.cox.net> has quit IRC | 03:17 | |
| *** ftonello <ftonello!~felipe@wsip-70-183-20-162.oc.oc.cox.net> has joined #yocto | 03:17 | |
| otavio | sgw_: there? | 03:18 |
| otavio | I am looking at u-boot build failure you reported (fw-utils) and am curious how it end being built | 03:19 |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 03:22 | |
| otavio | sgw_: is it a world build? | 03:23 |
| otavio | pidge_: do you have the build number which got the u-boot-fw-utils failure? | 03:25 |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 03:25 | |
| otavio | the bug is https://bugzilla.yoctoproject.org/show_bug.cgi?id=5223 | 03:25 |
| yocti | Bug 5223: major, High, 1.5 M5, anders, NEW , [autobuilder] u-boot-fw-utils does not build correctly | 03:25 |
| otavio | Found it | 03:27 |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has joined #yocto | 03:34 | |
| *** zenlinux__ is now known as zenlinux | 03:35 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 03:38 | |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has joined #yocto | 03:40 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has quit IRC | 03:41 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 03:41 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 03:43 | |
| otavio | sgw_: I sent the u-boot-fw-utils fix | 03:44 |
| otavio | zeddii: any clue about the ppc failure? I started a perf build in all my machines to see if any reproduce the issue. | 03:45 |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 03:47 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 03:48 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has joined #yocto | 03:48 | |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has quit IRC | 03:50 | |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 04:01 | |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 04:04 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 04:09 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 04:13 | |
| -YoctoAutoBuilder- build #295 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86/builds/295 | 04:15 | |
| *** [simar|on] <[simar|on]!~simar@206.248.139.195> has joined #yocto | 04:32 | |
| *** ynezz <ynezz!ynezz@ibawizard.net> has joined #yocto | 04:33 | |
| *** amarsman <amarsman!~marsman@52489B71.cm-4-1c.dynamic.ziggo.nl> has quit IRC | 04:35 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 04:36 | |
| *** Satrukaan <Satrukaan!~Thunderbi@192-0-149-234.cpe.teksavvy.com> has joined #yocto | 04:41 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 04:41 | |
| *** [simar|on] <[simar|on]!~simar@206.248.139.195> has quit IRC | 04:44 | |
| *** Satrukaan <Satrukaan!~Thunderbi@192-0-149-234.cpe.teksavvy.com> has quit IRC | 04:45 | |
| *** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has joined #yocto | 04:50 | |
| *** mihai <mihai!~mihai@188.27.91.28> has quit IRC | 04:54 | |
| *** _alex_kag_ <_alex_kag_!~alex_kag@178.124.25.159> has joined #yocto | 04:55 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 04:59 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has joined #yocto | 05:11 | |
| -YoctoAutoBuilder- build #270 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/270 | 05:11 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 05:14 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has quit IRC | 05:15 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 05:16 | |
| *** wgao <wgao!~wgao@1.202.252.122> has quit IRC | 05:18 | |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 05:19 | |
| *** sameo <sameo!samuel@nat/intel/x-inmvtrqqzhkkvzgr> has joined #yocto | 05:22 | |
| *** agust <agust!~agust@pD9E2FED9.dip0.t-ipconnect.de> has joined #yocto | 05:34 | |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has joined #yocto | 05:35 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 05:39 | |
| *** sameo <sameo!samuel@nat/intel/x-inmvtrqqzhkkvzgr> has quit IRC | 05:40 | |
| -YoctoAutoBuilder- build #268 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm-lsb/builds/268 | 05:42 | |
| *** tor <tor!~tor@c-d567e655.125-1-64736c10.cust.bredbandsbolaget.se> has joined #yocto | 05:50 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 05:52 | |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has quit IRC | 05:55 | |
| *** smartin <smartin!~smartin@46.218.232.202> has joined #yocto | 05:56 | |
| *** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto | 06:08 | |
| *** mihai <mihai!~mihai@80.97.15.150> has joined #yocto | 06:14 | |
| *** zeeblex <zeeblex!apalalax@nat/intel/x-paxdefzfsifvlsnv> has joined #yocto | 06:14 | |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 06:41 | |
| *** BjornArnelid <BjornArnelid!5be58d0a@gateway/web/freenode/ip.91.229.141.10> has joined #yocto | 06:45 | |
| BjornArnelid | Good morning. | 06:45 |
| *** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 06:51 | |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has joined #yocto | 06:55 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 06:58 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 07:00 | |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has quit IRC | 07:00 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 07:08 | |
| *** Zagor <Zagor!~bjst@sestofw01.enea.se> has joined #yocto | 07:09 | |
| *** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto | 07:09 | |
| *** florian <florian!~fuchs@port-217-146-132-69.static.qsc.de> has joined #yocto | 07:14 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 07:14 | |
| melonipoika | Morning | 07:16 |
| *** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has joined #yocto | 07:21 | |
| *** mckoan|away is now known as mckoan | 07:25 | |
| mckoan | good morning | 07:25 |
| *** bluelightning <bluelightning!~paul@83.217.123.106> has joined #yocto | 07:31 | |
| *** bluelightning <bluelightning!~paul@83.217.123.106> has quit IRC | 07:31 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 07:31 | |
| bluelightning | morning all | 07:31 |
| RP | morning | 07:32 |
| ant_work | gm folks | 07:34 |
| *** likewise <likewise!~likewise@h245113.upc-h.chello.nl> has joined #yocto | 07:35 | |
| ant_work | RP: I'm still struggling with the hardcoded paths to target_sysroot. May I ask you to comment on this by chance? http://tinyurl.com/njpzqre | 07:36 |
| *** hno <hno!~hno@squid/developer/hno> has quit IRC | 07:42 | |
| *** hno <hno!~hno@squid/developer/hno> has joined #yocto | 07:43 | |
| RP | ant_work: we do have a sysroot per machine but that does not mean things installed into the sysroot are machine specific | 07:45 |
| *** fpaut <fpaut!~fpaut@LVelizy-156-44-42-252.w217-128.abo.wanadoo.fr> has joined #yocto | 07:45 | |
| RP | ant_work: the problem is the klcc scripts? | 07:46 |
| ant_work | yes :/ | 07:47 |
| RP | ant_work: think about how we solve this with the gcc binaries - we pass in --sysroot to them through cflags | 07:47 |
| RP | ant_work: could you pass in a --sysroot option to klcc ? | 07:47 |
| ant_work | klibc and klcc-cross recipes are built with standard flags | 07:49 |
| ant_work | and in fact klcc-cross scripts points to the right binaries under /sysroots/i686-linux/usr/bin/armvXXX | 07:50 |
| ant_work | the problem is the last part of it | 07:50 |
| ant_work | where it teach the builds where the klibc headers (extra headers plus stuff) are | 07:50 |
| ant_work | here I get references to the target sysroot | 07:51 |
| ant_work | see includedir -> http://git.kernel.org/cgit/libs/klibc/klibc.git/tree/klcc/Kbuild | 07:52 |
| ant_work | the switch is $(INSTALLDIR) | 07:55 |
| *** Saur <Saur!pkj@nat/axis/x-ugznixvllmwewsjj> has quit IRC | 08:01 | |
| ant_work | RP: I even imagine it is possible to build klibc with headers in tcbootstrap but then the issue would remain: where to copy the headers to be shared by machine of the same arch? | 08:01 |
| *** spice <spice!~spice@83-65-34-132.arsenal.xdsl-line.inode.at> has joined #yocto | 08:02 | |
| RP | ant_work: you point them at the headers in the sysroot. when the sysroot changes, it needs to look in the new sysroot | 08:03 |
| RP | you have to specify this to the compiler | 08:03 |
| RP | just like we do with gcc-cross | 08:03 |
| ant_work | I'm sorry I can't follow.. all I can do is mangle oe_runmake 'INSTALLDIR=${STAGING_DIR_TARGET}${target_libdir}/klibc' klcc | 08:07 |
| ant_work | klcc i's not a binary | 08:07 |
| *** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC | 08:09 | |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 08:11 | |
| *** Saur <Saur!pkj@nat/axis/x-dacbyvzugvuhrjcj> has joined #yocto | 08:15 | |
| *** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 08:22 | |
| *** roric__ <roric__!~roric@194-237-7-146.customer.telia.com> has quit IRC | 08:22 | |
| *** roric <roric!~roric@194-237-7-146.customer.telia.com> has quit IRC | 08:24 | |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 08:25 | |
| ant_work | RP: I could manage so that the klibc recipe builds but I doubt it is in it's best shape ;) I'd appreciate vey much if one of you TC masters could 'visit' the puppy | 08:25 |
| *** BjornArnelid <BjornArnelid!5be58d0a@gateway/web/freenode/ip.91.229.141.10> has quit IRC | 08:26 | |
| spice | Hi all! I have the following problem: I am not able to create a working ISO file using Poky 9.0.2. The boot process hangs with: "Waiting for removable media…" Who could point me in the right direction to fix this? | 08:27 |
| *** elbc <elbc!2e12602e@gateway/web/freenode/ip.46.18.96.46> has quit IRC | 08:28 | |
| rburton | spice: that generally means udev is waiting for the right mount to appear | 08:28 |
| rburton | spice: have you been experimenting with systemd? | 08:29 |
| spice | not yet, I just tried to build core-image-base with default settings, except IMAGE_FSTYPES += "live" | 08:32 |
| spice | to get the iso file. | 08:32 |
| spice | I found this article via google, that says this was fixed in 4.0.1 ... https://lists.yoctoproject.org/pipermail/poky/2011-February/003583.html | 08:34 |
| rburton | hm the embedded initramfs should definitely have the mount rules | 08:38 |
| rburton | spice: you can check, go to tmp/work/[your machine]/core-image-minimal-initramfs/1.0-r0/rootfs | 08:39 |
| rburton | spice: there should be etc/udev/rules.d/automount.rules | 08:39 |
| ant_work | question: is the initramfs built? | 08:40 |
| *** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto | 08:43 | |
| *** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has quit IRC | 08:43 | |
| lpapp | hmm, I wonder how the unpack task can fail when I can unpack the tar.xz fine manually? | 08:44 |
| RP | ant_work: ok, how about you just create a machine specific part which takes a stored script and sets the sysroot correctly for that machine? | 08:46 |
| RP | ant_work: Right now I simply don't have the time, we should talk about it after the release | 08:47 |
| *** W1N9Zr0 <W1N9Zr0!~W1N9Zr0@69-165-241-155.cable.teksavvy.com> has quit IRC | 08:53 | |
| *** W1N9Zr0 <W1N9Zr0!~W1N9Zr0@69-165-241-155.cable.teksavvy.com> has joined #yocto | 08:53 | |
| ant_work | RP: I'll see about removing its sstate for now, if it is recreated for each machine all is just fine. For long term I'll surely poke you, thx | 08:54 |
| *** belen <belen!Adium@nat/intel/x-rlwtuaursffxjmbg> has joined #yocto | 08:56 | |
| *** roric <roric!~roric@194-237-7-146.customer.telia.com> has joined #yocto | 08:57 | |
| lpapp | file -> foo.tar.xz: POSIX tar archive | 08:59 |
| lpapp | why is yocto struggling with it? | 08:59 |
| lpapp | (to unpack) | 08:59 |
| rburton | lpapp: without seeing the unpack log its hard to say | 08:59 |
| lpapp | foo.tar.xz | tar x --no-same-owner -f - failed with return value 2 | 09:00 |
| rburton | lpapp: right | 09:00 |
| rburton | that's it | 09:00 |
| lpapp | manually running tar, it works fine. | 09:00 |
| rburton | your filename is tar.xz | 09:00 |
| rburton | but its not | 09:00 |
| rburton | its a .tar | 09:00 |
| lpapp | I do not follow. | 09:00 |
| rburton | its not compressed | 09:00 |
| lpapp | tar xvpf foo.tar.xz works just fine. | 09:00 |
| lpapp | so yocto should uncompress it without any issues, too. | 09:01 |
| rburton | .xz means "this file has been compressed with xz" | 09:01 |
| rburton | at no point in your tar command do you specify uncompressing | 09:02 |
| rburton | bitbake is seeing .tar.xz, and attempting to uncompress | 09:02 |
| lpapp | not sure what you mean. | 09:02 |
| lpapp | yocto should run tar xvpf | 09:02 |
| lpapp | and that should work. | 09:02 |
| lpapp | git archive --prefix=foo-0.1/ -o foo.tar.xz HEAD -> moreover, I do not see how this could generate non xz. | 09:02 |
| lpapp | it used to work in the path... I wonder what channged... o_O | 09:02 |
| rburton | because you didn't compress it | 09:02 |
| rburton | that writes a .tar | 09:02 |
| rburton | git-archive writes a tarball | 09:03 |
| rburton | it does not also compress it | 09:03 |
| lpapp | I am not sure I follow | 09:04 |
| lpapp | I used the same the command as before. | 09:04 |
| lpapp | and it worked fine with yocto as well without bothering. | 09:04 |
| rburton | you must have done something different | 09:05 |
| rburton | git-archive produces an uncompressed tarball | 09:05 |
| rburton | but you're calling it .tar.xz | 09:05 |
| rburton | which bitbake understandably considers to be a xz-compressed tarball | 09:05 |
| rburton | so tries to uncompress it | 09:05 |
| rburton | and fails | 09:05 |
| rburton | because its not compressed | 09:05 |
| lpapp | nope | 09:06 |
| rburton | as git-archive --help shows, pipe git-archive through xz or gzip or bzip2 | 09:06 |
| lpapp | git archive is supposed to provide a compressed tarball, name 'xz' format. | 09:06 |
| lpapp | namely* | 09:06 |
| lpapp | but even if git archive fails, Yocto should not. | 09:06 |
| lpapp | not sure why git archive fails though. | 09:06 |
| lpapp | rburton: seems git cannot produce xz at all... that is a weird surprise. | 09:12 |
| rburton | as i said, git archive doesn't compress | 09:12 |
| lpapp | anyway, it worked before with exactly the same command before copying the file to the yocto tree. | 09:12 |
| lpapp | so how did it work before? | 09:12 |
| rburton | you did something differently | 09:12 |
| lpapp | nope | 09:12 |
| lpapp | I did exactly the same. | 09:12 |
| rburton | anywya, does it matter? just pipe git-archive through xz and you'll be sorted | 09:12 |
| Guest31240 | Hi, How quick question ... How to replace this in bitbake recipe for yocto? | 09:13 |
| Guest31240 | fakeroot do_install() { | 09:13 |
| lpapp | well, it matters. | 09:13 |
| lpapp | it used to work.... | 09:13 |
| lpapp | I would understand why it does not work anymore.... | 09:13 |
| spice | rburton: i will have a look | 09:17 |
| Guest31240 | hi how to replace fakeroot do_install() { in yocto. It doesnt find recipe for fakeroot-native | 09:22 |
| Guest31240 | ??? | 09:22 |
| spice | rburton: I see two non commented lines in automount.rules: | 09:22 |
| spice | SUBSYSTEM=="block", ACTION=="add" RUN+="/etc/udev/scripts/mount.sh" | 09:22 |
| spice | SUBSYSTEM=="block", ACTION=="remove" RUN+="/etc/udev/scripts/mount.sh" | 09:22 |
| *** likewise <likewise!~likewise@h245113.upc-h.chello.nl> has quit IRC | 09:23 | |
| rburton | spice: so in that case, maybe your initramfs kernel doesn't know how to mount your media or access your device | 09:23 |
| spice | hm... | 09:23 |
| gonzzor | If I have files that should be part of the final image loaded on the hw, which isn't part of the kernel nor rootfs. How should such files be handled? | 09:24 |
| ant_work | rburton: spice: is the kernel really embedding the initramfs? | 09:24 |
| gonzzor | Added to the rootfs and removed using a image postprocess command and put into it's correct container? | 09:24 |
| spice | ant_work: how do I verify that? | 09:25 |
| ant_work | well, check the size or the presence of the cpio.(gz:lzma) in kernel workdir under linux/usr | 09:26 |
| lpapp | rburton: think I found the root cause. | 09:26 |
| lpapp | I had the tar.xz git setting in my config | 09:26 |
| lpapp | not this time. | 09:26 |
| spice | ant_work: rburton: when i open the ISO file with 7-zip i see the file "initrd" and there is also an according APPEND line in isolinux.cfg | 09:27 |
| ant_work | ah, ok, then it is not embedded | 09:27 |
| ant_work | I have right now issues with the old way of embedding initramfs, settting INITRAMFS_IMAGE | 09:28 |
| ant_work | I thougth you're maybe impacted but I see those image uses plain old initrd | 09:29 |
| lpapp | rburton: file format still not recognized for unpacking... what the ... hack ? :) | 09:29 |
| bluelightning | Guest31240: fakeroot-native should be provided by pseudo-native | 09:29 |
| *** Krz_ <Krz_!c0c6972c@gateway/web/freenode/ip.192.198.151.44> has joined #yocto | 09:30 | |
| rburton | lpapp: run file on the tarball, check it matches the filename | 09:30 |
| bluelightning | Guest31240: to be precise, virtual/fakeroot-native should be provided by pseudo-native | 09:31 |
| bluelightning | Guest31240: do_install is already marked fakeroot btw, so that shouldn't be necessary in the recipe anyway | 09:32 |
| *** _alex_kag_ <_alex_kag_!~alex_kag@178.124.25.159> has quit IRC | 09:33 | |
| Krz_ | I enabled 'argp' in my DISTRO_FEATURES for uclibc image, now trying to build opencv: /dev/shm/kmsywula/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux-uclibc/gcc/i586-poky-linux-uclibc/4.7.2/ld: cannot find -largp | collect2: error: ld returned 1 exit status | 09:40 |
| Krz_ | any idea? | 09:41 |
| Krz_ | the error comes from v4l2apps/v4l-utils_0.8.8 | 09:42 |
| *** mankku <mankku!~mankku@projects.sse.fi> has quit IRC | 09:42 | |
| *** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 09:42 | |
| *** ant___ <ant___!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 09:42 | |
| *** boz_v1 <boz_v1!~juukorho@projects.sse.fi> has quit IRC | 09:43 | |
| lpapp | rburton: thanks. | 09:47 |
| Guest31240 | thx bluelightning | 09:48 |
| *** dv_ <dv_!~quassel@chello080108009040.14.11.vie.surfer.at> has quit IRC | 09:49 | |
| *** gjohnson <gjohnson!~gjohnson@nwtn-static-agleaders0-0003.flex.iowatelecom.net> has quit IRC | 09:49 | |
| *** boz_v1 <boz_v1!~juukorho@projects.sse.fi> has joined #yocto | 09:52 | |
| spice | ant_work: rburton: Any ideas what I can do to debug my non working LiveCD? | 09:53 |
| *** dv_ <dv_!~quassel@chello080108009040.14.11.vie.surfer.at> has joined #yocto | 09:55 | |
| *** ant___ <ant___!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 09:56 | |
| *** mankku <mankku!~mankku@projects.sse.fi> has joined #yocto | 09:57 | |
| spice | rburton: ant_work: Another idea: Is there a possibility to build an initrd only LiveCD? | 09:58 |
| lpapp | hmm, what is the reason of having ./tmp/deploy/rpm/i586/ but not ./tmp/deploy/rpm/arm ? | 10:00 |
| lpapp | where can I find the rpm packages for my arm board? | 10:00 |
| rburton | lpapp: if there's not there, then maybe you removed package_rpm from your PACKAGE_CLASSES | 10:01 |
| lpapp | rburton: hmm, yeah, it was changed to package_ipk | 10:02 |
| lpapp | not that I see opkg packages? | 10:02 |
| rburton | the directory will be ipkg | 10:03 |
| lpapp | I do not have such a folder. | 10:03 |
| rburton | sorry, ipk. | 10:03 |
| rburton | $ ls /data/poky-master/tmp/deploy/ | 10:04 |
| rburton | images ipk licenses sdk | 10:04 |
| rburton | ^ mine | 10:04 |
| lpapp | strange. | 10:04 |
| lpapp | ok, now I have it after rebuild, thanks. | 10:06 |
| lpapp | is there a --prefix option with ipkg if I wanna install my package into /opt/foo ? | 10:06 |
| lpapp | or if I wanna have such a thing, I need to use rpm? | 10:06 |
| rburton | lpapp: why not build your package so that it installs into /opt/foo directly | 10:06 |
| lpapp | rburton: because others may want to install it usually. | 10:07 |
| rburton | not sure if ipk has that option | 10:08 |
| rburton | it does kinda break any hard-coded paths in the files | 10:08 |
| lpapp | rpm has --prefix at least. | 10:09 |
| rburton | sure. but any hard-coded paths will be incorrect. | 10:10 |
| lpapp | install -d ${D}${bindir} and install -m 0755 ${WORKDIR}/foo-0.1/foo/foo ${D}${bindir}/ | 10:10 |
| lpapp | I have this, yet my rpm packages are empty. :( | 10:10 |
| lpapp | Shouldn't at least my "foo" binary inside? | 10:10 |
| rburton | did you set FILES_${PN}? | 10:11 |
| lpapp | we do not use hard coded paths in our software. | 10:11 |
| lpapp | nope | 10:11 |
| lpapp | but I think install should be fine to the generic locations. | 10:11 |
| lpapp | as the default class content takes care of the usual paths. | 10:11 |
| rburton | then yes, the default should have caught that. in the work directory for that package you'll image, package, packages-split | 10:11 |
| rburton | see if anything is in those | 10:12 |
| rburton | (that's the order that stuff moves, do_install moves to image, then a link farm is made to package, which is then split into packages-split) | 10:12 |
| lpapp | rburton: yes, it is in that folder. | 10:15 |
| lpapp | I used rpm -l to list the content. | 10:15 |
| lpapp | hope that is the right command to check if there is anything inside. | 10:15 |
| *** Stygia <Stygia!~gmpsaifi@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk> has joined #yocto | 10:16 | |
| rburton | rpm -qpl, isn't it? | 10:17 |
| lpapp | ah, ok. | 10:17 |
| lpapp | my mistake then. :-) | 10:17 |
| lpapp | I thought -l would be fine. | 10:17 |
| spice | rburton: ant:work: I see another interesting thing on my LiveCD: According to the script "/rootfs/init" I should get dropped to a shell after 30 seconds, but this does not happen. What do I have to do to get manual changes to the rootfs on my ISO file to debug this? | 10:17 |
| lpapp | the list the content. | 10:17 |
| lpapp | rburton: what is the best practice for creating a bundled package? | 10:18 |
| lpapp | i.e. putting the openssl, etc libraries into the package. | 10:18 |
| lpapp | is it possible without putting those into the archive? | 10:19 |
| *** Krz_ <Krz_!c0c6972c@gateway/web/freenode/ip.192.198.151.44> has quit IRC | 10:22 | |
| *** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto | 10:23 | |
| *** _alex_kag_ <_alex_kag_!~alex_kag@178.126.178.164> has joined #yocto | 10:23 | |
| *** BjornArnelid <BjornArnelid!53fa9d78@gateway/web/freenode/ip.83.250.157.120> has joined #yocto | 10:25 | |
| *** Krz_ <Krz_!c0c69725@gateway/web/freenode/ip.192.198.151.37> has joined #yocto | 10:26 | |
| lpapp | rburton: hmm, the distributed rpm by core-image-minimal does not have the --prefix option. :( | 10:28 |
| lpapp | it seems to be coming from busybox? rpm | 10:29 |
| lpapp | BusyBox v1.20.2 (2012-11-16 01:53:09 GMT) multi-call binary. | 10:29 |
| lpapp | strange, my desktop busybox does not contain rpm... what is the origin of this then? | 10:29 |
| lpapp | yep, it is busybox. | 10:32 |
| lpapp | although it is a chopped variant (not supporting prefix :( | 10:32 |
| lpapp | ) | 10:32 |
| rburton | our defconfig disables that, so presumably that's your busybox | 10:33 |
| lpapp | oh, packages-split seems to be already stripped. | 10:34 |
| *** Jay7x <Jay7x!jay@2.94.242.252> has quit IRC | 10:44 | |
| lpapp | is it okay with Yocto if I want to have a daemon running automatically on boot with core-image-minimal, I just add my own init.d script in etc? | 10:45 |
| *** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC | 10:46 | |
| *** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC | 10:54 | |
| *** forcev is now known as FunkyPenguin | 10:56 | |
| *** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 10:57 | |
| *** e8johan_ <e8johan_!~quassel@194.237.7.146> has joined #yocto | 11:01 | |
| *** e8johan <e8johan!~quassel@194-237-7-146.customer.telia.com> has quit IRC | 11:01 | |
| *** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC | 11:08 | |
| RP | lpapp: I don't think it makes much difference to Yocto if you do that :) | 11:09 |
| RP | lpapp: it sounds reasonable | 11:09 |
| spice | rburton: Hi, just a short status update: So far I did not get the *.iso working in QEMU, but when I write the *.hddimg to an USB thumb drive it successfully boots on real hardware! | 11:10 |
| lpapp | RP: OK, thanks. | 11:10 |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 11:15 | |
| *** eren <eren!~eren@unaffiliated/eren> has joined #yocto | 11:16 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 11:29 | |
| *** blitz00 <blitz00!stefans@nat/intel/x-epjnoefzhewohqbh> has joined #yocto | 11:31 | |
| *** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto | 11:31 | |
| *** mshakeel <mshakeel!~mshakeel@110.93.212.98> has left #yocto | 11:32 | |
| *** Anusko <Anusko!~jcf@62.159.77.165> has quit IRC | 11:33 | |
| *** Anusko <Anusko!~jcf@62.159.77.165> has joined #yocto | 11:34 | |
| *** walters <walters!~walters@c-66-31-18-51.hsd1.ma.comcast.net> has quit IRC | 11:37 | |
| *** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC | 11:38 | |
| *** zecke <zecke!~ich@p5099b351.dip0.t-ipconnect.de> has joined #yocto | 11:46 | |
| *** TuTizz <TuTizz!~TuTizz@46.18.96.158> has joined #yocto | 11:47 | |
| *** spice <spice!~spice@83-65-34-132.arsenal.xdsl-line.inode.at> has quit IRC | 11:49 | |
| *** acidfu <acidfu!~nib@24.37.17.210> has joined #yocto | 11:54 | |
| *** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto | 11:54 | |
| *** Anusko <Anusko!~jcf@62.159.77.165> has quit IRC | 11:55 | |
| *** TuTizz <TuTizz!~TuTizz@46.18.96.158> has quit IRC | 12:01 | |
| *** mshakeel <mshakeel!~mshakeel@110.93.212.98> has joined #yocto | 12:01 | |
| Krz_ | I created recipe with SRC_URI += 'my.patch' and now fetcher cannot find that file. What was the trick to let know fetcher where the file is? I added it to files/ subdirectory of my bbappend recipe. | 12:05 |
| bluelightning | Krz_: is this a recipe or a bbappend? | 12:07 |
| Krz_ | bluelightning: bbappend | 12:07 |
| *** likewise <likewise!~likewise@h245113.upc-h.chello.nl> has joined #yocto | 12:07 | |
| bluelightning | Krz_: did you also extend FILESEXTRAPATHS in the bbappend? | 12:07 |
| *** TuTizz <TuTizz!~TuTizz@46.18.96.158> has joined #yocto | 12:07 | |
| Krz_ | bluelightning: no, I just added SRC_URI line | 12:07 |
| Krz_ | bluelightning: pointing to my patch | 12:08 |
| bluelightning | Krz_: right, you need to do FILESEXTRAPATHS_prepend := "${THISDIR}/files:" | 12:09 |
| Krz_ | bluelightning: works like a charm, thanks | 12:11 |
| bluelightning | Krz_: np | 12:12 |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 12:15 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 12:18 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 12:22 | |
| *** scot_ <scot_!~scot@130.164.62.183> has joined #yocto | 12:26 | |
| *** padge_ <padge_!~quassel@83-64-248-68.inzersdorf.xdsl-line.inode.at> has joined #yocto | 12:28 | |
| *** BjornArnelid <BjornArnelid!53fa9d78@gateway/web/freenode/ip.83.250.157.120> has quit IRC | 12:28 | |
| *** mthalmei_away is now known as mthalmei | 12:34 | |
| *** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC | 12:34 | |
| *** vmeson <vmeson!~quassel@128.224.252.2> has quit IRC | 12:35 | |
| *** vmeson <vmeson!~quassel@128.224.252.2> has joined #yocto | 12:37 | |
| *** tinti_ <tinti_!~tinti@201.49.230.58> has joined #yocto | 12:40 | |
| *** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has joined #yocto | 12:40 | |
| *** Jay7 <Jay7!jay@2.94.131.64> has joined #yocto | 12:41 | |
| *** mthalmei is now known as mthalmei_away | 12:42 | |
| *** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 12:46 | |
| *** roric_ <roric_!~roric@c-7e72e455.213-3-64736c14.cust.bredbandsbolaget.se> has joined #yocto | 12:48 | |
| *** mshakeel <mshakeel!~mshakeel@110.93.212.98> has quit IRC | 12:49 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 12:49 | |
| *** mshakeel <mshakeel!~mshakeel@110.93.212.98> has joined #yocto | 12:51 | |
| *** gmacario <gmacario!~gmacario@maxlab.polito.it> has joined #yocto | 12:52 | |
| *** elbc <elbc!2e12602e@gateway/web/freenode/ip.46.18.96.46> has joined #yocto | 13:02 | |
| elbc | rburton: hi ! I succeeded in building gstreamer1.0 plugins ! hiwever the pipe failed : it seems that a gbm_gallium_drm.so file is needed (linked to mesalib or ligbm1) and I pull one's hair out to find how to have this file, so if yoou have time or any idea let me know ! | 13:05 |
| *** roric_ <roric_!~roric@c-7e72e455.213-3-64736c14.cust.bredbandsbolaget.se> has quit IRC | 13:07 | |
| rburton | elbc: mesa probably built it, have a look at packages in your deploy with mesa in their name | 13:07 |
| elbc | i have done a find . -name gbm_gallium_drm.so | 13:09 |
| elbc | and nothing | 13:09 |
| elbc | the package ligbm1 is present and installed on the image but is not providing the /usr/lib/gbm_gallium_drm.so | 13:10 |
| elbc | libgbm1 | 13:10 |
| rburton | there might be a mesa-driver-gallium-something | 13:12 |
| rburton | by default we don't build gallium though | 13:12 |
| elbc | rburton: ok thanks but how to build without gallium and to make gstreamer1.0 working under wayland ? | 13:14 |
| rburton | elbc: no idea, sorry. | 13:15 |
| rburton | haven't tried that yet | 13:15 |
| elbc | ok thank you anyway ! | 13:15 |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has joined #yocto | 13:16 | |
| *** walters <walters!walters@nat/redhat/x-czevttnefvmapamz> has joined #yocto | 13:18 | |
| *** cascardo <cascardo!cascardo@nat/ibm/x-kecxioqsrhgdgwgi> has joined #yocto | 13:21 | |
| *** e8johan_ <e8johan_!~quassel@194.237.7.146> has quit IRC | 13:21 | |
| *** walters <walters!walters@nat/redhat/x-czevttnefvmapamz> has quit IRC | 13:23 | |
| *** e8johan <e8johan!~quassel@194-237-7-146.customer.telia.com> has joined #yocto | 13:30 | |
| *** joeythesaint <joeythesaint!~jjm@128.224.252.2> has joined #yocto | 13:35 | |
| *** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 13:41 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 13:45 | |
| *** gjohnson <gjohnson!~gjohnson@nwtn-static-agleaders0-0003.flex.iowatelecom.net> has joined #yocto | 13:45 | |
| otavio | sgw_1: perf fix for ppc sent | 13:56 |
| *** volker_ <volker_!~quassel@host-80-81-19-29.customer.m-online.net> has joined #yocto | 13:56 | |
| *** volker <volker!~quassel@host-80-81-19-29.customer.m-online.net> has quit IRC | 13:56 | |
| *** belen <belen!Adium@nat/intel/x-rlwtuaursffxjmbg> has quit IRC | 13:57 | |
| *** bluelightning_ <bluelightning_!~paul@83.217.123.106> has joined #yocto | 14:01 | |
| *** bluelightning_ <bluelightning_!~paul@83.217.123.106> has quit IRC | 14:01 | |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 14:01 | |
| *** belen <belen!~Adium@134.134.139.76> has joined #yocto | 14:02 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 14:03 | |
| *** sameo <sameo!~samuel@192.55.54.36> has joined #yocto | 14:03 | |
| *** mihai <mihai!~mihai@80.97.15.150> has quit IRC | 14:09 | |
| Krz_ | I have a recipe for opencv (meta-oe) which depends on GTK+. I want to build it without GTK+ support. Can I create a bbappend + patch on top of original recipe to remove GTK+ dependency? | 14:12 |
| JaMa | it would be best to send patch to meta-oe converting gtk+ dependency to PACKAGECONFIG | 14:13 |
| JaMa | then you can have only very small .bbappend or just line in config disabling gtk+ dependency for your build | 14:14 |
| *** wv <wv!~wv@ip2.televic.com> has joined #yocto | 14:14 | |
| wv | hello, I want to bitbake core-image-web-kiosk for my imx53qsb | 14:15 |
| wv | this works | 14:15 |
| Krz_ | JaMa: can you give me some pointers on how to do that? I don't have much experience with PACKAGECONFIG | 14:15 |
| wv | but I also want to add gstreamer1.0 with all plugins | 14:15 |
| wv | I do this by passing IMAGE_INSTALL_append = " gstreamer1.0 gstreamer1.0-plugins-base etc..." to my local.conf | 14:16 |
| wv | I think they are getting build, but I don't see all plugins in my rootfs | 14:16 |
| wv | I only have the libav and omx plugins available | 14:17 |
| wv | even the gstreamer0.10 which is apparantly build standard with this bitbake doesn't provide these plugins | 14:17 |
| *** nitink1 <nitink1!~nitink@134.134.139.70> has joined #yocto | 14:18 | |
| *** nitink <nitink!nitink@nat/intel/x-ctgrrbekcbtblcbm> has quit IRC | 14:18 | |
| kergoth | wv: the plugins are packaged in a very granular fashion, gstreamer1.0-plugins-base will only install the 'base' plugins | 14:19 |
| wv | yes, I know, with the thing that I don't see them via gst-inspect1.0 | 14:21 |
| wv | even when I should have added them via IMAGE_INSTALL_append | 14:21 |
| Krz_ | JaMa: PACKAGECONFIG does not support 'EXTRA_OECMAKE' and I need to remove '-DWITH_GTK=ON' from that variable... | 14:23 |
| bluelightning_ | Krz_: PACKAGECONFIG will add to EXTRA_OECMAKE if the recipe inherits cmake | 14:24 |
| *** sameo <sameo!~samuel@192.55.54.36> has quit IRC | 14:24 | |
| Krz_ | bluelightning_: in documentation PACKAGECONFIG is described as: EXTRA_OECONF, EXTRA_OECONF, DEPENDS, RDEPENDS | 14:25 |
| Krz_ | bluelightning_: if recipe inherits cmake where do I put my EXTRA_OECMAKE ? | 14:25 |
| bluelightning_ | Krz_: it happens automatically | 14:28 |
| bluelightning_ | Krz_: the documentation is perhaps deficient in not mentioning that it'll add to EXTRA_OECMAKE automatically if the recipe inherits cmake | 14:29 |
| bluelightning_ | (instead of EXTRA_OECONF, that is) | 14:29 |
| *** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC | 14:30 | |
| JaMa | Krz_: grep for PACKAGECONFIG in meta-oe, there are some examples from me also using EXTRA_OECMAKE (but it looks the same as in recipe with autotools and EXTRA_OECONF) | 14:32 |
| *** _alex_kag_ <_alex_kag_!~alex_kag@178.126.178.164> has quit IRC | 14:34 | |
| *** likewise <likewise!~likewise@h245113.upc-h.chello.nl> has quit IRC | 14:36 | |
| *** belen <belen!~Adium@134.134.139.76> has quit IRC | 14:37 | |
| *** belen <belen!~Adium@134.134.137.75> has joined #yocto | 14:38 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has joined #yocto | 14:41 | |
| *** mckoan is now known as mckoan|away | 14:42 | |
| wv | Is it possible that I have somewhere a filter which prevents me in adding these gstreamer1.0-plugins-base, good etc? | 14:42 |
| wv | (rather new to yocto) | 14:43 |
| *** ArunKumar <ArunKumar!~SnowWhite@203.187.209.201> has joined #yocto | 14:48 | |
| TuTizz | Have anyone got any yocto's tutorial, I am actually reading the mega-manual and it is difficult to understand without trying. Example : for a custom image, should I write my own recipe or just write my options in the conf/local.conf file? | 14:56 |
| *** wmcdevel <wmcdevel!~wmcdevel@barracuda.hmctelco.com> has joined #yocto | 14:57 | |
| *** joeythesaint <joeythesaint!~jjm@128.224.252.2> has quit IRC | 14:57 | |
| *** bluelightning1 <bluelightning1!~paul@83.217.123.106> has joined #yocto | 14:57 | |
| *** bluelightning1 is now known as bluelightning | 14:57 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 14:57 | |
| fray | TuTizz I don't have one, but I can help you.. | 14:59 |
| fray | if you are just screwing around, doing it in the conf/local.conf is easier... but if you are making a product, it's much better to write a custom image recipe.. | 14:59 |
| fray | MUCH easier to share and maintain | 14:59 |
| TuTizz | yes this is it, I creating a new product. | 15:01 |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 15:01 | |
| TuTizz | so I should create a new recipe, for example I want qt4e and openssh | 15:02 |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 15:02 | |
| fray | you can 'require' an existing image recipe, and then start modifying from that.. or copying it and make changes, etc.. | 15:02 |
| fray | it should be as simple as adding the packages (not recipes) that you want installed to the IMAGE_INSTALL (think that is right) variable | 15:03 |
| TuTizz | ok, a good start should be extend core-image-minimal | 15:03 |
| TuTizz | ? | 15:03 |
| wmcdevel | @TuTizz: for openssh, you'll want to add ssh-server-openssh to your IMAGE_FEATURES ... that will cause it to be picked up | 15:03 |
| fray | if you are trying for a small image,t hen yes that is a perfect starting point.. | 15:04 |
| fray | core-image-basic (or is it core-image-core) is a good point if you want discrete (not busybox) command line apps | 15:04 |
| wmcdevel | core-image-basic | 15:04 |
| fray | always try to build from small UP to what you want.. | 15:04 |
| wmcdevel | if you want more than busybox :) | 15:04 |
| fray | it's much more difficult to start with something too big and build "down" | 15:05 |
| TuTizz | ok | 15:05 |
| *** dvhart <dvhart!~dvhart@134.134.139.72> has joined #yocto | 15:05 | |
| Krz_ | bluelightning: JaMa: my point is what's the syntax for PACKAGECONFIG in recipe inheriting cmake | 15:05 |
| fray | the other thing to keep in mind, unless you know -exactly- what you need in your image.. a good place to start is the various 'packagegroup' recipes.. the purpose of those is to implement specific sets of functionality | 15:06 |
| TuTizz | qt4e-demo-image run on my imx6, (I don't want the demo so I kill it then start my own application) | 15:06 |
| TuTizz | ok lets talk about packagegroup | 15:06 |
| Krz_ | bluelightning: JaMa: I presume it's PACKAGECONFIG[xyz] = "EXTRA_OECMAKE, EXTRAOECMAKE, DEPENDS, RDEPENS", am I right? | 15:07 |
| fray | packagegroup-core-boot -- things required to 'boot' a typical system | 15:07 |
| TuTizz | if I want qt4e without the demo, I can extend core-image-basic with qt4-embedded_4.8.5.bb | 15:07 |
| *** joeythesaint <joeythesaint!~jjm@128.224.252.2> has joined #yocto | 15:08 | |
| fray | .. what you can do is: | 15:08 |
| fray | create a new recipe | 15:08 |
| fray | require core-image-basic.bb | 15:08 |
| fray | IMAGE_INSTALL += "qt4-embedded" | 15:09 |
| fray | there is a packagegroupe though.. packagegroup-core-qt and packagegroup-core-qt4e | 15:09 |
| bluelightning | Krz_: yes that's correct for recipes that inherit cmake | 15:09 |
| fray | that would add additional things usually needed for qt/qte | 15:09 |
| Krz_ | bluelightning: great, thanks | 15:09 |
| TuTizz | then bitbake myRecipe | 15:10 |
| TuTizz | ? | 15:11 |
| TuTizz | Another information, where should I put my new recipe? In meta directory? In meta-imx6? | 15:17 |
| fray | ys.. | 15:20 |
| fray | yes | 15:20 |
| fray | best practice is to create a new customer layer for your recipes.. | 15:20 |
| fray | then place them in there.. | 15:20 |
| fray | basically create a new directory.. 'meta-local' for instance.. | 15:21 |
| fray | then inside of there you need a conf/layer.conf | 15:21 |
| fray | look at meta-yocto/conf/layer.conf as an example.. | 15:22 |
| fray | copy that file, and then replace 'yocto' with 'local' | 15:22 |
| fray | (remove the LAYERVERSION_yocto = "2" it's not needed for your local layer) | 15:22 |
| fray | (or set it to '1') | 15:22 |
| fray | then as you create recipes.. just place them under 'recipes-<category>/<recipe>/<recipe>.bb | 15:23 |
| *** wv <wv!~wv@ip2.televic.com> has quit IRC | 15:25 | |
| wmcdevel | TuTizz: I would also suggest reading through the Yocto Project Development manual ... take a look at section 5.1 Understanding and Creating Layers ... there's a lot to digest there, but it covers basically everything you need to develop your own custom layer for your recipes. | 15:25 |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 15:25 | |
| fray | yup.. the stuff I am telling you should all be covered.. | 15:26 |
| fray | but get in the habit of saving your work to recipes and in you own 'layer' right away.. | 15:26 |
| fray | it will pay off in the long run with code you can share with others, and an easier way to manage things in an SCM.. | 15:26 |
| JaMa | just to be sure that I'm not overlooking something, INCOMPATIBLE_LICENSE is global setting for whole distro, right? i.e. it cannot be different for normal-image and devel-image | 15:26 |
| fray | (you just need to store your layer and perhaps configuration files in the SCM, instead of your whole project) | 15:26 |
| fray | JaMa, it's global.. but you can use the overrides to play some games.. as well as the whitelisting | 15:27 |
| JaMa | true, but I cannot use e.g. image-name as _pn override, so the global flag isn't very useful for my use-case | 15:29 |
| *** mihai <mihai!~mihai@188.27.91.28> has joined #yocto | 15:29 | |
| JaMa | for example I cannot exclude binutils from normal image by INCOMPATIBLE_LICENSE_pn-normal-image while keeping it included in devel-image (pulled by the same packagegroup) | 15:29 |
| wmcdevel | TuTizz: fray: just to throw it out there, as it has been a big help to me the past few days, a good example of customizing Yocto/Poky to your needs is: github.com/Guacamayo/meta-guacamayo/ ... I really like how they set up their project, and it gives example of custom layers, customized recipes, and a customized distro. | 15:30 |
| fray | ya, can't do that | 15:30 |
| *** hollisb <hollisb!~hollisb@c-67-169-221-181.hsd1.or.comcast.net> has joined #yocto | 15:30 | |
| fray | you can do it based on global flags for debug and such | 15:30 |
| TuTizz | ok thank you very much wmcdevel and fray, I am more confident now, I will try it. (and re-read the section 5.1) | 15:31 |
| wmcdevel | TuTizz: you're most welcome | 15:31 |
| fray | no problem.. | 15:32 |
| fray | JaMa, you can do stuff like look for 'DEBUG_BUILD' = 1 | 15:33 |
| fray | vs a FULL_OPTIMIZATION build that kind of thing | 15:33 |
| JaMa | huh | 15:36 |
| JaMa | are you saying that I can build devel-image with DEBUG_BUILD = 1 and normal-image with DEBUG_BUILD = 0? I don't think so | 15:36 |
| fray | you can.. it'll rebuild | 15:37 |
| elbc | rburton: I have configured the mesa.bb to build with gallium but I've got the following error : EGL/eglplatform.h: No sych file or directory (I've seen you already know the problem) | 15:37 |
| fray | the FULL and DEBUG optimizations are differnt | 15:37 |
| JaMa | that's exactly what I don't want :) | 15:37 |
| fray | ok | 15:37 |
| JaMa | I can use uninstall feature in worst case to maintain list of incompatible packages and remove them after image is built | 15:38 |
| JaMa | or just carefully keep dependency trees for images separate so that any incompatible package won't leak into normal image | 15:39 |
| fray | yes | 15:39 |
| fray | you can also use the new PACKAGE_EXCLUDE functionality to prevent packages from being installed | 15:40 |
| *** joeythesaint <joeythesaint!~jjm@128.224.252.2> has quit IRC | 15:40 | |
| fray | set PACKAGE_EXCLUDE = "..." in the production image that you -never- want installed on the target and it'll prevent them from 'leaking in' due to dependencies | 15:40 |
| kergoth | guh, BUILD_CFLAGS is exported, so ends up in the task deps of *target* recipes | 15:40 |
| *** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 15:40 | |
| fray | thats because of apps building local 'helpers' and such.. | 15:41 |
| fray | but it might make sense to avoid that.. | 15:41 |
| kergoth | yeah, but the output doesn't change, thats internal build use | 15:41 |
| kergoth | so while it's technically used, it might not be best to include it in the signature.. hmm | 15:41 |
| fray | it could affect the packaging or sysroot.. but I'm not sure if thats a real concern.. | 15:41 |
| kergoth | at this point we can't share target sstates across different build hosts anymore, since we had to explicitly add -march=<arch> to our builds, as we're building on centos5 with a 4.5 native toolchain | 15:43 |
| kergoth | heh | 15:43 |
| fray | (I'm thinking of the few recipes that build a local helper and install it into the cross sysroot.. but I'm wondering if those are all scripts and no executables) | 15:43 |
| fray | in fact I'm pretty sure that is the case | 15:43 |
| fray | the -march= is only needed on the -really- old compiler(s) | 15:44 |
| *** ArunKumar <ArunKumar!~SnowWhite@203.187.209.201> has quit IRC | 15:44 | |
| kergoth | centos 5 uses a really old compiler, at least according to poky's sanity.bbclass checks :) | 15:45 |
| * kergoth looks into some sort of workaround until we can pursue a longer temr fix | 15:46 | |
| fray | I thought latest centos 5 worked.. maybe not | 15:46 |
| *** fpaut is now known as fpaut_ | 15:46 | |
| fray | you can always use the ${HOST_MARCH} -- exclude HOST_MARCH, set HOST_MARCH = '-march=' when necessary | 15:46 |
| kergoth | we've had to work around a number of problems over time, even when using the buildtools tarball | 15:47 |
| kergoth | good point, that'd work as a workaround, thanks | 15:47 |
| kergoth | didn't think about that | 15:47 |
| fray | if you do that, I'd like to see the patch.. we may have to do the same.. :) | 15:47 |
| *** drasko <drasko!~drasko@gut75-3-82-227-163-94.fbx.proxad.net> has joined #yocto | 15:47 | |
| drasko | Hi all. How to remove package source with bitbake? | 15:48 |
| Krz_ | I have the bbappend which is not applied by Yocto on original recipe. Does the order of layers in bblayers.conf matter? Or maybe these magic numbers in layer.conf: BBFILE_PRIORITY ? | 15:49 |
| fray | order int he bblayers.conf does matter.. | 15:49 |
| bluelightning | Krz_: bbappends are applied in priority order, but always after the recipe | 15:49 |
| fray | so does the file priority.. but I believe the file priority only matters if you have two files of identical names.. (.conf, .bb... NOT .bbappend) | 15:49 |
| drasko | Is there a command to bitbake to remove package source from download directory? | 15:49 |
| fray | ahh so it does also affect application order of bbappends | 15:50 |
| *** belen <belen!~Adium@134.134.137.75> has quit IRC | 15:50 | |
| fray | see #oe.. bitbake -c cleanall <recipe> | 15:50 |
| elbc | rburton: if you have any solution don't hesitate to tell me about. thank you again | 15:50 |
| fray | does clean, cleansstate as well | 15:50 |
| bluelightning | fray: it didn't way back when bbappends were first introduced, but it was changed to do it quite a while ago | 15:50 |
| fray | ok | 15:50 |
| fray | does layer order matter still? | 15:51 |
| fray | I thought it did affect something | 15:51 |
| kergoth | layer order in bblayers affects bbpath, which affects .conf/.bbclass priority | 15:52 |
| bluelightning | fray: the layer order will affect how BBPATH gets constructed; but that's only about how conf/classes are found | 15:52 |
| fray | gotcha.. so I had it backwards.. | 15:52 |
| fray | layer order is the .conf/.bbclass and other 'files', while priority is recipe and bbappend | 15:52 |
| *** belen <belen!~Adium@134.134.137.71> has joined #yocto | 15:52 | |
| *** sameo <sameo!~samuel@192.55.54.41> has joined #yocto | 15:55 | |
| drasko | is there a way to force a bitbke to show messages of used commands during the fetch? I tried with -v, but I can not see much. | 15:56 |
| *** cascardo <cascardo!cascardo@nat/ibm/x-kecxioqsrhgdgwgi> has left #yocto | 15:57 | |
| ndec | drasko: looking at the log file? | 15:57 |
| ndec | or the 'run' script | 15:58 |
| drasko | ndec: no way for this to be printed on console during the execution? | 15:58 |
| *** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC | 15:58 | |
| *** zenlinux_ <zenlinux_!~sgarman@c-24-20-145-95.hsd1.or.comcast.net> has joined #yocto | 16:01 | |
| ndec | drasko: there -d for debug level. but i dont use it too much | 16:01 |
| drasko | ndec: I am looking at the log... | 16:01 |
| *** joeythesaint <joeythesaint!~jjm@128.224.252.2> has joined #yocto | 16:02 | |
| *** nrossi <nrossi!~nrossi@203.126.243.116> has quit IRC | 16:04 | |
| drasko | but I was mostly thinking about on-the-go information in the shell. For example, I am fetching the source and I'd like to see percentage of progress... | 16:05 |
| *** nrossi <nrossi!~nrossi@203.126.243.116> has joined #yocto | 16:05 | |
| drasko | And observe if download is stuck | 16:05 |
| fray | kergoth FYI, we're adding the -march via a BUILD_CFLAGS_append.. and for some reason it doesn't appear to be changing the checksum | 16:05 |
| fray | litterally if we detect a broken host.. we add the following to the local.conf -- BUILD_CFLAGS_append = " -march=<arch>" | 16:06 |
| ndec | drasko: about percentage of download, no i don't think this is possible. you can probably get to see the command, though if you print all commands your console will go crazy... but that's all you can do. | 16:07 |
| fray | we've wondered in the past as well about that.. but we end up shipping to our customers already downloaded sources.. so it turns out to not really be an issue | 16:07 |
| kergoth | huh, interesting. i just did a diffsig between two target sstates from our 32 bit and 64 bit automated builds and saw BUILD_CFLAGS change | 16:11 |
| * kergoth shrugs | 16:11 | |
| fray | I've got someone running a comparison for us.. | 16:12 |
| fray | he was doing CentOS 5 and Ubuntu 12.04 | 16:12 |
| fray | possible the _append misses the checksum for some odd rason | 16:12 |
| fray | er.. reason | 16:13 |
| *** ArunKumar <ArunKumar!~SnowWhite@219.91.250.135> has joined #yocto | 16:13 | |
| *** Stygia <Stygia!~gmpsaifi@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk> has quit IRC | 16:16 | |
| drasko | join #xenomai | 16:20 |
| kergoth | we're pulling in https://github.com/MentorEmbedded/meta-mentor/blob/master/classes/add_build_arch.bbclass at the moment. not pretty, but gets the job done for us for now | 16:21 |
| drasko | http://pastebin.com/t6HsyGPB | 16:26 |
| drasko | Anybody has idea why Yocto breaks EXTRA_OECONF += "CFLAGS=\"-march=armv7-a -mfpu=vfp3\" LDFLAGS=\"-march=armv7-a -mfpu=vfp3\" | 16:27 |
| drasko | in this way, adding ' between the words? | 16:27 |
| *** amarsman <amarsman!~marsman@52489B71.cm-4-1c.dynamic.ziggo.nl> has joined #yocto | 16:27 | |
| drasko | This confuses ./configure tool | 16:27 |
| fray | kergoth ya, what we have is an external script (that writes the local.conf).. | 16:27 |
| fray | it runs three checks.. does gcc work w/o -march=.. if not, does gcc -march=native work?, if not does -march=<host> work? | 16:28 |
| *** mr_science <mr_science!~sarnold@net-cf9a4e91.cst.impulse.net> has joined #yocto | 16:28 | |
| *** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 16:28 | |
| fray | hen sets the BUILD_CFLAGS_append = " -march=<value>" based on the results of the last two tests.. | 16:28 |
| fray | (if neither work, an error is generated) ;) | 16:28 |
| drasko | fray, no I explicitly added this | 16:29 |
| drasko | EXTRA_OECONF += "CFLAGS=\"-march=armv7-a -mfpu=vfp3\" LDFLAGS=\"-march=armv7-a -mfpu=vfp3\" | 16:29 |
| drasko | in the .bb file | 16:29 |
| *** gmacario <gmacario!~gmacario@maxlab.polito.it> has quit IRC | 16:29 | |
| fray | drasko sorry was talking about kergoths issue | 16:29 |
| fray | for the CFLAGS thing.. w/o the \" (inline quotes) the CFLAGS could get seperated into multiple "arguments" causing the shell to blow up | 16:30 |
| drasko | but it has \" | 16:32 |
| drasko | The whole line is : "CFLAGS=\"-march=armv7-a -mfpu=vfp3\" LDFLAGS=\"-march=armv7-a -mfpu=vfp3\" --build=x86_64-linux-gnu --host=arm-linux-gnueabihf" | 16:32 |
| drasko | as needed here : http://www.xenomai.org/documentation/xenomai-2.6/html/README.INSTALL/ | 16:32 |
| drasko | chapter 3.4. Building for ARM | 16:33 |
| fray | when it gets interpreted by the shell it comes out as: | 16:33 |
| fray | ...configure <values> CFLAGS="-march=armv7-a -mfpu=vfp3\" LDFLAGS="-march=armv7-a -mfpu=vfp3" --build=x86_64-linux-gnu --host=arm-linux-gnueabihf | 16:34 |
| fray | that is trying to pass specific CFLAG and LDFLAG vlaues into configure.. | 16:34 |
| fray | nothing more | 16:34 |
| drasko | but why? | 16:35 |
| drasko | line seems correct | 16:35 |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 16:35 | |
| fray | most likely to avoid configure from setting it's own (incorrect) CFLAGS and LDFLAGS.. but I don't know why for that specific app | 16:36 |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 16:36 | |
| drasko | "CFLAGS=\"-march=armv7-a -mfpu=vfp3\" LDFLAGS=\"-march=armv7-a -mfpu=vfp3\" --build=x86_64-linux-gnu --host=arm-linux-gnueabihf" | 16:36 |
| drasko | so, this line normally is correct? | 16:36 |
| fray | it's not incorrect.. if it does the right thing or not, I don't know for that app | 16:36 |
| drasko | for the app it works | 16:37 |
| drasko | I can compile by hand | 16:37 |
| drasko | however, bitbake separates "CFLAGS=\"-march=armv7-a -mfpu=vfp3\" LDFLAGS=\"-march=armv7-a -mfpu=vfp3\"" | 16:37 |
| drasko | into separate words | 16:37 |
| fray | I can only guess because configure was implemented "poorly" for cross compiling | 16:37 |
| drasko | hmmm | 16:37 |
| fray | that was an errant message.. sorry | 16:38 |
| fray | bitbake SHOULD pass the values of EXTRA_OECONF -directly- to the shell.. | 16:38 |
| fray | and the shell or configure may decided to expand it | 16:38 |
| drasko | adding these CFLAGS and LDFLAGS to configure - it is needed for build | 16:38 |
| fray | you can see what is passed by looking at the tmp/work/<arch>/<recipe>/<version>/temp/run.do_configure.<pid. | 16:38 |
| drasko | so, can I pass these values to bitbke for build? | 16:39 |
| drasko | maybe that will do the trick? | 16:39 |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has joined #yocto | 16:39 | |
| fray | the 'do_configure' task, calls into one of the many do_configure implementations.. assuming autotools is enabled.. it should eventually run configure w/ standard options and then ${EXTRA_OECONF} simply passed in.. | 16:40 |
| fray | the only way to see for sure is to look at the runfile | 16:40 |
| *** ArunKumar <ArunKumar!~SnowWhite@219.91.250.135> has quit IRC | 16:42 | |
| *** khem1 <khem1!~khem@99-57-140-209.lightspeed.sntcca.sbcglobal.net> has quit IRC | 16:43 | |
| drasko | here: http://pastebin.com/t6HsyGPB | 16:43 |
| drasko | on the line 18 looks like bitbake passes wrong parameters to configure after all | 16:44 |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 16:44 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 16:44 | |
| fray | values look fine, prior to the actual call into configure | 16:44 |
| fray | then something (shell?) is breaking it up | 16:45 |
| fray | sorry, I'm not sure why.. | 16:45 |
| drasko | from my point of view first call to the shell is on line 18 | 16:45 |
| drasko | first call to configure | 16:45 |
| drasko | before that bitbake was echoing what it will do | 16:46 |
| drasko | and reall call to configure happens on line 8 | 16:46 |
| fray | ya.. and something is wrong there | 16:46 |
| drasko | *18 | 16:46 |
| drasko | yes | 16:46 |
| fray | prior to that you can see that it's quoted | 16:46 |
| drasko | this is echo | 16:46 |
| fray | one possibility is to change the recipe to: | 16:46 |
| drasko | and then when configure is actually called | 16:46 |
| drasko | it is called wrongly | 16:47 |
| fray | EXTRA_OECONF += 'CFLAGS="...." LDFLAGS="..."' | 16:47 |
| fray | then you can avoid the \ | 16:47 |
| drasko | I am trying this right now | 16:47 |
| drasko | but... | 16:47 |
| drasko | however seems like bitbake bug | 16:47 |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 16:47 | |
| fray | bitbake doesn't do the parsing.. the shell does | 16:48 |
| drasko | which would say that bitbake passes line like this to configure: 'CFLAGS="-march=armv7-a' '-mfpu=vfp3"' | 16:49 |
| drasko | and hopes that shell will parse this correctly... | 16:50 |
| fray | no.. | 16:50 |
| fray | it -should- pass CFLAGS="..." to the shell.. | 16:50 |
| drasko | but on line 18 we see that it did not | 16:50 |
| fray | the shell should see the " and group until the next quote w/ no shell argument expansion | 16:50 |
| fray | correct.. it didn't do that.. I don't know why | 16:50 |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 16:51 | |
| fray | bitbake isn't expanding arguments.. it just writes out a run file.. (which is a shell script in this case).. you can view it directly looking at the run.do_configure.<pid> file.. | 16:52 |
| *** dany <dany!~Thunderbi@sestofw01.enea.se> has quit IRC | 16:52 | |
| fray | it then calls /bin/sh and executes the script | 16:52 |
| mr_science | moin | 16:52 |
| *** amarsman <amarsman!~marsman@52489B71.cm-4-1c.dynamic.ziggo.nl> has quit IRC | 16:56 | |
| *** amarsman <amarsman!~marsman@52489B71.cm-4-1c.dynamic.ziggo.nl> has joined #yocto | 16:57 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 16:59 | |
| drasko | OK, with single quetes it is advancing a bit | 16:59 |
| *** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has quit IRC | 17:00 | |
| drasko | however I have a probelm: includedir=/usr/include is automatically passed by bitbake | 17:00 |
| drasko | And then configure shouts : configure:2361: error: Using /usr/include as includedir is not supported. Please change your --prefix or specify another --includedir | 17:00 |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has quit IRC | 17:01 | |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has joined #yocto | 17:01 | |
| fray | your EXTRA_OECONF should pass then --include=${includedir}/${BPN} (for instance) this is fairly common | 17:02 |
| *** belen <belen!~Adium@134.134.137.71> has quit IRC | 17:07 | |
| *** _alex_kag_ <_alex_kag_!~alex_kag@178.126.178.164> has joined #yocto | 17:07 | |
| *** sameo <sameo!~samuel@192.55.54.41> has quit IRC | 17:08 | |
| *** belen <belen!Adium@nat/intel/x-wcivblipjhdlxpzv> has joined #yocto | 17:10 | |
| drasko | fray:this worked, thanks | 17:11 |
| drasko | can you tell me why, however? | 17:11 |
| fray | differnent programs take different interpretations of what --include= should contain.. | 17:11 |
| fray | generally it's supposed to be the location (on the target fs) of where to install the headers.. | 17:12 |
| drasko | and what is ${includedir}/${BPN}? | 17:12 |
| fray | many apps want their users directly in /usr/include, some automatically add a subdirectory themselves.. others (like this one) want the include directory to include a subdir | 17:12 |
| fray | includedir == /usr/include | 17:12 |
| *** ausxxh <ausxxh!~szaus18@198.199.104.214> has joined #yocto | 17:12 | |
| fray | BPN == recipe name | 17:12 |
| fray | so foo_1.0.bb -- ${BPN} = 'foo' | 17:13 |
| drasko | thanks a lot! | 17:13 |
| fray | no problem | 17:14 |
| ant_work | jwessel: any hint about embedding initramfs 'old-style'? | 17:18 |
| ant_work | jwessel: I can't even get the 'new-style' working :/ | 17:18 |
| jwessel | What is "the old style" ? | 17:18 |
| ant_work | embed on first pass | 17:19 |
| jwessel | Perhaps you can send me your local.conf | 17:19 |
| ant_work | I simply cannot trigger the bundle_initramfs task | 17:19 |
| jwessel | and build target and can fix it. | 17:19 |
| ant_work | is standard | 17:19 |
| ant_work | I'll try on qemuarm to ease up debugging | 17:19 |
| ant_work | note: is oe-core default, not Poky ! | 17:20 |
| jwessel | ok, I have an oe-core and several builds, but none error out, I imagine you set something or another in the local.conf to see the problem? | 17:21 |
| ant_work | not really | 17:21 |
| ant_work | I have tried to inject the cpio in our linux-yocto | 17:21 |
| ant_work | just adding the INITRAMFS variables | 17:21 |
| ant_work | and trying to embed core-image-minimal | 17:22 |
| ant_work | well, I did build core-image-base and the core-image-minimal wasn't even built | 17:22 |
| wmcdevel | ant_work: is the cpio something created as part of your build or a static file that you are adding? | 17:22 |
| ant_work | note we always build th ekernel in our bsp | 17:22 |
| ant_work | for every image | 17:23 |
| jwessel | For example, I have in my local.conf: | 17:24 |
| jwessel | INITRAMFS_IMAGE_BUNDLE = "1" | 17:24 |
| jwessel | INITRAMFS_IMAGE = "core-image-minimal-initramfs" | 17:24 |
| ant_work | hm.. I put th plain "core-image-minimal" | 17:24 |
| jwessel | What happens is that in the final stage the bzIamge gets re-linked to have the initramfs build in. | 17:24 |
| jwessel | I just do bitbake core-image-minimal in this case. | 17:25 |
| *** zenlinux_ <zenlinux_!~sgarman@c-24-20-145-95.hsd1.or.comcast.net> has quit IRC | 17:25 | |
| *** belen <belen!Adium@nat/intel/x-wcivblipjhdlxpzv> has quit IRC | 17:25 | |
| ant_work | jwessel: I have nothing against the two passes | 17:25 |
| jwessel | So you want to build core-image-minimal and then wrap it into a single binary? | 17:25 |
| ant_work | no, usually I embed a very very small cpio | 17:26 |
| ant_work | I just tried to reproduce what you were aiming for | 17:26 |
| ant_work | a linux-yocto embeding a big image | 17:26 |
| ant_work | whithout setting CONFIG_INITRAMFS_SOURCE in my cfg | 17:27 |
| jwessel | Well if you have a image recipe that creates your "small cpio" you can just specify it. | 17:27 |
| ant_work | jwessel: somehow only specifying INITRAMFS_TASK triggers the build | 17:27 |
| ant_work | but the do_bundle_initramfs seems not run so I don't have the copy_initramfs() -> my patch to kernel.bbclass | 17:29 |
| jwessel | The initramfs task is separate from the bundling. | 17:29 |
| jwessel | The kernel's do configure depends on the intramfs task. | 17:29 |
| ant_work | yes, that's the old, proven, way | 17:29 |
| jwessel | In that case you would need to specify where your image is. | 17:30 |
| jwessel | What you are asking for is the ability to specify a specific cpio image that got built in a specific location right? | 17:30 |
| ant_work | no | 17:30 |
| ant_work | I just want to specify the cpio image without path, like it was | 17:31 |
| ant_work | it is an image known to bitbake | 17:31 |
| ant_work | is in BBFILES | 17:31 |
| ant_work | the point is that it resides in deploy dir | 17:31 |
| ant_work | so in one way or other you have to copy it in /usr | 17:32 |
| ant_work | your code: | 17:32 |
| ant_work | cp ${DEPLOY_DIR_IMAGE}/${INITRAMFS_IMAGE}-${MACHINE}.$img ${B}/usr/. | 17:32 |
| jwessel | That is the part I was looking at. | 17:32 |
| ant_work | but in my tests, this funtion is never called | 17:32 |
| ant_work | the task is not run | 17:33 |
| jwessel | The function is only called if you have INITRAMFS_IMAGE and INITRAMFS_IMAGE_BUNDLE set. | 17:33 |
| ant_work | I'd expect too | 17:33 |
| ant_work | btw the image is | 17:34 |
| ant_work | http://cgit.openembedded.org/meta-openembedded/tree/meta-initramfs/recipes-bsp/images/initramfs-kexecboot-klibc-image.bb | 17:34 |
| ant_work | no renames, anything | 17:34 |
| ant_work | but EXTRA_IMAGEDEPENDS = "" | 17:34 |
| ant_work | jwessel: once at home I'll send you my full setup | 17:36 |
| ant_work | thx for your time | 17:36 |
| ant_work | bbl | 17:36 |
| *** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 17:36 | |
| *** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC | 17:41 | |
| *** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 17:43 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 17:52 | |
| *** padge_ <padge_!~quassel@83-64-248-68.inzersdorf.xdsl-line.inode.at> has quit IRC | 17:54 | |
| *** joaohf <joaohf!~joaohf@apolo.padtec.com.br> has quit IRC | 17:57 | |
| *** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto | 17:58 | |
| drasko | fray: interestingly, trying : "CFLAGS="-march=armv7-a -mfpu=vfp3" LDFLAGS="-march=armv7-a -mfpu=vfp3"" works | 17:59 |
| *** zz_ka6sox is now known as ka6sox | 17:59 | |
| drasko | so, Bitbake exports this to the shell CFLAGS="-march=armv7-a -mfpu=vfp3" | 17:59 |
| drasko | as seen in run.do_configure | 17:59 |
| drasko | However, doing "CFLAGS=\"-march=armv7-a -mfpu=vfp3\" LDFLAGS=\"-march=armv7-a -mfpu=vfp3\"" | 18:00 |
| drasko | Bitbake exports CFLAGS=\"-march=armv7-a -mfpu=vfp3\" | 18:01 |
| drasko | Looks like it takes first quote, goes to the last, and takes everything in between literally... | 18:01 |
| *** YoctoNewbie <YoctoNewbie!dc562822@gateway/web/freenode/ip.220.86.40.34> has joined #yocto | 18:04 | |
| YoctoNewbie | hi there | 18:05 |
| wmcdevel | quick question for the gurus ... I'm making a BSP for a board, and I have a custom ts.conf and tslib.sh that I want to be used when building for that board. My recipe is in meta-mini6410-bsp/recipes-graphics/tslib/tslib_1.1.bbappend ... should my ts.conf and tslib.sh go in meta-mini6410-bsp/recipes-graphics/tslib/mini6410, where mini6410 == ${MACHINE}? | 18:08 |
| kergoth | that's one option, yes, if you set FILESEXTRAPATHS_prepend := "${THISDIR}:" | 18:11 |
| *** joaohf <joaohf!~joaohf@apolo.padtec.com.br> has joined #yocto | 18:11 | |
| sgw_ | wmcdevel: I think you will want it in tslib/tslib/mini6410 and this FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:" take a look at the formfactor recipe for example | 18:13 |
| wmcdevel | cool. anything else I would need to override in the bbappend with "_mini6410 at the end? | 18:13 |
| wmcdevel | ok ... yeah, don't know why I didn't think of that - that's exactly the setup I'm trying to get. :) | 18:14 |
| wmcdevel | that's also how the xorg-xserver is done as well in the same folder ... hard to work in a terminal and not see the rest of the directory structure around you | 18:16 |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 18:28 | |
| *** joaohf <joaohf!~joaohf@apolo.padtec.com.br> has quit IRC | 18:30 | |
| wmcdevel | another odd question to throw out there ... is it possible to build more than one cross toolchain? The customized 2.6 kernel I have for this board will build and boot just fine if I use the 4.5.x version of gcc, but when I use the 4.7.2 that gets built by bitbake, it compiles but will not boot. | 18:37 |
| wmcdevel | at the moment, I'm simply building it separately and providing it as a binary. not a big deal, but was hoping to have the entire build done by yocto/oe. | 18:38 |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 18:39 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 18:42 | |
| *** joaohf <joaohf!~joaohf@apolo.padtec.com.br> has joined #yocto | 18:43 | |
| *** roric_ <roric_!~roric@c-7e72e455.213-3-64736c14.cust.bredbandsbolaget.se> has joined #yocto | 18:47 | |
| *** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC | 18:48 | |
| *** drasko_ <drasko_!~drasko@seg75-7-88-164-183-180.fbx.proxad.net> has joined #yocto | 18:49 | |
| *** YoctoNewbie <YoctoNewbie!dc562822@gateway/web/freenode/ip.220.86.40.34> has quit IRC | 19:07 | |
| *** wmcdevel <wmcdevel!~wmcdevel@barracuda.hmctelco.com> has quit IRC | 19:21 | |
| *** wmcdevel <wmcdevel!~wmcdevel@barracuda.hmctelco.com> has joined #yocto | 19:22 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:26 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 19:27 | |
| *** joaohf <joaohf!~joaohf@apolo.padtec.com.br> has quit IRC | 19:28 | |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 19:37 | |
| *** joeythesaint <joeythesaint!~jjm@128.224.252.2> has quit IRC | 19:40 | |
| *** joaohf <joaohf!~joaohf@apolo.padtec.com.br> has joined #yocto | 19:40 | |
| *** mr_science <mr_science!~sarnold@net-cf9a4e91.cst.impulse.net> has joined #yocto | 19:45 | |
| *** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 19:45 | |
| *** zeeblex <zeeblex!apalalax@nat/intel/x-paxdefzfsifvlsnv> has left #yocto | 19:53 | |
| *** nitink1 <nitink1!~nitink@134.134.139.70> has quit IRC | 20:06 | |
| *** nitink <nitink!nitink@nat/intel/x-gvhttbjekpukmxcl> has joined #yocto | 20:07 | |
| *** eren <eren!~eren@unaffiliated/eren> has quit IRC | 20:08 | |
| *** amarsman <amarsman!~marsman@52489B71.cm-4-1c.dynamic.ziggo.nl> has quit IRC | 20:13 | |
| *** amarsman <amarsman!~marsman@52489B71.cm-4-1c.dynamic.ziggo.nl> has joined #yocto | 20:17 | |
| *** amarsman <amarsman!~marsman@52489B71.cm-4-1c.dynamic.ziggo.nl> has quit IRC | 20:18 | |
| *** nitink <nitink!nitink@nat/intel/x-gvhttbjekpukmxcl> has quit IRC | 20:21 | |
| *** sameo <sameo!~samuel@192.55.54.42> has joined #yocto | 20:30 | |
| -YoctoAutoBuilder- build #258 of nightly is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly/builds/258 | 20:31 | |
| *** tor <tor!~tor@c-d567e655.125-1-64736c10.cust.bredbandsbolaget.se> has quit IRC | 20:35 | |
| *** ArunKumar <ArunKumar!~SnowWhite@219.91.250.135> has joined #yocto | 20:41 | |
| -YoctoAutoBuilder- build #42 of nightly-qa-extras is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-extras/builds/42 | 20:51 | |
| -YoctoAutoBuilder- build #2 of nightly-qa-pam is complete: Failure [failed Building Images Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-pam/builds/2 | 20:56 | |
| -YoctoAutoBuilder- build #2 of nightly-qa-skeleton is complete: Failure [failed Building Images Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-skeleton/builds/2 | 20:58 | |
| *** Krz_ <Krz_!c0c69725@gateway/web/freenode/ip.192.198.151.37> has quit IRC | 20:59 | |
| *** kspr <kspr!~kasper@x1-6-20-aa-4b-6e-41-6e.k573.webspeed.dk> has joined #yocto | 21:00 | |
| -YoctoAutoBuilder- build #271 of nightly-fsl-arm is complete: Failure [failed Building Images Building Toolchain Images Building Toolchain Images_1 Building Images_1 Building Images_2 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/271 | 21:00 | |
| -YoctoAutoBuilder- build #151 of minnow is complete: Failure [failed Building Images Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow/builds/151 | 21:01 | |
| kspr | Hi there :) | 21:02 |
| kspr | When creating a .bbappend file, does it append til previous revisions of .bbappend files, or does the .bbappend with the highest revision append directly to the .bb recipe? | 21:03 |
| -YoctoAutoBuilder- build #2 of nightly-qa-logrotate is complete: Failure [failed Building Images Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-logrotate/builds/2 | 21:03 | |
| -YoctoAutoBuilder- build #68 of eclipse-plugin-kepler is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/eclipse-plugin-kepler/builds/68 | 21:04 | |
| -YoctoAutoBuilder- build #307 of nightly-intel-gpl is complete: Exception [exception Building Images] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-intel-gpl/builds/307 | 21:04 | |
| -YoctoAutoBuilder- build #272 of nightly-oecore is complete: Exception [exception Building Images] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-oecore/builds/272 | 21:04 | |
| seebs | kspr, I'm not totally sure, but I think all the bbappends apply in some order. | 21:04 |
| *** ArunKumar <ArunKumar!~SnowWhite@219.91.250.135> has quit IRC | 21:04 | |
| kspr | seebs, ok, thanks. Trying to find some docs on this.. not easy :P | 21:05 |
| evanp | kspr: what do you mean by "revision of .bbappend"? | 21:05 |
| kspr | evanp, I mean, if I have multiple .bbappend files, with the PR incremented.. | 21:06 |
| -YoctoAutoBuilder- build #107 of buildtools is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/buildtools/builds/107 | 21:06 | |
| -YoctoAutoBuilder- build #298 of poky-tiny is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/poky-tiny/builds/298 | 21:06 | |
| evanp | kspr: I'm pretty sure the .bbappends apply in layer priority order | 21:06 |
| evanp | kspr: which has nothing to do with what variables they do or do not contain assignments to, of course | 21:06 |
| kspr | Okay, so if I create my own .bbappend for the kernel, it should apply to both existing .bbappends for the same kernel recipe in other layers, and lastly to the recipe itself | 21:07 |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 21:08 | |
| -YoctoAutoBuilder- build #296 of build-appliance is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/build-appliance/builds/296 | 21:08 | |
| -YoctoAutoBuilder- build #298 of nightly-x86-lsb is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-lsb/builds/298 | 21:09 | |
| -YoctoAutoBuilder- build #295 of nightly-non-gpl3 is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-non-gpl3/builds/295 | 21:09 | |
| evanp | kspr: my understanding is that, effectively, the .bb and all the .bbappends are concatenated together in layer priority order and parsed as if there were only one file | 21:09 |
| -YoctoAutoBuilder- build #293 of nightly-ppc-lsb is complete: Exception [exception interrupted] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc-lsb/builds/293 | 21:10 | |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has quit IRC | 21:10 | |
| kspr | evanp, okay, great. So it is the layer priority that defines the order, and not the PR | 21:10 |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has joined #yocto | 21:10 | |
| evanp | kspr: not sure if .bbappends in earlier layers affect .bbs in later layers.... | 21:10 |
| kspr | evanp, which means that an older PR could override a newer one, if the layer order dictates it. | 21:11 |
| kspr | evanp, okay :) | 21:11 |
| evanp | kspr: and it _is_ possible I don't have the right mental model of what's happening, but in my own experience it behaves as I described | 21:11 |
| evanp | kspr: yes, that's right | 21:12 |
| kspr | evanp, right, okay :) | 21:12 |
| *** roxell_ <roxell_!~roxell@c-853670d5.07-21-73746f28.cust.bredbandsbolaget.se> has quit IRC | 21:17 | |
| *** roxell <roxell!~roxell@linaro/roxell> has joined #yocto | 21:17 | |
| *** zecke <zecke!~ich@p5099b351.dip0.t-ipconnect.de> has quit IRC | 21:17 | |
| *** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ncrbeepnvazpxzhu> has quit IRC | 21:18 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has quit IRC | 21:19 | |
| *** drasko_ <drasko_!~drasko@seg75-7-88-164-183-180.fbx.proxad.net> has quit IRC | 21:20 | |
| *** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC | 21:23 | |
| *** roric_ <roric_!~roric@c-7e72e455.213-3-64736c14.cust.bredbandsbolaget.se> has quit IRC | 21:24 | |
| *** khem1 <khem1!~khem@natint3.juniper.net> has joined #yocto | 21:30 | |
| *** sameo <sameo!~samuel@192.55.54.42> has quit IRC | 21:34 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has joined #yocto | 21:41 | |
| *** Jay7 <Jay7!jay@2.94.131.64> has quit IRC | 22:00 | |
| *** el_robin <el_robin!~el_robin@sd-22215.dedibox.fr> has quit IRC | 22:02 | |
| kspr | Hmm, I have a problem configuring my kernel. Bitbake correctly copies my defconfig to .config in the do_unpack function. But then it creates a new .config in the do_configure step, and overwrites the one copied in do_unpack. | 22:03 |
| mranostay | qemu recipe get broken? | 22:04 |
| rburton | mranostay: pull, was fixed | 22:04 |
| * rburton blames emacs! | 22:04 | |
| *** el_robin <el_robin!~el_robin@2a01:e0b:1:124:3c7c:66ec:30c8:530f> has joined #yocto | 22:04 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 22:06 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 22:10 | |
| * mranostay converts rburton to the church of the vim | 22:10 | |
| *** mulhern <mulhern!~mulhern@c-67-186-188-203.hsd1.ma.comcast.net> has quit IRC | 22:11 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 22:11 | |
| *** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 22:12 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 22:12 | |
| rburton | mranostay: then you'll have patches that don't apply because there's random :w:w:q:q! in the middle | 22:13 |
| Crofton|work | rburton, would you like us to slap him around sum? | 22:14 |
| Crofton|work | some? | 22:14 |
| rburton | ha | 22:14 |
| *** tomz <tomz!~trz@c-68-53-177-94.hsd1.in.comcast.net> has quit IRC | 22:14 | |
| *** tomz <tomz!~trz@c-68-53-177-94.hsd1.in.comcast.net> has joined #yocto | 22:15 | |
| rburton | never encountered the militant arm of the emacs league ;) | 22:15 |
| *** ant_home <ant_home!~andrea@host77-44-dynamic.54-79-r.retail.telecomitalia.it> has joined #yocto | 22:18 | |
| *** tomz1 <tomz1!~trz@c-68-53-177-94.hsd1.in.comcast.net> has joined #yocto | 22:20 | |
| *** tomz <tomz!~trz@c-68-53-177-94.hsd1.in.comcast.net> has quit IRC | 22:20 | |
| mr_science | okay, dumb question time... | 22:24 |
| mr_science | where do i look for the packaging/versioning guidelines? | 22:24 |
| mr_science | ie, what's legal for a pre-release package version? | 22:25 |
| mr_science | something like libfoo_1.2.0_pre1 | 22:25 |
| mr_science | or should it be libfoo_1.2.0_rc1 | 22:26 |
| kergoth | best off doing 1.1.0+1.2.0_pre1 or so, so it sorts after 1.1.0 but before 1.2.0 | 22:26 |
| kergoth | afaik anyway | 22:26 |
| mr_science | it's undefined then? | 22:27 |
| *** vmeson <vmeson!~quassel@128.224.252.2> has quit IRC | 22:27 | |
| *** vmeson <vmeson!~quassel@128.224.252.2> has joined #yocto | 22:29 | |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has joined #yocto | 22:31 | |
| *** _alex_kag_ <_alex_kag_!~alex_kag@178.126.178.164> has quit IRC | 22:33 | |
| *** [simar|on] <[simar|on]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 22:34 | |
| *** agust <agust!~agust@pD9E2FED9.dip0.t-ipconnect.de> has quit IRC | 22:34 | |
| *** wmcdevel <wmcdevel!~wmcdevel@barracuda.hmctelco.com> has left #yocto | 22:38 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has joined #yocto | 22:40 | |
| otavio | mr_science: nooooooooooooooooooooooooooooo; emacs is the way! lol | 22:42 |
| otavio | oops; mranostay it was to you heh | 22:42 |
| otavio | ttfn | 22:43 |
| *** [simar|o1] <[simar|o1]!~simar@96.125.133.73> has quit IRC | 22:43 | |
| mr_science | lisp freak... | 22:47 |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 22:48 | |
| mr_science | damn, shot myself in the foot on that one... | 22:48 |
| *** dvhart <dvhart!~dvhart@134.134.139.72> has quit IRC | 22:49 | |
| mranostay | mr_science: every time you use emacs god kills a kitten :P | 22:51 |
| JaMa | and a dog when VIM is used? | 22:52 |
| *** nitink <nitink!~nitink@134.134.139.72> has joined #yocto | 22:52 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 22:52 | |
| rburton | sounds about right | 22:52 |
| JaMa | I don't care about animals, I just want to edit recipes | 22:52 |
| mr_science | so what happens if i use nano? does the universe implode? | 22:52 |
| rburton | no no, don't be silly | 22:53 |
| rburton | hamsters die | 22:53 |
| mr_science | good | 22:53 |
| JaMa | no, your pen1s gets a bit smaller :) | 22:53 |
| mr_science | not touching that one... | 22:53 |
| ant_home | mc can also open ipk archives and inspect the files | 22:54 |
| JaMa | that would be aweful | 22:54 |
| JaMa | ah you meant you're not touching nano editor, right? :) | 22:54 |
| * mranostay goes back to work | 22:54 | |
| * JaMa goes back to watching "0: gcc-4.8.1-r0 do_compile (pid 26914)" line | 22:54 | |
| JaMa | 1 beer on that it will fail again | 22:55 |
| JaMa | and it just did, /me wins a beer from his own fridge (sigh), someone building gcc for armv4t and seeing this? | 22:56 |
| JaMa | | /OE/shr-core/tmp-eglibc/work-shared/gcc-4.8.1-r0/gcc-4.8.1/gcc/cp/decl.c:7438:(.text.unlikely+0x2fa): relocation truncated to fit: R_ARM_THM_CALL against symbol `fancy_abort(char const*, int, char const*)' defined in .glue_7 section in linker stubs | 22:56 |
| JaMa | | /OE/shr-core/tmp-eglibc/work-shared/gcc-4.8.1-r0/gcc-4.8.1/gcc/cp/decl.c:7442:(.text.unlikely+0x318): additional relocation overflows omitted from the output | 22:56 |
| *** notinreallife <notinreallife!~notinreal@108-91-142-36.lightspeed.wlfrct.sbcglobal.net> has joined #yocto | 22:57 | |
| *** pidge_ <pidge_!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has quit IRC | 22:57 | |
| *** Gintaro_ <Gintaro_!~gintaro@geertswei.nl> has joined #yocto | 23:00 | |
| *** Gintaro <Gintaro!~gintaro@geertswei.nl> has quit IRC | 23:00 | |
| *** khem1 <khem1!~khem@natint3.juniper.net> has quit IRC | 23:00 | |
| seebs | JaMa, I have seen things like that, and the general answer we got was "you really can't compile things that large for old thumb, it just won't work". | 23:06 |
| seebs | I think. My memory is fuzzy. | 23:06 |
| -YoctoAutoBuilder- build #43 of nightly-qa-extras is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-extras/builds/43 | 23:07 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 23:07 | |
| JaMa | it looks like I've seen it too before, http://patches.openembedded.org/patch/49903/ is from 4 months ago | 23:08 |
| RP | kergoth: have you ever actually read the output of "bitbake --help" recently? Its scary :/ | 23:10 |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 23:11 | |
| RP | kergoth: things that are completely obsolete, plain wrong or using really old terminology. Thought I was done fixing it, then found more problems... | 23:11 |
| Crofton|work | no one reads docs :) | 23:12 |
| JaMa | RP: would you accept patch disabling thumb in gcc at this point? | 23:12 |
| wmat | ouch | 23:12 |
| RP | JaMa: for armv4 only? | 23:12 |
| JaMa | RP: I've sent RFC long time ago and now I've discovered that it's still needed (build running to verify) | 23:12 |
| JaMa | RP: yes, I can change it to armv4 only | 23:13 |
| JaMa | the problem is triggered only on armv4t | 23:13 |
| RP | JaMa: I'd need to see the patch tbh | 23:13 |
| RP | We've had a horrible set of build failures recently :( | 23:13 |
| JaMa | http://patches.openembedded.org/patch/49903/ this is the old version which doesn't apply anymore, but I'll test new one with added override for armv4 and send it to list | 23:14 |
| RP | Crofton|work: A new user correctly filed a bug complaining it was confusing | 23:14 |
| Crofton|work | I'd like to see us get past build failures and work on failures of running systems to do useful stuff | 23:14 |
| Crofton|work | :) | 23:14 |
| JaMa | if it builds, it's good; if it boots, it's perfect | 23:15 |
| RP | JaMa: oh, I see what you mean. If you make that armv4t only we can probably get it in... | 23:15 |
| JaMa | :) | 23:15 |
| RP | Crofton|work: a lot of the problem were the automated boot testing ;-) | 23:15 |
| Crofton|work | yep | 23:15 |
| Crofton|work | it is annoying when people build images that do not quite work out of the box | 23:16 |
| Crofton|work | ok gotta run and eat | 23:16 |
| Crofton|work | l8r | 23:16 |
| RP | well, I say were. I'm hoping this build is good | 23:16 |
| Crofton|work | w can save this idea for the next release | 23:16 |
| RP | Crofton|work: what, building working images? :) | 23:16 |
| Crofton|work | :) | 23:16 |
| mranostay | heh | 23:17 |
| JaMa | and for 1.7 we can sell them in paper boxes :) | 23:20 |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 23:23 | |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 23:24 | |
| ant_home | JaMa, all normal for armv4 here | 23:25 |
| ant_home | gn | 23:26 |
| *** ant_home <ant_home!~andrea@host77-44-dynamic.54-79-r.retail.telecomitalia.it> has quit IRC | 23:26 | |
| *** kspr <kspr!~kasper@x1-6-20-aa-4b-6e-41-6e.k573.webspeed.dk> has quit IRC | 23:26 | |
| *** Jay7 <Jay7!jay@2.93.246.220> has joined #yocto | 23:30 | |
| *** kmccombe <kmccombe!~kevinm@bas10-ottawa23-1128688106.dsl.bell.ca> has joined #yocto | 23:34 | |
| -YoctoAutoBuilder- build #3 of nightly-qa-skeleton is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-skeleton/builds/3 | 23:38 | |
| -YoctoAutoBuilder- build #3 of nightly-qa-pam is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-pam/builds/3 | 23:41 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has joined #yocto | 23:43 | |
| *** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has quit IRC | 23:46 | |
| *** [simar|on] <[simar|on]!~simar@96.125.133.73> has quit IRC | 23:46 | |
| *** [simar|o1] <[simar|o1]!~simar@206-248-139-195.dsl.teksavvy.com> has quit IRC | 23:47 | |
| *** [simar|on] <[simar|on]!~simar@69.166.24.103> has joined #yocto | 23:48 | |
| *** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 23:58 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!