Tuesday, 2013-08-20

*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto00:12
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC00:13
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto00:20
*** _julian_ <_julian_!~quassel@x2f03027.dyn.telefonica.de> has joined #yocto00:27
-YoctoAutoBuilder- build #226 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc-lsb/builds/22600:28
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has quit IRC00:29
kergothsometimes i wish i could append to a variable default value without modifying the flag directly00:30
kergothfoo ??+= or something equally twisted00:30
kergothwould be really handy for PACKAGECONFIG defaults00:30
*** _julian <_julian!~quassel@x2f12c27.dyn.telefonica.de> has quit IRC00:30
kergothwe should think about having a packageconfig backfill mechanism00:31
*** shoragan <shoragan!~jlu@2001:6f8:1178:2:219:99ff:fe56:8d7> has joined #yocto00:31
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has joined #yocto00:31
*** scot__ <scot__!~scot@> has quit IRC00:49
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC00:50
-YoctoAutoBuilder- build #269 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips-lsb/builds/26900:55
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto00:56
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC00:57
-YoctoAutoBuilder- build #257 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-multilib/builds/25701:00
-YoctoAutoBuilder- build #259 of nightly-non-gpl3 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-non-gpl3/builds/25901:12
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:15
*** jkridner <jkridner!~jkridner@nat/ti/x-canoznmotynanaea> has joined #yocto01:16
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto01:16
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:16
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:20
*** jkridner <jkridner!~jkridner@nat/ti/x-uiygidrggcecobzi> has joined #yocto01:25
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto01:25
*** Net147 <Net147!~Net147@60-241-181-112.static.tpgi.com.au> has joined #yocto01:25
*** Net147 <Net147!~Net147@60-241-181-112.static.tpgi.com.au> has quit IRC01:28
-YoctoAutoBuilder- build #251 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64-lsb/builds/25101:36
-YoctoAutoBuilder- build #114 of minnow is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow/builds/11401:46
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto01:50
-YoctoAutoBuilder- build #228 of nightly-fsl-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc/builds/22802:00
*** silviof1 <silviof1!~silviof@unaffiliated/silviof> has joined #yocto02:01
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC02:03
*** sameo <sameo!~samuel@> has quit IRC02:08
*** darknighte is now known as darknighte_znc02:26
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC02:28
*** _Lucretia_ <_Lucretia_!~munkee@pdpc/supporter/active/lucretia> has quit IRC02:28
-YoctoAutoBuilder- build #257 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc-lsb/builds/25702:32
-YoctoAutoBuilder- build #257 of nightly-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc/builds/25702:40
-YoctoAutoBuilder- build #260 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-lsb/builds/26002:49
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has quit IRC02:50
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has joined #yocto02:52
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto03:17
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC03:20
-YoctoAutoBuilder- build #98 of minnow-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow-lsb/builds/9803:26
-YoctoAutoBuilder- build #230 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/23003:48
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto04:17
*** tonghuix <tonghuix!~tonghuix@> has joined #yocto04:17
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC04:19
*** tonghuix <tonghuix!~tonghuix@> has quit IRC04:32
-YoctoAutoBuilder- build #260 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm-lsb/builds/26004:38
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto04:43
*** davest <davest!Adium@nat/intel/x-hcvgiizzucxikkyx> has joined #yocto04:43
*** wgao <wgao!~wgao@> has quit IRC04:48
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC04:48
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto04:50
*** wgao <wgao!~wgao@> has joined #yocto04:52
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto05:12
*** mihai <mihai!~mihai@> has joined #yocto05:13
*** davest <davest!Adium@nat/intel/x-hcvgiizzucxikkyx> has quit IRC05:25
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto05:32
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has joined #yocto05:47
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has joined #yocto05:47
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC05:59
-YoctoAutoBuilder- build #228 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/22806:08
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC06:09
*** zeeblex <zeeblex!apalalax@nat/intel/x-sgwkmykjrrllzsyw> has joined #yocto06:10
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto06:11
*** simar <simar!~simar@> has joined #yocto06:34
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:35
*** simar_ <simar_!~simar@> has quit IRC06:37
*** bluelightning <bluelightning!~paul@cpc13-lewi17-2-0-cust74.2-4.cable.virginmedia.com> has joined #yocto06:44
*** bluelightning <bluelightning!~paul@cpc13-lewi17-2-0-cust74.2-4.cable.virginmedia.com> has quit IRC06:44
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto06:44
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC06:44
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto06:45
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC06:50
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto06:51
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto06:52
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC06:52
*** tf <tf!~tomas@> has joined #yocto06:58
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC07:00
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto07:01
*** silviof1 is now known as silviof07:04
*** Zagor <Zagor!~bjst@sestofw01.enea.se> has joined #yocto07:09
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto07:09
*** mike <mike!c2881242@gateway/web/freenode/ip.> has joined #yocto07:12
*** mike is now known as Guest2732107:12
*** dany <dany!~Thunderbi@sestofw01.enea.se> has quit IRC07:13
*** tbn <tbn!~tbn@> has joined #yocto07:38
LetoThe2ndis there a way to completely reset a bitbake build? i just aborted one and cleared download/sstate afterwars, but now it seems to be confused07:39
*** tbn is now known as Guest1586207:39
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto07:43
*** agust <agust!~agust@p4FC46B48.dip0.t-ipconnect.de> has joined #yocto07:44
*** wgao <wgao!~wgao@> has quit IRC07:46
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC07:46
*** wgao <wgao!~wgao@> has joined #yocto07:46
*** _Lucretia_ <_Lucretia_!~munkee@pdpc/supporter/active/lucretia> has joined #yocto07:48
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:51
*** florian_kc is now known as florian07:51
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto07:52
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto07:56
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto07:59
ndecLetoThe2nd: what do you mean by reset?08:11
ndecyou can either remove 'tmp' folder and keep download and sstate, that's generally enough.08:11
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto08:12
ndecnext step is to remove sstate too, and you pretty much restart from scratch.08:12
LetoThe2ndndec: thanks *notes*08:14
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC08:16
ndecLetoThe2nd: sometimes when doing 'dev' i end up with messing up the 'sysroot' folder, especially when editing/changing recipes. in that case removing 'tmp' is the right thing to do.08:16
LetoThe2ndndec: ok.. think i get it (slowly)08:16
*** sameo <sameo!samuel@nat/intel/x-rqpxkfdpwqjwzexo> has joined #yocto08:18
*** simon_b <simon_b!c06dbe58@gateway/web/freenode/ip.> has joined #yocto08:19
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto08:21
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC08:22
erboanyone know if there's some documentation on the nativesdk.bbclass (other than reading the bbclass :) )?08:24
simon_bHello. I would like to add patches in a fixes layer (called meta-fixes) for dlt-daemon in meta-ivi. But bitbake only searches inside meta-ivi and in downloads.. Hence, it does find the bbappend, which lists the patches as part of the SRC_URI08:24
simon_bCan I append something to the search path?08:24
erbosimon_b: yes, using FILESEXTRAPATHS_prepend08:25
simon_berbo: thank you. How do I specifiy the bbappend'08:26
erbosimon_b: look at e.g. recipes-core-ivi/eglibc/eglibc_2.18.bbappend08:26
erbothe row FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" will make it look in the <dir of the bbappend>/<packagename> for files08:27
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto08:28
erbosimon_b: if it's a fix that affects everyone the meta-ivi maintainers are usually very helpful getting it fixed in meta-ivi08:28
*** honschu <honschu!~honschu@p549E8157.dip0.t-ipconnect.de> has joined #yocto08:30
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto08:30
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC08:34
*** Stygia <Stygia!~gmpsaifi@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk> has joined #yocto08:35
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto08:35
*** dany <dany!~Thunderbi@sestofw01.enea.se> has joined #yocto08:39
*** jeremiah <jeremiah!~jeremiah@194-237-7-146.customer.telia.com> has joined #yocto08:49
* jeremiah lurks08:49
B4gderhey jeremiah!08:50
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC08:50
jeremiahB4gder: Ohai!08:54
jeremiahGood to know you're here too!08:54
jeremiahNow I'm not as scared =D08:54
*** belen <belen!~Adium@> has joined #yocto08:59
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto09:02
*** bluelightning <bluelightning!~paul@> has joined #yocto09:07
*** bluelightning <bluelightning!~paul@> has quit IRC09:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:07
bluelightningmorning all09:08
*** alex_kag <alex_kag!~alex_kag@> has quit IRC09:31
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:37
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has joined #yocto09:54
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:14
*** B4gder <B4gder!~daniel@sestofw01.enea.se> has quit IRC10:17
*** B4gder <B4gder!~daniel@rockbox/developer/bagder> has joined #yocto10:17
*** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has joined #yocto10:18
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto10:28
*** simar_ <simar_!~simar@> has joined #yocto10:34
*** simar <simar!~simar@> has quit IRC10:38
*** e8johan <e8johan!~quassel@c-d463e455.16-3-64736c10.cust.bredbandsbolaget.se> has joined #yocto10:40
*** Guest27321 <Guest27321!c2881242@gateway/web/freenode/ip.> has quit IRC10:53
*** e8johan <e8johan!~quassel@c-d463e455.16-3-64736c10.cust.bredbandsbolaget.se> has quit IRC10:54
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC11:20
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto11:20
*** daBONDi_work <daBONDi_work!~david@> has joined #yocto11:23
BCMMwhen building kbd, i get "Exception: ExpansionError: Failure expanding variable SUMMARY, expression was ${SUMMARY} - Debugging files which triggered exception Exception: variable SUMMARY references itself!". i don't particularly mind if my distro doesn't have kbd; is there an easy way to tell bitbake not to include it in the image?11:32
daBONDi_workHi, i got a bootup problem, i generate an Image cpio.gz Image with "Intel Atom" and core-image-minimal-initramfs, then i copied it to a cf card with a syslinux bootloader, it boots up and Holds/Wait with follow Message "Waiting for removable media..." is there any special kind in syslinux to append the rootfs?11:32
BCMMas far as i can tell, the actual inclusion of kbd is several includes/inherits deep, so ideally i would like a way to say "don't build kbd even though it says you should", rather than having to edit some official bbclass11:33
BCMMdaBONDi_work: does yocto generate a syslinux config for you, or did you have to do that manually?11:34
rburtonBCMM: this may sound odd, but try bitbake kbd -ccleanall and then try your build again11:34
rburtonBCMM: i've seen that error happen very rarely/randomly11:34
BCMMrburton: thanks, i'll try that11:35
daBONDi_workbcmm: i build it manualy syslinux -i /dev... and make a syslinux config, LABEL xx kernel bzImage initrd ...gpio.gz11:35
BCMMrburton: in general, is there an easy way to just remove a package from my image, other than by modifying core classes or recipes?11:35
BCMMrburton: looks like that's working now, thanks. what's the diff between clean and cleanall?11:36
daBONDi_workbcmm i think it removes the kernel file also and rebuild it11:37
rburtonBCMM: there's a way in development now, but sometimes if you can chase where the package is getting pulled in you can see a way to remove it11:39
rburtonie kbd might be tied to "have a keyboard" machine feature11:40
BCMMrburton: huh, that's a pretty good idea actually11:40
BCMMit does have a keyboard, but i'm perfectly happy to just use the in-kernel keymap11:40
BCMMrburton: any idea how to do a build without udev?11:40
*** BCMM_ <BCMM_!~user@unaffiliated/bcmm> has joined #yocto11:41
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC11:41
*** BCMM_ is now known as BCMM11:41
rburtonBCMM: meta/recipes-core/packagegroups/packagegroup-core-boot.bb defines VIRTUAL-RUNTIME_dev_manager ?= udev11:43
rburtonso you could change that11:43
rburtoni expect setting it to "" would let you use a static /dev11:43
rburton(you can do that in your distro or local.conf)11:43
*** smartin_ is now known as smartin11:43
rburtonthen you get to play the game of all the other things that also want udev ;)11:44
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto11:49
*** el_robin_ <el_robin_!~el_robin@2a01:e0b:1:124:7ca1:158a:f7c4:103d> has quit IRC11:51
*** el_robin <el_robin!~el_robin@2a01:e0b:1:124:5dde:883e:3ed5:b46e> has joined #yocto11:53
BCMMrburton: the client switch above was me losing electricy and moving to a phone, so I'll try stuff when it comes back. thanks.11:58
*** jeremiah <jeremiah!~jeremiah@194-237-7-146.customer.telia.com> has quit IRC12:07
daBONDi_workwhen i want to build a linux Image to run completly from ram the core-image-minimal-initramfs is the way to go right?12:12
daBONDi_workor is it even possible to build it with yocto12:12
rburtondaBONDi_work: yeah, that works12:12
daBONDi_worki use "debirf" before to shrink down a debian dist12:12
rburtonthere's plenty of prior art for yocto-based products that are actually fairly large initramfs systmes12:13
daBONDi_worki need a small x86_64 Image12:14
daBONDi_workcurrent my debirf image has 70 MB12:14
daBONDi_workspace is not so critical its running on an full blown intel atom12:14
daBONDi_workwith 2gb ram12:14
daBONDi_workok i think i found it why my image not booting on system with cf card12:18
daBONDi_workCONFIG_PCMCIA in kernel config maybe missing12:18
BCMMdaBONDi_work: that is exactly wthan I'm trying to do (run with only an initramfs)12:19
daBONDi_workyou got it to work ? :D12:19
BCMMdaBONDi_work: still working on it, but kinda12:19
BCMMi've been using rpi-hwup-image from the unofficial raspberry pi bsp, then building an initramfs manually from the generated filesystem12:20
daBONDi_worki trying realy hard to understand the yocto structure, but my brain don't get it :-) maybe my brain missing some prerequesites12:20
BCMMso far it requires manually disabling udev to boot12:20
BCMMmaybe i should be basing what I'm doing on core-image-minimal-initramfs instead12:21
BCMMi guess i could still use the MACHINE from the pi bsp to get the right arm abi...12:22
daBONDi_workso prbly i need a selfmade bsp depennding on atom-pc and add up "CONFIG_PCMCIA", back to the yocto docs :-)12:22
*** scot__ <scot__!~scot@> has joined #yocto12:26
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC12:28
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto12:29
*** cfo215 <cfo215!~christos@mail.abemblem.com> has joined #yocto12:40
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC12:40
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto12:41
cfo215Hello everyone, I've been playing around with my own layers and after removing my layer from the bblayers.conf file bitbake seems to still include remnants from it in the build.  I keep getting "ERROR: Nothing RPROVIDES 'hello' "12:45
daBONDi_workcfo215: I think << yocto noob, make a bitbake -c cleanall12:46
daBONDi_workshould cleanup all prebuild packages and the sstate dir an rebuild all fresh12:47
bluelightningno, that's not the problem here12:47
bluelightningcfo215: you must still have a reference to "hello" somewhere in your configuration12:47
cfo215bluelightning: I'm reproducing it for you now.  I'll paste it along with my notes.12:53
daBONDi_workKernel find now my cf Card and put it under hda1 but got still "Waiting for removable media" :-/12:55
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC13:01
*** jkridner <jkridner!~jkridner@nat/ti/x-zfmqmrfnupykqyfu> has joined #yocto13:01
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:01
*** Guest15862 <Guest15862!~tbn@> has quit IRC13:10
*** tbn <tbn!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has joined #yocto13:10
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC13:11
*** tbn is now known as Guest9974013:11
*** Guest99740 <Guest99740!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has quit IRC13:12
*** rikroled <rikroled!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has joined #yocto13:12
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-qamcpnvsqfuvhrqn> has joined #yocto13:12
*** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has quit IRC13:13
*** Garibaldi|work1 <Garibaldi|work1!~andydalt@nat/cisco/x-phfzdwsnrkpwvusy> has quit IRC13:15
tfdaBONDi_work: you will probably have to make your own init script13:15
tfor your card is not getting correctly mounted13:17
tfthe init script looks for rootfs.img in /media/*/13:17
daBONDi_workim currently crawling the meta\rec..-core\initrdscripts\files/init-live.sh, here it stands13:17
daBONDi_workyeah thats the same iam reading13:17
daBONDi_workim trying now to put debugshell as kernel option so it breaks out of the udev script and bring me to shell13:18
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto13:18
daBONDi_workcan i overrite a script in an recipie from an other recipie ?13:19
lpapphi, when I am building 32 bit stuff with Yocto on a 64 bit host, do I need to have a lot of 32 bit libraries around or Yocto will build those for me?13:19
tfdaBONDi_work: make a bbappend13:19
tflpapp: should just work13:19
*** thaytan_ is now known as thaytan13:20
daBONDi_worktf: will the rootfs.img get copied to a ram root fs?13:20
*** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has joined #yocto13:20
daBONDi_workor will system mount the img itself13:21
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC13:21
tfdaBONDi_work: if you choose the 'boot' option, it creates a loop device and mounts the rootfs.img on the loop device13:22
tfthe rootfs.img is not a ram image13:22
daBONDi_workwhat 'boot' option?13:22
cfo215bluelightning: http://pastebin.com/3WwNnEtw13:22
erennew blog post: http://hambedded.org/blog/2013/08/20/waiting-for-removable-media-problem/13:23
tfdaBONDi_work: when the live image first boots, you get an option in the bootloader to either 'boot' or 'install'13:24
tfthe default is 'boot'13:24
daBONDi_worki make a syslinux bootloader config13:24
daBONDi_workand pass the initrd and kernel file13:24
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto13:24
tfdaBONDi_work: the init script that is waiting for removable media is part of the initrd13:24
tfbecause the initrd is just a small image that loads / installs the real image13:26
tfyou want to make a real image, with a normal init program instead, I think13:26
daBONDi_workahh now i get it13:26
daBONDi_workyes i want a system hows run completly from ram13:26
daBONDi_workafter start13:26
tfbasically, you want the rootfs from something line core-image-minimal13:27
tfbut build in the appropriate format for the ram disk13:27
daBONDi_workyes :-)13:27
tfwhich is cpio.gz, if I am not mistaken13:27
daBONDi_workyes thats what i was reading13:27
tfI don't think core-image-minimal builds cpio.gz by default13:28
bluelightningcfo215: run bitbake -e | less and search for hello (with / )13:28
tfyou need to enable that13:28
tfdaBONDi_work: plus you will need to make sure the ramdisk is big enough, there are some kernel params for that, iirc13:29
*** davest <davest!~Adium@> has joined #yocto13:29
cfo215bluelightning: will grep do?13:30
daBONDi_workwill check, thx tf! for clueing the thing with initrd!13:30
bluelightningcfo215: not really, we want to see how it's being set13:30
cfo215bluelightning: Will do.13:30
tfdaBONDi_work: you might want to create your own image recipe from something like core-image-minimal, and just change the IMAGE_FSTYPES in the recipe (see core-image-minimal-initramfs for that)13:32
*** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has quit IRC13:34
daBONDi_workso i make a copy of core-image-minimal-dev.bb(Inerits core-image Minimal.bb with dev-pkgs) put it in my own layer and add IMAGE_FSTYPE=cpio.gz to it, or something like that, will try tf THX13:37
cfo215bluelightning: http://pastebin.com/3yTjKHaS13:37
bluelightningcfo215: so basically on line 45 of your local.conf you are appending " hello"13:38
bluelightningcfo215: if you don't want that, remove it :)13:38
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC13:40
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC13:42
cfo215bluelightnight:  sure enough "IMAGE_INSTALL_append += "hello"... but now I'm really confused.  Should I use my layer from bblayers.conf or use IMAGE_INSTALL_append += "<recipe-name>" in local.conf?13:43
bluelightningcfo215: it's not really either-or13:44
bluelightningcfo215: two different things13:44
bluelightningcfo215: if you want to add a layer to your configuration, the path to it has to be added to conf/bblayers.conf13:44
bluelightningcfo215: the IMAGE_INSTALL_append is adding a package to be installed in your image13:45
bluelightningcfo215: I'm assuming you changed your bblayers.conf to remove the layer that contained the recipe that provided a "hello" package, but since you didn't remove the line from local.conf that added that package to your image -> error13:45
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC13:46
cfo215bluelightning:  Yes, that is correct.  So if I understand it correctly then if i have a recipe in my layer but don't included it in bblayers.conf I could still use a recipe from it by 'IMAGE_ISTALL_append'ing the recipe name.13:47
bluelightningcfo215: no, that's not right13:48
cfo215bluelightning: ic13:48
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto13:48
bluelightningcfo215: if a package is mentioned in IMAGE_INSTALL there must be a recipe providing it or you'll get the error you were getting13:49
bluelightningthere's not a lot more to it than that13:49
*** zeeblex <zeeblex!apalalax@nat/intel/x-sgwkmykjrrllzsyw> has left #yocto13:50
cfo215bluelightning: I guess I was thinking that if the recipe was in the sources folder, even though it's parent layer was not included in the bblayers.conf file that bitbake would find it.13:50
cfo215bluelightning: ... if I used IMAGE_INSTALL to make a reference to it.13:51
cfo215bluelightning:  Thanks for all your help!  I've got to get moving on...13:52
bluelightningno, IMAGE_INSTALL doesn't at all influence the recipes that are parsed13:52
cfo215bluelightning:  I'm still trying to get my head around all the configuration docs.  It will come... or my head will explode.  Either, I suppose, will work.13:54
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto13:54
*** cfo215 <cfo215!~christos@mail.abemblem.com> has quit IRC13:54
daBONDi_workhi, I am again :-) i got a recipie in my layer, in the bb file(its an new Image File), i have follow line: "require core-image-minimal.bb"13:55
daBONDi_work how can i include something from an other layer in an bb , bitbakes tells me it cannot finr core-image-minimal.bb13:55
Stygiabluelightning, Hey dude, I have a problem. I hope you have some advice.13:57
StygiaThe boss N' I are trying to update the recipes for our own code, which needs to be fetched from our private git repository13:57
StygiaWe have set it up so that he is authenticated via ssh, so no credentials are need to push or pull.13:58
*** kspr <kspr!~Kasper@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk> has joined #yocto13:58
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has quit IRC13:58
StygiaAnd now, we've added something like git://bitbucket.org/movis/movisboxsite;protocol=ssh;branch=master;user=git13:59
StygiaThis is what we've managed to find that doesn't generate errors outright...13:59
Stygiabluelightning, Okay, as I"m typing this, he actually managed it. :P So sorry to disturb you.13:59
ksprHey Stygia14:00
StygiaIt's that guy, BTW.14:00
bluelightningStygia: ok, happy to be your cardboard cutout developer ;)14:00
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto14:00
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has joined #yocto14:00
bluelightningdaBONDi_work: use the full path from the base of the layer14:02
bluelightningdaBONDi_work: i.e. require recipes-core/images/core-image-minimal.bb14:02
*** darknighte_znc is now known as darknighte14:02
*** alex_kag <alex_kag!~alex_kag@> has quit IRC14:04
daBONDi_workbluelightning: THX it works, was obvious, why iam not thinging about this :-), maybe i dont understand the system, do it combine all layers to 1 big thing?14:05
bluelightningdaBONDi_work: no, you just clone/extract each one wherever it makes sense, then point to them in the conf/bblayers.conf file under your build directory14:06
daBONDi_workok this is why the Path is only recipies-core/.. because meta = layer is in bblayers.conf and got submerged to the big Virtual bblayers.conf Directory/configfile/or wathever :-)14:07
daBONDi_worknow i get it, documentation is quite confusing :-), thx 4 your time14:11
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC14:12
Stygiabluelightning, Hah it wasn't quite like that, I genuinely didn't know, my boss' just managed to make it work after he asked me to come ask here.14:12
Stygiabluelightning, FYI you've made a noticable impact in our company's efforts to get profitable. :P14:12
Stygiabluelightning, We should pay you or something.14:12
bluelightningStygia: it's ok, I'm happy to help :)14:13
Stygiabluelightning, Yea I know. :)14:13
bluelightningStygia: the perl recipe contributions you're preparing will be more than sufficient recompense :)14:13
Stygiabluelightning, Heh yea I'm hoping so.14:15
StygialibX-something-perl, Artistic-1.0+ | GPL-1.0+, all this stuff is gradually getting there...14:15
Stygiabluelightning, This, titled libtaint-util-perl: http://pastebin.com/v4WnDKSq14:19
Stygiabluelightning, That's what you'd want commited, yea?14:19
bluelightningStygia: yep14:20
Stygiabluelightning, With section set to 'libs', but still.14:20
bluelightningStygia: FYI it seems like we inherited this naming scheme from debian, fwiw: http://packages.debian.org/search?keywords=libtaint-util-perl14:21
Stygiabluelightning, Yea, it does match the debian one very closely.14:21
*** tomz <tomz!~trz@c-68-53-177-94.hsd1.in.comcast.net> has joined #yocto14:22
*** tomz is now known as Guest1540814:23
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto14:26
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC14:29
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto14:29
*** BCMM <BCMM!~user@unaffiliated/bcmm> has quit IRC14:31
*** sameo <sameo!samuel@nat/intel/x-rqpxkfdpwqjwzexo> has quit IRC14:31
*** tonghuix <tonghuix!~tonghuix@> has joined #yocto14:34
*** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has joined #yocto14:45
*** sameo <sameo!~samuel@> has joined #yocto14:46
*** BSDCat <BSDCat!unique@calvin.idempot.net> has joined #yocto14:48
*** tonghuix <tonghuix!~tonghuix@> has quit IRC14:48
*** BCMM <BCMM!~user@unaffiliated/bcmm> has joined #yocto14:50
*** belen <belen!~Adium@> has quit IRC14:56
davestYPTM: davest is in the meeting!14:57
bluelightningYPTM: Paul Eggleton joined14:57
sgw_YTPM: Saul is on and will be leading this week14:57
sgw_YTPM: Is the Yocto Project Tech Meeing Con-Call Starting now14:58
sgw_Dial-in number: 1.972.995.777714:58
sgw_Participant passcode:   4200107814:58
*** belen <belen!~Adium@> has joined #yocto14:58
sgw_This call is open to all and the channel remains open to discuss any topic.14:59
BSDCatYTPM: MatthewW is on14:59
*** AlexG <AlexG!86bfdd4a@gateway/web/freenode/ip.> has joined #yocto14:59
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has quit IRC15:00
Guest15408YPTM: Tom Z on15:00
*** Guest15408 is now known as tomz215:00
belenYPTM: belen joined15:00
cristianiorgaYPTM: Cristian joined15:01
RPYPTM: Richard is on the call15:02
*** Corneliu <Corneliu!c0c6972c@gateway/web/freenode/ip.> has joined #yocto15:02
pidgeYPTM: Beth is on the call.15:02
CorneliuYPTM: Corneliu joined15:02
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has joined #yocto15:02
*** alex_kag <alex_kag!~alex_kag@> has quit IRC15:03
jmpdelos__YPTM: Polk is here15:03
frayYPTM: Mark is here15:03
*** jzhang-laptop <jzhang-laptop!~jzhang16@> has joined #yocto15:03
jzhang-laptopYPTM: jzhang's here15:03
zeddiiYPTM: Bruce will be late.15:03
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto15:04
nitinkYPTM: nitin on the call15:04
rburtonYPTM: ross on15:04
Zagorargh, what's the code?15:05
ZagorYPTM: Björn is on the call15:06
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC15:08
halsteadYPTM: Michael present.15:10
*** Ramana_ <Ramana_!0117d572@gateway/web/freenode/ip.> has joined #yocto15:11
rburtonpidge: can i grab you for 5 after the call?15:12
*** BCMM_ <BCMM_!~BCMM@unaffiliated/bcmm> has joined #yocto15:16
pidgerburton: sure15:17
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto15:18
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto15:19
lpapphi, how can I get a package list what core-image-minimal builds?15:20
*** sameo <sameo!~samuel@> has quit IRC15:20
JaMaenable buildhistory15:20
lpappwithout building.15:20
lpappI would like to see what it will build.15:20
lpappand judge if that is good enough for me.15:21
*** sameo <sameo!~samuel@> has joined #yocto15:21
*** belen <belen!~Adium@> has quit IRC15:22
rburtonlpapp: bitbake -g will give you the dependency tree, from which you can get the package list15:22
rburtonits not exactly what you want though, but it will work now15:22
lpapprburton: sounds like something to be reported.15:23
daBONDi_workhi i can boot the generated hddimg file from a cf card on the device, how i can boot it with syslinux and the rootfs is in ram so the system dont need the cfcard anymore, is that even possible ? can someone point me in a direction? thx15:23
lpappit would be nice for the users to be able to get the package list for an image, anytime, anywhere.15:23
*** belen <belen!~Adium@> has joined #yocto15:24
lpapprburton: is there a report about it, already15:26
*** jzhang-laptop <jzhang-laptop!~jzhang16@> has quit IRC15:27
*** eren <eren!~eren@unaffiliated/eren> has quit IRC15:28
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto15:28
*** ant_home <ant_home!~andrea@host59-63-dynamic.1-79-r.retail.telecomitalia.it> has joined #yocto15:30
lpapprburton: reported because I have not found anything quickly, https://bugzilla.yoctoproject.org/show_bug.cgi?id=502515:30
yoctiBug 5025: normal, Undecided, ---, saul.wold, NEW , Query the package list built by an image15:30
*** Ramana_ <Ramana_!0117d572@gateway/web/freenode/ip.> has quit IRC15:39
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC15:45
*** phdeswer_ <phdeswer_!~phdeswer@a88-113-104-180.elisa-laajakaista.fi> has joined #yocto15:46
*** jmpdelos__ <jmpdelos__!~polk@174-22-161-20.clsp.qwest.net> has quit IRC15:47
*** simon_b <simon_b!c06dbe58@gateway/web/freenode/ip.> has quit IRC15:49
*** jmpdelos <jmpdelos!~polk@174-22-161-20.clsp.qwest.net> has joined #yocto15:54
*** tonghuix <tonghuix!~tonghuix@> has joined #yocto16:07
*** jzhang-laptop <jzhang-laptop!~jzhang16@> has joined #yocto16:07
*** rikroled <rikroled!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has quit IRC16:08
bluelightningsgw_: re the PACKAGE_EXCLUDE functionality, you can see my comment here: http://lists.openembedded.org/pipermail/openembedded-core/2013-August/082760.html16:11
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC16:11
*** Corneliu <Corneliu!c0c6972c@gateway/web/freenode/ip.> has quit IRC16:11
sgw_bluelightning: I am reviewing fray's patch set, and the pending question is if we persist the excluded package list or not, correct?16:11
bluelightningsgw_: yes16:11
sgw_bluelightning: Yeah, I have read both your message and fray's reply16:11
frayya.. I don't think it is necessary myself.. but I can see why someone could expect it..16:12
bluelightningto my mind it makes sense that the excluded packages stay excluded; the user is free to disable the exclusions16:12
JaMaseebs: when you have a minute can you please check http://pastebin.com/C5Z1jYCg and suggest what else to try with pseudo?16:12
*** tonghuix <tonghuix!~tonghuix@> has quit IRC16:12
*** tonghuix <tonghuix!~tonghuix@> has joined #yocto16:13
sgw_bluelightning: I can see both sides of this as fray points out. I would tend to fall to leaving them transient since 2 of 3 package systems don't support persistence (at this time) and in most cases there won't be the data on the system anyway.16:14
sgw_bluelightning: it would take user action on a system with pkg-management enabled to install something new.16:15
bluelightningthe (common) case where the package manager and associated db are not installed don't enter into this discussion, this is about when they are16:16
sgw_bluelightning: fray: The question that comes to mind is will an update unwittingly cause a previously excluded patch to be included?16:16
sgw_or just the user action of adding a package?16:16
bluelightningif it were only a matter of the user explicitly installing items on the excluded list then this wouldn't be an issue16:16
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC16:17
*** hollisb <hollisb!~hollisb@nat-wv.mentorg.com> has joined #yocto16:17
sgw_bluelightning: so the question is: when updating a system, will a previously excluded patch be installed? Possibly due to a change in dependecies?16:18
bluelightningI don't see how it couldn't be16:19
*** tonghuix <tonghuix!~tonghuix@> has quit IRC16:20
*** mihai <mihai!~mihai@> has quit IRC16:21
*** jzhang-laptop <jzhang-laptop!~jzhang16@> has left #yocto16:21
*** sameo <sameo!~samuel@> has quit IRC16:21
sgw_yes package,16:22
*** dvhart <dvhart!dvhart@nat/intel/x-zdqnzfcwpeiepydz> has joined #yocto16:25
sgw_bluelightning: I am still leaning to leave it transient, as fray sez it's a limited case, this can be address at a later time if it becomes an issue, even if we wanted it to persist we could only make it work for rpm in the time frame we have.16:26
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC16:26
fraysgw_ sorry back..  ya..  a field upgrade could bring in exclude packages..16:27
fraybut I'm not sure if that is a good or bad thing..16:27
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto16:28
*** daBONDi_work <daBONDi_work!~david@> has quit IRC16:28
sgw_fray: that what this seems to hinge on, you have more background on deployments at this point, so you would have to answer that question.16:28
frayfor a desktop environment, it'd be a problem..16:28
frayfor an embedded environment, I'm not sure it is..16:28
fraythe people I know who want the exclusion stuff will likely NOT be doing package based field upgrades.. or at least not ones with packages available theyd on't want installed -- ever16:29
bluelightningso it kind of sounds like it doesn't matter one way or another for most cases16:30
sgw_As I think about this, I can see an edge case of excluding a package that provides a service and then it being installed and started, it uses resources (disk and cpu) which could have un-intended effects on the embedded systems, I could be talking may way the other direction!16:30
bluelightningin which case, we can merge the patches as-is, but I will be working on a follow-up series that makes it persist16:31
bluelightningso far I haven't heard a convincing argument as to why it should not16:31
sgw_bluelightning: given I have just started to look at think about this, I think that's a good direction to take. If we have a persistent patch set then we won't run into issues that might occur.16:32
sgw_fray I will pull in your updated patch set.16:33
kergothhttps://gist.github.com/kergoth/6283884 - any thoughts?16:36
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto16:36
bluelightningkergoth: do we need to add another class for this?16:37
fraysorry, having way way too many discussions at once.. catching back up16:38
bluelightningkergoth: I like the idea of centralising this, it's just that the number of classes we have is only going up :(16:38
*** AlexG <AlexG!86bfdd4a@gateway/web/freenode/ip.> has quit IRC16:38
fraybluelightning / sgw_ :  I can't say I have a compelling argument either way honestly..  the existing implementation is simply there to be consistent across package managers (to avoid suprises)..  and this met the 'easiest way to implement the solution'16:39
frayit's certainly easier on smart to store the exclusions then it was on opkg / deb16:40
kergothbluelightning: we could put it in cml1.bbclass, but then we'd need a way to opt-in to it, since we don't want to break existing recipes.16:41
kergothbluelightning: so.. options are limited afaict16:41
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto16:43
* kergoth shrugs16:44
bluelightningkergoth: looking at this, surely there's a way to make it not break anything...16:44
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto16:44
kergothi don't see how.16:45
kergothbut i'd certainly be interested to see it16:45
*** darknighte is now known as darknighte_znc16:46
sgw_fray: I think we have a plan moving forward, to start with your implementation, and then move to a persistent model, with you and bluelightning looking at the creating the persistent version16:46
kergothI guess you could make it not do anything if DEFCONFIG is unset, but still fail if the path doesn't exist, then alter kernel.bbclass to set DEFCONFIG to KERNEL_DEFCONFIG by default, for compat with existing recipes. but then there's the question of default behavior if neither defconfig nor kernel_defconfig are set by the recipe, does it trust the recipe knows what its doing, or does it default to ${WORKDIR}/defconfig the way kernel.bbclass does today16:47
fraysgw_ works for me16:47
sgw_fray: great16:47
kergoththe problem is, many kernel recipes prepend to do_configure to create .config and everything16:47
kergoththere's no way to inject code between that and the actual configuration16:47
* sgw_ back after a run16:47
kergothso there's no way to automatically do it without the recipe opt-ing in to this manner of configuration16:48
* kergoth goes to get food and caffeine and think about it16:48
frayin some ways, this type of change seems reasonable to me as a 'compatibility' break..16:48
*** alex_kag <alex_kag!~alex_kag@> has quit IRC16:48
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto16:48
fraylets get rid of the inconsistencies.. and explaint o people how to 'fix' the recipes that use the cml1 class16:48
fraymy only question though is right now appropriate for implementation, or does this need to wait for 1.6?16:49
bluelightningonly if it could be made to error out when using "incompatible" recipes16:49
fraybluelightning yes..16:49
fraydetectign that is a question...16:49
kergothi thought about making it chmod -w .config in prepare_config, so do_configure would error out if it tried to write to it, but that'd break use of minimal defconfigs w/ oldconfig filling in the gaps16:50
seebsJaMa: That does indeed look like files are getting created by statically-linked binaries. We've got basically nothing for that right now, except "rebuild binaries dynamically linked".16:51
seebsWould be interesting to run more comprehensive logging in some other way to see when those files are created, and what by.16:52
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC16:53
kergothaside: we should also dro pour "yes '' | oe_runmake oldconfig" bits in kernel.bbclass in favor of oe_runmake silentoldconfig (though it'd change the behavior from auto-enabling what's missing to using its default values, but that's much more sane anyway..)16:53
*** BCMM_ <BCMM_!~BCMM@unaffiliated/bcmm> has quit IRC16:54
kergother, no, nevermind that, i forgot about yes's argument behavior :)16:57
*** BCMM <BCMM!~user@unaffiliated/bcmm> has quit IRC17:05
*** Stygia <Stygia!~gmpsaifi@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk> has quit IRC17:06
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC17:13
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC17:14
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto17:15
JaMaseebs: ah I forgot to mention that this one was created with internal toolchain17:20
JaMaseebs: the same happens e.g. with procfs utils, I'm running another build from scratch to see if the list of modified file atributtes is the same17:22
seebsHmm. Interesting! Then we may actually have a case of something bypassing pseudo and moving files around. I suppose in theory you could try to run things with pseudo's logging on, it can be very verbose.17:22
seebsIt's at least a little disturbing for a file to be showing up in the database with 'no path', that sort of implies that it got added in some unexpected way.17:24
JaMaPSEUDO_DEBUG=5 should be enough?17:24
seebsDon't use PSEUDO_DEBUG, that's... useless, really.17:24
seebsI don't know off the top of my head how to export the right values, I think it might just be PSEUDO_OPTIONS=-l17:24
seebsPseudo has a logging mode where it creates a log database which records every operation.17:25
seebsThis is much more informative than the debug crud.17:25
*** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has joined #yocto17:25
seebsBTW, I have patches that improve the debug stuff a LOT.17:25
JaMaI'll try to create some smaller reproducer then image which takes 3 hours to build from scratch :)17:25
seebsMy background task is fixing it.17:25
seebsBasically, in my tree, PSEUDO_DEBUG=[letters] toggles various debugging flags.17:26
seebsSo you don't have to have verbose reporting on every aspect of everything to get information about IPC.17:26
JaMasounds nice17:31
*** belen <belen!~Adium@> has quit IRC17:31
seebsIn retrospect, I have no idea why I didn't do it that way in the first place.17:32
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto17:32
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC17:33
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto17:34
*** cjosephson <cjosephson!~cjosephso@> has quit IRC17:35
*** cjosephson <cjosephson!~cjosephso@> has joined #yocto17:37
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC17:37
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto17:38
*** ka6sox is now known as zz_ka6sox17:47
*** e8johan <e8johan!~quassel@c-d463e455.16-3-64736c10.cust.bredbandsbolaget.se> has joined #yocto17:48
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC17:51
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has quit IRC17:54
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto17:58
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto17:58
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto18:14
*** ftonello <ftonello!~felipe@wsip-70-183-20-162.oc.oc.cox.net> has joined #yocto18:16
*** zz_ka6sox is now known as ka6sox18:20
*** smartin <smartin!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto18:20
sgw_khem: around?18:23
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:25
*** amarsman <amarsman!~marsman@90-145-17-249.wxdsl.nl> has quit IRC18:26
*** davest <davest!~Adium@> has quit IRC18:29
*** challinan <challinan!~challinan@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC18:31
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto18:34
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC18:35
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC18:36
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC18:38
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto18:43
*** challinan <challinan!~challinan@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto18:53
*** swex__ <swex__!~swex@> has joined #yocto18:58
*** swex_ <swex_!~swex@> has quit IRC18:58
mranostayhowdy challinan19:04
challinanhey mranostay how are ya?19:05
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC19:07
mranostayoh it is going19:08
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto19:09
*** cjosephson <cjosephson!~cjosephso@> has quit IRC19:11
*** cjosephson <cjosephson!~cjosephso@> has joined #yocto19:12
*** cfo215 <cfo215!~christos@mail.abemblem.com> has joined #yocto19:13
challinanmranostay: you going to ELC-E?19:13
_alex_kag_hello, does qt4e-demo-image broken? it buiding good, but then i run it - qtdemoE -qws is segmentation fault19:17
*** amarsman <amarsman!~marsman@195-241-212-143.ip.telfort.nl> has joined #yocto19:18
_alex_kag_i try run it on imx6qsabresd19:19
cfo215_alex_kag_: try '$ file qtdemoE' to see if it compiled properly for your target.  It should give you something like " ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, stripped" if it compile correctly for your target.  my target is ELF 32-bit LSB on ARM processor.  Also, make sure all your required libraries are on the target (if using shared libraries).19:26
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC19:27
JaMaseebs: sorry to interrupt you again, but where should I find logs from PSEUDO_OPTIONS=-l? pseudo.log and logs.db looks the same as before19:28
seebsThe logs.db should be huge. If they're not, it's quite possible that, say, bitbake is helping by stripping PSEUDO_... oh.19:29
seebsI should perhaps point out that my memory for words is occasionally quite bad, and it never hurts to check what I say against the man page. :)19:29
JaMaI've used sysroots/x86_64-linux/usr/bin/pseudo --help | grep -i PSEUDO without any output :)19:31
*** BSDCat <BSDCat!unique@calvin.idempot.net> has left #yocto19:31
JaMabtw not sure if it's intentional but -l is described as long and later as verbose format19:31
_alex_kag_cfo215: thanks, tomorrow will test19:34
seebsIt's not --help. There is an actual man page.19:36
cfo215how do you extend IMAGE_FEATURES += "dev-pkgs" to include a custom development package from a custom layer?  I tried finding dev-pkgs* but it must not be a .bb file or *.inc file.19:36
seebsSee pseudo.1 in the pseudo directory.19:36
JaMaseebs: yes I'm reading it now19:38
JaMaseebs: --help is a bit more accessible when using pseudo from OE19:38
seebsYes. Although currently pseudo doesn't actually have *any* long options, so all it's doing is displaying the default usage stuff because - isn't a valid option.19:39
seebsThe man page is probably too large to be encapsulated in --help output, but I could probably improve it some.19:39
JaMastrassek_: btw there is also many entries in pseudo.log about path mismatch19:40
JaMapseudo: path mismatch [2 links]: ino 49477724 db '/OE/work/i586-oe-linux/perl/5.14.3-r1/pkgdata/runtime/perl' req '/OE/pkgdata/i586-oe/runtime/perl'.19:40
seebsWhere is -l described as "long" and later as "verbose" format? I am not sure what you were looking at.19:40
JaMaI belive it's caused by using hardlinks19:40
*** agust <agust!~agust@p4FC46B48.dip0.t-ipconnect.de> has quit IRC19:40
seebsYes. pseudo is okay with those, they're advisory warnings -- thus  the "path mismatch [2 links]".19:41
seebsIt is suspicious but those aren't regarded as fatal errors, in general.19:41
JaMafrom --help:19:41
JaMa      --format=WORD          across -x, commas -m, horizontal -x, long -l,19:41
JaMa                               single-column -1, verbose -l, vertical -C19:41
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto19:41
seebs... Which program's --help is that? It does not look familiar to me.19:42
JaMapseudo --help19:43
JaMawell pseudo version used in dylan release19:43
seebsThose options aren't at all related to pseudo, but I have no idea what they ARE from.19:44
JaMaomg please ignore it :)19:44
seebsLooks like diagnostics from ls.19:44
JaMaI forgot leading "ls" before path to pseudo19:44
* JaMa needs more coffee or less rum or something19:44
seebs... And of course, rather than "ls path --help" telling you that there's no file --help, it "helpfully" interprets the option anyway.19:45
seebsI hate that behavior.19:45
JaMabtw the list of files with different file attributes is changing a bit with each rebuild from scratch, I'll let you know if I find something interesting in logs.db after few hours19:47
seebsIt really feels like something is moving files around that pseudo was tracking, and doing so outside of pseudo.19:51
seebsEither statically-linked binaries, or a syscall I don't know about yet, or just some harmless bookkeeping task that needed a fakeroot qualifier and didn't get it.19:51
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC19:53
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto20:03
*** cfo215 <cfo215!~christos@mail.abemblem.com> has left #yocto20:03
*** eren <eren!~eren@unaffiliated/eren> has quit IRC20:06
*** davest <davest!Adium@nat/intel/x-kgltwapxlxccutav> has joined #yocto20:07
*** e8johan <e8johan!~quassel@c-d463e455.16-3-64736c10.cust.bredbandsbolaget.se> has quit IRC20:12
*** smartin__ <smartin__!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto20:12
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC20:13
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC20:14
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has quit IRC20:20
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC20:22
seebsSo, I think I have meta-sourcery working with multilibs, too, now.20:24
seebsIt turned out to be stunningly easy, except for the 45 minutes I spent unable to figure out why nothing at all was working.20:25
kergothi hate those days20:25
seebsAnswer: I had some buggy code, I wanted to run bitbake -e to examine some values, and I had put a "return" above a large hunk of necessary functionality so that bitbake -e would work, then forgot to remove it.20:25
seebsOnly got it when I did a "git diff" to look at all the changes in case I'd done something obviously wrong. I had.20:25
kergothugh, yes, ConfigParsed time sanity checking sucks20:26
seebsI am not sure at all whether my multilib handling is right.20:26
seebsIt's basically a check for MULTILIB_VARIANTS, and if that's set, for each one, get a new d.createCopy(), get DEFAULTTUNE_virtclass-multilib-%s, set DEFAULTTUNE to that, finalize, and invoke populate_toolchain_links on that.20:27
seebsI feel that this is almost certainly overengineered, but I am not sure of a simpler way.20:27
seebs... My build failed due to a kernel source file producing a warning, which was treated as an error.20:28
seebsOriginal plan: Use our XLP-based BSP to quickly confirm that I'm generating the right name for the multilib subdirectory, which I need to make a one-line change.20:29
seebsActual outcome: Roughly 9 hours of debugging how meta-sourcery interacts with multilibs.20:29
seebs... But I did successfully make the one-line change, so that's a win.20:31
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto20:32
*** bbp <bbp!2e412846@gateway/web/freenode/ip.> has joined #yocto20:42
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC20:54
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto20:57
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC20:58
*** tlwoerner_ <tlwoerner_!~tlwoerner@dsl-67-55-9-50.acanac.net> has joined #yocto21:05
*** tlwoerner_ <tlwoerner_!~tlwoerner@linaro/tlwoerner> has joined #yocto21:05
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:06
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC21:07
*** Liang <Liang!~Leon@> has joined #yocto21:13
*** Liang <Liang!~Leon@> has quit IRC21:14
*** LiangC <LiangC!~Leon@> has joined #yocto21:15
pidgeHi LiangC21:21
LiangCHi Beth?21:21
LiangCLooking forward to working with you:)21:22
pidgeditto. we'll take this to pm.21:23
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has quit IRC21:23
*** nerdboy <nerdboy!~sarnold@dsl-66-59-252-223.static.linkline.com> has joined #yocto21:27
* mranostay yawns21:31
RPkhem: around?21:34
seebsRP: Should I resubmit my proposed patch to improve the reporting when shell commands cause an exit due to set -e?21:35
*** nerdboy <nerdboy!~sarnold@dsl-66-59-252-223.static.linkline.com> has quit IRC21:36
*** nerdboy <nerdboy!~sarnold@dsl-66-59-252-223.static.linkline.com> has joined #yocto21:38
RPseebs: I'll merge it, it just about still applies21:39
seebsOkay, thanks!21:40
kergoththat'll be handy21:41
kergothjust yesterady i got bit by a quietly failing task :)21:41
frayif it saves time, we have a version that applies to bitbake as of about a week ago21:41
seebsThe worst of those we ever had involved a tar command which wasn't actually failing silently.21:43
seebsIt was emitting an error message followed by several thousand lines of non-diagnostic normal output.21:43
seebsSo we didn't *see* the error message, we just saw a sudden exit for no reason. A patch similar to this at least told us tar was exiting with a non-zero status.21:43
RPits in21:44
kergothhuh, this kernel build is putting the generated dtbs in arch/arm/boot/dts/, not in arch/arm/boot/ the way linux-dtb.inc is expecting21:44
kergothcausing a do_install failure. wonder if thats specific to this bsp kernel or what, weird21:44
RPkergoth: I think a patch just landed for that21:44
kergothah, indeed, didn't see that21:46
RPDoes anyone see any value in the current gcc .inc files or are we better collecting things into less files?21:47
RPI'm finding it a twisty maze and I doubt anyone else finds it easier :/21:47
seebsI'd have to double-check, but I *think* we may be using some of that in our build stuff. Or may not be.21:48
seebs... Woah, there are a LOT more of those than I realized.21:48
seebsI would guess that we could get away with fewer.21:49
kergothi'm not big fan of .inc use in recipes anymore for that reason, it definitely gets confusing21:49
kergoththough i'd like to resurrect my vim bits that made 'gf' work on required/included/inherited files in recipes21:50
RPThere are some simple no brain fixes like killing gcc-cross4.inc which I have a patch for21:50
kergothcause that was awesome when it worked (back when BBPATH was in the env)21:50
RPbut do we merge the gcc-configure-* and gcc-package-*  ?21:50
sgw_RP: did you grab the other half of otavio's DISTRO_FEATURES for poky.conf?21:51
RPgcc-configure-common and gcc-common ?21:51
RPsgw_: no, not yet21:51
kergothRP: for what its worth, there might be value in keeping packaging separate for things like external toolchains, if at any point we want to be able to split out independent recipes for things21:52
kergothcourse thats more important for eglibc than gcc :)21:52
RPkergoth: right, eglibc is a very different situation. If you look at the gcc-package bits, its mostly the do_install functions :/21:53
kergothahh, right, in that case, likely just adds confusion21:53
RPkergoth: that is my current feeling, the split is currently rather confused...21:54
RPsgw_: The reason I haven't done anything with the patch is I can never find the thing21:55
RPsgw_: If people sent them to the right mailing lists, I might do a better job of that21:55
sgw_RP: it went to both poky and oe-core might have been sucked into one filter or the other21:57
RPsgw_: the resend went to OE-Core only afaict22:00
RPI'd marked the original as obsolete which makes it effectively disappear22:01
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto22:02
*** amarsman <amarsman!~marsman@195-241-212-143.ip.telfort.nl> has quit IRC22:05
ftonellodoes any one had any problem with python linkage while building perf?22:05
bluelightningftonello: failure at do_rootfs?22:09
ftonellobluelightning: no, while linking22:10
bluelightningok, then no, maybe someone else has22:10
ftonellostuff like /usr/src/kernel/tools/perf/scripts/python/Perf-Trace-Util/Context.c:87: undefined reference to `Py_InitModule4'22:10
ftonelloI will just disable it, but it's weird because I have python installed.. probably a bug in the recipe22:12
*** darknighte_znc is now known as darknighte22:16
*** smartin <smartin!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC22:18
*** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has quit IRC22:22
*** jkridner <jkridner!~jkridner@nat/ti/x-qquxzzqpyelzykbc> has joined #yocto22:30
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto22:30
*** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has joined #yocto22:34
*** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has quit IRC22:36
*** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has joined #yocto22:36
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto22:39
kergothso, i've seen host compiler ICE's building qemu 1.5.0 in the past, but we found bumping to 1.5.1 sidestepped the issue22:40
kergoththoughts on updating qemu in the core?22:40
*** phdeswer_ <phdeswer_!~phdeswer@a88-113-104-180.elisa-laajakaista.fi> has quit IRC22:42
-YoctoAutoBuilder- build #137 of nightly-qa-systemd is complete: Failure [failed Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-systemd/builds/13722:48
*** cfo215 <cfo215!~christos@mail.abemblem.com> has joined #yocto22:48
cfo215anyone out there know what the default password is for the Angstrom 2012 core-image-minimal build.  I've tried all the obvious ones.  I thought it was supposed to be blank.22:49
kergothtry the angstrom channel22:50
cfo215How/where do you set the default password for the yocto core-image-minimal build?22:51
*** LiangC <LiangC!~Leon@> has quit IRC22:54
ant_homecfo215, you probably want to enable # "debug-tweaks" as EXTRA_IMAGE_FEATURES22:55
ant_homecheck out local.conf examples22:55
cfo215ant_home: thanks I'll look at that.  Thank you.22:55
*** cfo215 <cfo215!~christos@mail.abemblem.com> has left #yocto22:56
*** cfo215 <cfo215!~christos@mail.abemblem.com> has joined #yocto22:56
*** cfo215 <cfo215!~christos@mail.abemblem.com> has left #yocto22:59
*** cfo215 <cfo215!~christos@mail.abemblem.com> has joined #yocto22:59
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto23:07
*** cfo215 <cfo215!~christos@mail.abemblem.com> has left #yocto23:07
*** smartin__ <smartin__!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC23:08
*** zenlinux_ <zenlinux_!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has joined #yocto23:17
*** nitink <nitink!nitink@nat/intel/x-mnwgosekvtysksja> has quit IRC23:19
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has quit IRC23:20
-YoctoAutoBuilder- build #255 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64/builds/25523:22
*** hollisb <hollisb!~hollisb@nat-wv.mentorg.com> has quit IRC23:30
*** dvhart <dvhart!dvhart@nat/intel/x-zdqnzfcwpeiepydz> has quit IRC23:32
*** ant_home <ant_home!~andrea@host59-63-dynamic.1-79-r.retail.telecomitalia.it> has quit IRC23:32
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC23:35
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC23:37
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:38
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC23:50
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto23:52

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