Wednesday, 2013-07-17

*** Jefro <Jefro!> has joined #yocto00:01
lpapp_hmm, interesting that no one has written a ninja class yet.00:04
sgw_ftonello: no, if you are using dylan or master, it will notice the signature difference and compute the correct dependencies when the image is created00:05
*** davest <davest!~Adium@> has joined #yocto00:09
ftonellosgw_: thanks00:09
*** mulhern <mulhern!> has joined #yocto00:13
*** jbaxter <jbaxter!> has quit IRC00:19
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC00:20
*** _julian <_julian!> has joined #yocto00:25
*** _julian_ <_julian_!> has quit IRC00:25
*** mulhern <mulhern!> has quit IRC00:30
ftonellois this statement, RDEPENDS_${PN}_append_pulseaudio-server = " package1 package2", going to append package1 and package2 to RDEPENDS_pulseaudio-server ?00:34
ftonelloso basically I'm adding those new packages as pulseaudio-server package run time depend?00:34
sgw_ftonello: what you want to do is RDEPENDS_pulseaudio-server += "package1 package2"00:39
ftonellosgw_: but can I do that in any recipe?00:40
ftonellothe ${PN} is not pulseaudio for example00:41
ftonelloI want to add the extra dep from a nother recipe00:41
sgw_add the extra dep for what package?  or only when pulseaudio-server is used?00:42
ftonellothe thing is that00:46
ftonelloadd the extra dep for pulseaudio-server for example00:47
ftonellois that possible?00:47
ftonellolike, if I install this package, add this dep to pulseaudio-server as well00:47
sgw_ftonello: from  another recipe or a bbappend?00:47
ftonellosgw_: another recipe00:48
*** scot__ <scot__!> has quit IRC00:49
sgw_ftonello: you could add a pulseaudio.bbappend to your layer that RRECOMMENDS the package your building, that will cause it to be installed if it's build and available in the package feed.00:50
ftonellook.. i need to do in a bbappend then00:50
sgw_you could also try the RDEPENDS_pulseaudio-server_append = " pacakge1 package2" in your recipe, but I have not really seen recipes do that, so I don't really want to reccommend it.  (remember the leading space, since append does not add spaces while += does).00:54
*** mulhern <mulhern!> has joined #yocto00:58
*** mulhern <mulhern!> has quit IRC01:05
*** sameo <sameo!~samuel@> has quit IRC01:07
*** Jefro <Jefro!> has quit IRC01:09
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:16
*** zenlinux <zenlinux!> has quit IRC01:26
*** zenlinux <zenlinux!> has joined #yocto01:45
ftonellosgw_: yes.. i will test and see01:58
sgw_ftonello: sure, thanks for those patches, they are appreciated02:00
*** silviof1 <silviof1!> has joined #yocto02:05
*** silviof <silviof!> has quit IRC02:07
*** mitz <mitz!> has quit IRC02:26
*** mitz <mitz!> has joined #yocto02:28
*** JimNH3 <JimNH3!> has joined #yocto02:28
*** JimNH2 <JimNH2!> has quit IRC02:31
*** zenlinux <zenlinux!> has quit IRC02:31
*** zenlinux <zenlinux!> has joined #yocto02:32
*** JimNH2 <JimNH2!> has joined #yocto02:33
*** JimNH3 <JimNH3!> has quit IRC02:36
*** mitz <mitz!> has quit IRC02:45
*** Garibaldi|work <Garibaldi|work!> has joined #yocto02:46
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-xhrdyzbwwjpwwuxz> has joined #yocto02:46
*** fce84x0dev <fce84x0dev!~fce84x0de@> has joined #yocto02:48
fce84x0devafter I add a new package in the local .conf ,  (for example add ethtool) how can I use bitbake to rebuild the new image including the new package? I tried "bitbake core-image-basic", but can't find the added package after the target  boot02:50
kergoth`what did you change in local.conf?02:53
kergoth`bitbaking the image should be sufficient.02:53
*** andyross <andyross!> has joined #yocto02:53
fce84x0devadd "CORE_IMAGE_EXTRA_INSTALL = "ethtool "02:54
fce84x0devhow to check if any wrong configuration or typing in the local.conf with bitbake?02:56
-YoctoAutoBuilder- build #187 of nightly-oecore is complete: Exception [exception Running Sanity Tests] Build details are at
*** agherzan <agherzan!~agherzan@> has joined #yocto03:12
agherzanHello all03:12
agherzanonce sepbuildir is inherited is there anyway i can deactivate it for a certain package?03:12
agherzanB = "${S}" has no effect as i see...03:12
agherzanIt is just ignored03:13
-YoctoAutoBuilder- build #208 of nightly-arm is complete: Success [build successful] Build details are at
*** mitz <mitz!> has joined #yocto03:24
*** agherzan <agherzan!~agherzan@> has quit IRC03:27
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-xhrdyzbwwjpwwuxz> has quit IRC03:35
*** agust <agust!> has joined #yocto03:43
*** klinger <klinger!> has joined #yocto03:43
*** klinger_ <klinger_!> has quit IRC03:46
*** doerrpau <doerrpau!> has quit IRC03:57
*** davest <davest!~Adium@> has quit IRC03:58
*** davest <davest!Adium@nat/intel/x-zrzhzumfiqebnfqv> has joined #yocto03:58
-YoctoAutoBuilder- build #207 of nightly-world is complete: Failure [failed Building Images] Build details are at
*** andyross <andyross!> has quit IRC04:32
*** andyross <andyross!> has joined #yocto04:33
*** crazy_imp <crazy_imp!> has quit IRC04:38
*** Jefro <Jefro!> has joined #yocto04:40
*** Jefro <Jefro!> has quit IRC04:41
*** crazy_imp <crazy_imp!> has joined #yocto04:43
*** agust <agust!> has quit IRC04:49
-YoctoAutoBuilder- build #209 of nightly-ppc is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #212 of nightly-arm-lsb is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #212 of nightly-x86 is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #212 of nightly-x86-lsb is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #180 of nightly-fsl-ppc is complete: Exception [exception Building Images interrupted] Build details are at
-YoctoAutoBuilder- build #180 of nightly-fsl-arm-lsb is complete: Exception [exception interrupted] Build details are at
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC04:54
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto04:55
*** Umeaboy <Umeaboy!> has joined #yocto04:55
*** mihai <mihai!~mihai@> has joined #yocto04:57
*** seebs <seebs!> has quit IRC05:03
*** agust <agust!> has joined #yocto05:03
*** seebs <seebs!> has joined #yocto05:04
*** zecke <zecke!> has joined #yocto05:08
*** fce84x0dev <fce84x0dev!~fce84x0de@> has quit IRC05:10
*** andyross <andyross!> has quit IRC05:13
*** Jefro <Jefro!> has joined #yocto05:24
*** khem <khem!> has quit IRC05:31
*** plfiorini <plfiorini!~plfiorini@> has quit IRC05:43
*** mihai <mihai!~mihai@> has quit IRC05:45
*** tor <tor!> has joined #yocto05:56
*** zeddii_home_ <zeddii_home_!> has joined #yocto06:03
*** behanw <behanw!> has quit IRC06:04
*** zeddii <zeddii!~ddez@> has quit IRC06:04
*** zeddii_home <zeddii_home!> has quit IRC06:05
*** zeddii_home_ is now known as zeddii_home06:05
*** zeddii <zeddii!~ddez@> has joined #yocto06:05
*** yzhao2 <yzhao2!~yzhao2@> has quit IRC06:05
*** Jefro <Jefro!> has quit IRC06:05
*** lpapp_ <lpapp_!~lpapp@> has left #yocto06:06
*** yzhao2 <yzhao2!~yzhao2@> has joined #yocto06:06
*** Jefro <Jefro!> has joined #yocto06:11
*** khem <khem!> has joined #yocto06:12
*** panda84kde <panda84kde!> has joined #yocto06:22
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:34
*** diego_ <diego_!~diego@> has joined #yocto06:38
*** panda84kde <panda84kde!> has quit IRC06:39
*** jukkar <jukkar!~jukka@> has joined #yocto06:41
*** mihai <mihai!~mihai@> has joined #yocto06:42
*** zeeblex <zeeblex!apalalax@nat/intel/x-hcsdqkzwmyzoswiq> has joined #yocto06:44
*** e8johan <e8johan!> has joined #yocto06:47
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto06:51
*** diego_ is now known as panda84kde06:57
*** smartin_ is now known as smartin06:57
*** eballetbo <eballetbo!> has joined #yocto06:58
*** ftonello_ <ftonello_!> has joined #yocto07:07
*** runexe_ <runexe_!> has joined #yocto07:09
*** ftonello <ftonello!> has quit IRC07:14
*** runexe <runexe!> has quit IRC07:14
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:23
*** W1N9Zr1418 is now known as W1N9Zr007:26
*** karfield <karfield!~karfield@> has joined #yocto07:27
karfieldHi, One question: does oe limit a package size?07:28
*** ant_work <ant_work!> has joined #yocto07:29
karfieldhere's my situation: after do_compile(), I got a bin file larger than 120M(the oe turn on -g in CFLAGS by default), and then do_package() produce some errors, like:07:32
karfieldNOTE: Executing RunQueue Tasks07:32
karfieldERROR: debugedit failed with exit code 256 (cmd was '/home/karfield/poky/beaglebone/product/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit' -b '/home/karfield/poky/beaglebone/product/work/armv7a-vfp-neon-poky-linux-gnueabi' -d '/usr/src/debug' -i -l '/home/karfield/poky/beaglebone/product/work/armv7a-vfp-neon-poky-linux-gnueabi/webrtc/0.0+depot0-r0/debugsources.list' '/home/karfield/poky/beaglebone/product/work/armv7a-vfp-neon-poky-linux-gnueabi/webrtc07:32
karfield/home/karfield/poky/beaglebone/product/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit: canonicalization unexpectedly shrank by one character07:32
karfieldERROR: Function failed: split_and_strip_files07:32
karfieldERROR: Logfile of failure stored in: /home/karfield/poky/beaglebone/product/work/armv7a-vfp-neon-poky-linux-gnueabi/webrtc/0.0+depot0-r0/temp/log.do_package.1081807:32
karfieldERROR: Task 10 (/home/karfield/poky/meta-karlab/recipes-rtc/webrtc/, do_package) failed with exit code '1'07:32
karfieldNOTE: Tasks Summary: Attempted 9 tasks of which 4 didn't need to be rerun and 1 failed.07:32
karfieldany one could help this, Thx!07:32
*** Crofton <Crofton!> has quit IRC07:41
*** Jefro <Jefro!> has quit IRC07:47
*** sameo <sameo!~samuel@> has joined #yocto07:49
*** zeddii_home <zeddii_home!> has quit IRC07:50
*** francois99 <francois99!> has joined #yocto07:57
*** jbaxter <jbaxter!> has joined #yocto07:59
*** karfield <karfield!~karfield@> has quit IRC08:05
*** bluelightning <bluelightning!~paul@> has joined #yocto08:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:07
bluelightningmorning all08:21
*** zerus <zerus!> has quit IRC08:25
*** honschu_ <honschu_!> has joined #yocto08:26
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has joined #yocto08:26
*** zerus <zerus!> has joined #yocto08:27
*** Stygia <Stygia!> has joined #yocto08:27
*** honschu <honschu!~honschu@shackspace/j4fun> has quit IRC08:29
StygiaHey, I am trying to build a package, and I receive this error during do_package (Which I do not manually set) that I will admit I don't quite understand: (Recipe included). Any pointers on how to start debugging this issue?08:32
JaMaStygia: run the shown command manually to see what the error was08:35
StygiaJaMa, Will do, hang on.08:36
zibristygia: i got that working yesterday with the cpan bbclass08:36
bluelightningI did send a patch to print the output from commands such as objcopy during do_package08:37
zibristygia: never got that issue, but i recommend you move to using the cpan bbclass... everything becomes much more simple :)08:37
Stygiazibri, perl-module-dbd-sqlite?08:38
*** zecke <zecke!> has quit IRC08:38
Stygiazibri, I tried it with the CPAN metaclass but I couldn't get it to work. Do you have a recipe that builds?08:38
StygiaJaMa, Also, turns out I probably don't have the program in my path, I'll look into it.08:38
Stygiazibri, Alright, I will try. Remind/teach me... what is a "native" deb again?08:43
Stygiazibri, Why would I depend on cpan-dbi-native instead of just cpan-dbi?08:44
bluelightningStygia: if it's something that is to be run on the build host, it would be -native08:45
Stygiabluelightning, Ah, makes sense.08:46
Stygiazibri, And of course it just worked... I swear I already tried this.08:48
Stygiazibri, Well. Thanks dude. :) You saved me quite a bit of wasted time there, then.08:48
Stygiazibri, I wonder what I did wrong, though. I've done so many CPAN recipes, I checked it for typo's so many times...08:49
Stygiazibri, Ah, well. On to the next thing. :P08:49
zibristygia: heh, no problem :).08:49
zibrigood luck!08:49
Stygiazibri, Hmm, just formally, do you release this code for me to use under a BSD or MIT license?08:49
zibriwhatever you want, based on your recipe you pastebinned yesterday :)08:49
*** Noor <Noor!~noor@> has joined #yocto08:49
Stygiazibri, Heh sure. :P I plan to put it under BSD 3-clause. Not very fond of GPL.08:50
Stygiazibri, I think your adding DEPENDS = "cpan-dbi-native" did the trick08:51
Stygiazibri, I already had cpan-dbi in my DEPENDS when I tried CPAN for this one, I believe, but it didn't work, presumably because it wants to build some stuff locally or something.08:52
*** smartin_ <smartin_!> has joined #yocto08:52
zibriyeah, that's because it's required within the Makefile.PL (i.e. run on the build host)08:52
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.> has joined #yocto08:52
*** slaine <slaine!~slaine@> has joined #yocto08:52
Stygiazibri, Hmm yes, which is why I ended up doing a lot of sed's on that Makefile to ensure that local-sounding paths got redirected to the working/destination directories.08:53
fenrigHi I'm looking for someone with a bit of SDK and Qt knowledge, as I'm trying to produce an SDK with Qt4 support (qmake) with my own custom image08:53
*** ynezz_ is now known as ynezz08:53
*** smartin_ <smartin_!> has quit IRC08:53
bluelightningStygia: of course it's up to you, but the norm is to use MIT license for metadata08:56
Stygiabluelightning, Hmm MIT is fine, but I do like the third clause of BSD, not to advertise with my name. But I think it's hardly realistic in this case.08:58
*** addu <addu!> has left #yocto08:59
bluelightningI don't recall that it's ever happened in our community :)08:59
bluelightningthe most likely thing that could happen would be the name of the project being used for promotion; even that's not been much of an issue (and the Yocto Project has a means for enabling that in any case)09:00
zibristygia: btw, the cpan-test-* rdepends can probably be discarded unless you plan to run unittests on target09:02
Stygiazibri, Presumably. But meta-cpan did list it as dependencies for this package.09:03
zibriand they are all coremodules distributed with perl anyway :)09:03
Stygiazibri, Maybe I could just set them as depends though.09:03
Stygiazibri, Well... the OE perl is pretty messed up. And they are?09:03
zibrithey are in installed in my sysroot at least09:04
*** belen <belen!~Adium@> has joined #yocto09:04
*** diego <diego!> has joined #yocto09:05
zibriactually all the rdepends except DBI is core modules09:05
*** diego is now known as Guest3733209:05
*** zecke <zecke!> has joined #yocto09:05
Stygiazibri, the OE perl is pretty messed up, it lacks several core modules. But this is listed as a module:
Stygiazibri, And not as part of perl 5.14.3, _possibly_ 5.18 though.09:06
*** panda84kde <panda84kde!~diego@> has quit IRC09:06
zibristygia: nope, File::Spec was introduced in 5.4.509:07
zibristygia: try `corelist File::Spec` :)09:07
Stygiazibri, Then why is it shown as a separate module on metacpan?09:09
zibria lot of modules live dual lives, e.g. for backporting fixes. active development is usually made outside of perl, but merged to perl on release etc09:09
Stygiazibri, Weird.09:20
Stygiazibri, Well, I will look into it. Once we have everything building here, you and me can perhaps try and fix the OE perl recipe, as that recipe only includes the bare minimum.09:20
Stygiazibri, Would you believe that,, and similar things aren't even installed by default?09:21
Stygiazibri,  I had to make this bbappend to even make simple perl things work:
zibristygia: hum, i have those in my sysroot09:22
Stygiazibri, Hmm, your BB sysroot? They may _be_ there, but unless they go in FILES they aren't actually deployed.09:23
zibrialthough, some of the modules in your list aren't core modules (e.g. URI and URI::Escape)09:23
Stygiazibri, OH wait, nice spotted, I have those as modules, fixed it. :)09:23
zibristygia: the FILES variable only affects stuff being picked up for packaging from the per recipe destination dir (e.g. ${WORKDIR}/image) if i understand correctly.09:25
zibriif things wasn't included in FILES, but installed, we would get qa warnings when running bitbake09:26
Stygiazibri, Yea... you would think so. And yet, when I used the standard perl recipe and deployed, crucial modules like were missing.09:27
Stygiazibri, It took quite a while to allow even simple modules and my script to work.09:27
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto09:29
zibristygia: i think you have to rdepend on perl-lib09:29
zibriFILES_${PN}-lib = "... ${libdir}/perl5 ..."09:29
*** Guest37332 is now known as panda84kde09:29
zibri(from the perl recipe)09:29
fenrigIs there someone who can nudge me in the right direction for generating a Qt SDK?09:30
Stygiazibri, That's... possible, I guess? But ${libdir}/perl5 cgertainly doesn't contain _all_ the files, they are pretty scattered.09:32
Stygiazibri, Actually they were almost all in ${libdir}/perl/5.14.3/09:32
zibri/usr/lib/perl5 is a symlink to /usr/lib/perl :)09:34
Stygiazibri, Ah well... fair enough then. :P09:35
Stygiazibri, And dear fuck... if you're right I've wasted so much time.09:35
Stygiazibri, Someone really needs to mind the OE documentation more. I'm probably gonna write a OE crash-course tutorial thing once I'm done here.09:35
rburtonStygia: we've a documentation writer, so if there's any problems/missing sections then feel free to file bugs09:38
Stygiarburton, I may take you up on that. Just to verify, I should file the bug with the yocto project, yes?09:40
Stygiarburton, I never got the whole oe/bitbake/poky/yocto thing straight honestly.09:42
*** chitz <chitz!~chitz@> has joined #yocto09:42
rburtonStygia: yes09:47
rburtonthe short version is that Yocto is an umbrella project, containing bitbake (the build tool) and oe-core (the core metadata).  poky is a reference distro build using bitbake+oe-core.  the rest of "oe", such as meta-oe, isn't actually part of the Yocto Project, although its simple for any layer to be Yocto Compatible and so on.09:48
Stygiarburton, Ah right, makes sense. Thanks dude. :)09:50
rburtonthe confusing this is the layers that make up poky are called meta-yocto. that's stupid.09:50
fenrigrburton: just report documentation bugs to filezilla?09:51
fenrigrburton: eerrrr bugzilla -.-09:51
rburtonfenrig: yeah09:51
fenrigrburton: okay will do :d09:51
zeckebluelightning: hi, are you awake yet?09:52
bluelightningzecke: yep09:52
zeckebluelightning: hehe, is there a command to 'prune' the sstate cache?09:53
bluelightningzecke: there is, one sec09:53
zeckebluelightning: my laptop is running low on disk space.09:54
bluelightningzecke: (under scripts/)09:54
zeckeah thanks. let me see if that works for edison too. :)09:56
zeckeit does :)09:58
*** smartin <smartin!> has quit IRC10:06
*** smartin <smartin!> has joined #yocto10:10
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:52
*** swex_ <swex_!~swex@> has joined #yocto11:00
*** swex <swex!~swex@> has quit IRC11:04
*** pev <pev!~pev@> has joined #yocto11:04
*** chitz <chitz!~chitz@> has left #yocto11:06
*** exosyst <exosyst!~nick@> has joined #yocto11:29
*** tjsieb_away is now known as tsjsieb11:34
*** zerus <zerus!> has quit IRC11:40
*** tbn <tbn!> has joined #yocto11:41
*** tbn is now known as Guest3507111:42
*** behanw <behanw!> has joined #yocto11:46
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto11:51
*** joeythesaint <joeythesaint!~jjm@> has joined #yocto11:57
*** zerus <zerus!> has joined #yocto12:01
*** sameo <sameo!~samuel@> has quit IRC12:02
*** mulhern <mulhern!> has joined #yocto12:13
mshakeelrburton: If you have time please comment here:
mshakeelI want to finish it before getting into something else12:14
*** sameo <sameo!~samuel@> has joined #yocto12:18
*** panda84kde <panda84kde!> has quit IRC12:22
*** diego <diego!> has joined #yocto12:22
*** diego is now known as Guest9402612:23
*** panda84kde <panda84kde!> has joined #yocto12:24
*** diego_ <diego_!> has joined #yocto12:24
*** scot__ <scot__!> has joined #yocto12:27
rburtonmshakeel: sorry for not doing so before, done12:27
*** Guest94026 <Guest94026!> has quit IRC12:28
*** panda84kde <panda84kde!> has quit IRC12:28
mshakeelrburton: thanks, then I just need to make sure that do_install_append() in systemd.bbclass is appended after any package recipe do_install_append()12:45
rburtongood point.12:45
rburtonmust be a way to ensure that12:45
rburtondo it as a package postprocess func?12:45
rburtonthat's hopefully not too *late*12:46
mshakeelyes, seems like either we need a post func of do_install or we can prepend do_package12:47
rburtoncould add a new task in the class, that would work.12:48
mshakeelI was thinking something similar to: do_install[postfuncs] += "func_for_systemd"12:48
mshakeelyes, a new task will make things simpler12:49
rburtonbluelightning: any opinion on the best place for a class to go in and delete files after do_install?12:49
rburtonoptions appear to be a new task added by the class / do_install[postfunc] / PACKAGE_PREPROCESS_FUNCS12:50
mshakeelI just gave it a run and do_install_append() from systemd.bbclass is the first thing appended in do_install12:51
rburtonassuming the inherit happens first, that would make sense12:52
*** Stygia <Stygia!> has quit IRC13:00
*** madman-alex <madman-alex!~luccisa@nat/cisco/x-rzgrlooicakaviok> has joined #yocto13:03
*** swex_ <swex_!~swex@> has quit IRC13:06
*** swex <swex!~swex@> has joined #yocto13:07
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC13:10
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto13:12
*** ant_work <ant_work!> has quit IRC13:17
*** sameo <sameo!~samuel@> has quit IRC13:18
*** darknighte is now known as darknighte_znc13:19
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ouftiolwzclyivbi> has joined #yocto13:21
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ouftiolwzclyivbi> has quit IRC13:26
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zpazijkwosudsxne> has joined #yocto13:29
*** davest <davest!Adium@nat/intel/x-zrzhzumfiqebnfqv> has left #yocto13:33
*** sameo <sameo!samuel@nat/intel/x-phmgydpnyqngaidr> has joined #yocto13:35
*** joeythesaint <joeythesaint!~jjm@> has quit IRC13:39
*** walters <walters!> has joined #yocto13:40
waltersi'm trying to rebase a very custom system from danny -> dylan, and mostly was easy except the kernel install is looping infinitely doing "depmod"; sound like a familiar symptom to anyone?13:41
waltersit's quite painful to read all the generated shell script and try to debug that way13:41
bluelightningzeddii: ^ any ideas?13:45
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC13:45
waltersohh...maybe it's not an infloop, it's just running depmod after each individual kernel module rpm install13:46
*** joeythesaint <joeythesaint!~jjm@> has joined #yocto13:47
* zeddii reads13:49
zeddiidepmod would be running as part of the kernel.bbclass, so no need to look at any generated shell code, and yes, there's nothing terribly efficient about the kernel packaging and install at the moment .. but it is better than it used to be.13:50
waltersdo you guys make use of rpm %posttrans anywhere?  git grep says no but13:52
waltersit's significantly more efficient13:53
bluelightningwalters: that sounds like a useful thing, I guess nobody ever got around to doing something like that13:54
bluelightningwalters: I guess the difficulty would be it would need some kind of generic hint of which postinstalls (or which parts of a postinstall) could be deferred *if* the package backend supports it13:55
rburtonyeah, dpkg's approach is different, and opkg... well, is opkg.13:55
* rburton curses gtk and goes to walk the dog instead13:55
*** belen <belen!~Adium@> has quit IRC13:56
waltersrburton, what'd gtk do?13:58
*** belen <belen!Adium@nat/intel/x-ehtxdlcwsajorhyn> has joined #yocto13:58
*** darknighte_znc is now known as darknighte13:59
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto13:59
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:59
*** sameo <sameo!samuel@nat/intel/x-phmgydpnyqngaidr> has quit IRC14:02
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC14:02
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.> has quit IRC14:02
zeckebluelightning_: I have a theory and maybe you find a flaw. kernel.bbclass does not appear to pass TUNE_CC (e.g. no -march=arm..) to the kernel compilation.. my kernel appears to die in unaligned memory access.. cat /proc/cpu/alignment shows system issues14:04
zeckebluelightning_: now I wonder what gcc 4.8.1 optimizes for by default (I am on arm9/armv5t) system.. so somehow I think gcc will generate unaligned memory access by default now? Is that plausible?14:04
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.> has joined #yocto14:05
fenrighow do I enable sftp support in my image?14:05
bluelightning_zecke: I don't know I'm afraid, not my area of expertise... zeddii or khem would be the best people to speak to about that I would think14:05
*** panda84kde <panda84kde!> has joined #yocto14:06
zeckekhem: ping?14:06
bluelightning_fenrig: server or client?14:06
*** diego_ <diego_!> has quit IRC14:06
fenrigbluelightning_: server ;)14:06
bluelightning_fenrig: add "openssh-sftp-server" to IMAGE_INSTALL14:07
fenrigbluelightning_: cool, how do I find this information?14:07
zeddiizecke, the kernel shouldn't be taking tune arguments from a build system, it knows best for any given arch.14:08
zeddiiif there's a bad tuning, we need to look into kernel patches, not passing build system arguments in, that would potentially be toolchain specific.14:08
bluelightning_fenrig: I just did "git grep sftp" to find that...14:09
fenrigbluelightning_: ah okay sorry :/14:09
fenrigbluelightning_: could have found that myself then :/14:09
bluelightning_fenrig: well sometimes it's not that easy14:09
zeckezeddii: is the first two oopses I get14:10
zeckezeddii: that is 3.2.48 + two memset fixes from newer kernel releases14:10
zeckezeddii: so I wonder if the data abort is a red herring or not. :}14:13
zeckezeddii: same kernel compile with GCC 4.6 (minus the two memset patches is okay). I will now build with gcc 4.6 and the two new patches. :}14:14
* zeddii looks14:16
zeddiizecke, I don't have all the background. you are seeing the traps with what ? gcc 4.8 ?14:17
zeckezeddii: gcc 4.8.1 from oe-core as of today14:18
zeddiiok. so perhaps not surprising. We've been through lots of issues with gcc 4.8 and the kernel. What arch was this again ?14:18
zeckezeddii: ARM, armv5t14:18
* zeddii nods. 14:19
zeddiiif you are using the same two memset fixes that we've been discussing on the mailing lists, you are most of the way there, but 3.2 may be missing more.14:19
*** sameo <sameo!~samuel@> has joined #yocto14:20
rburtonwalters: change "something" between 2 and 3, so now my widget grows in a size-allocate loop forever14:20
waltersyeah the sizing stuff is...messy14:22
fenrigcool, finally got a basic Cross development enviroment working14:25
fenrigwith Qt Creator ;)14:27
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has quit IRC14:34
erencongrats fenrig :)14:34
waltersok, i replaced the pkg_postinst_modules() in kernel-module-split.bbclass with /bin/true for now...this build system ends up running depmod in a different layer anyways, and that got me going14:36
*** hollisb <hollisb!> has joined #yocto14:37
*** diego_ <diego_!> has joined #yocto14:37
*** belen <belen!Adium@nat/intel/x-ehtxdlcwsajorhyn> has quit IRC14:38
*** panda84kde <panda84kde!> has quit IRC14:40
pevRandom question ; some recipes seem to have a "files" directory in the same dir as the .bb, others have a dir the same name as the recipe name - is there any particular convention?14:40
*** bluelightning1 <bluelightning1!~paul@> has joined #yocto14:40
*** bluelightning1 is now known as bluelightning14:41
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto14:41
*** belen <belen!~Adium@> has joined #yocto14:41
mario-goulartpev: I guess "files" is common to all recipes in that directory. A directory named after the recipe is only for that particular recipe.14:42
rburtonyou'll also see foo-1.0 where patches are specific to a single version14:42
mario-goulartI think you can also use <recipe>-<version> to apply restrictions per version.14:42
*** munch <munch!> has joined #yocto14:44
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC14:45
pevThanks :-)14:45
*** davest <davest!Adium@nat/intel/x-egzvjkvmqynospvo> has joined #yocto14:45
mario-goulartYou're welcome. :-)14:46
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zpazijkwosudsxne> has quit IRC14:48
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.> has quit IRC14:49
*** sameo <sameo!~samuel@> has quit IRC14:50
pevOk, so another fun question - I'm looking at how to put together a shared library recipe under yocto. I'm trying to use a simplish example to break down so im looking at ./meta/recipes-multimedia/libomxil/ to start with. I can see how "FILES_${PN}-dev" handles the libs, but I'm not sure what happens to the header files? Do they not need to be exported somehow so other apps building can find them or is that down to the Makefile of the package itself?14:58
*** crazy_imp <crazy_imp!> has left #yocto14:58
rburtonthe makefile is expected to install them to (usually) /usr/include14:59
rburtonand then they go into PN-dev15:00
*** Jefro <Jefro!> has joined #yocto15:00
peveven though /usr/include isnt in -dev's FILES?15:01
rburtonit is by default15:02
rburtonsee bitbake.conf15:02
pevCool. Also, what part of the Makefile should do the install? If it's under a "install:" rule, does the build system make that by default?15:03
pevor do I need to put the install under my "all:" rule?15:03
rburtonnow you're entering style choices15:03
rburtonautotools-style is "all" is build, and "install" is install15:03
*** eren <eren!~eren@unaffiliated/eren> has quit IRC15:04
rburtonand they'll get ran by default15:04
rburtonno, i'm wrong15:04
pevI'm trying to keep simple and just have raw source and a Makefile avoiding autotools :-D15:04
rburtonwriting a raw makefile *and* supporting cross compilation isn't always easy15:05
rburtonbut if you insist, have an install rule that installs the files15:05
pevI have no doubt of that :-P15:05
rburtonand call that in your do_install()15:05
pevGreat, I'll give that a shot!15:05
rburtonby *default*, we run make in the compile phase, and hope the recipe knows what its doing to install15:05
rburtonie autotools.bbclass knows it can run make install15:05
*** sameo <sameo!samuel@nat/intel/x-tqpwjhhciwjvdmhh> has joined #yocto15:07
ndecanybody knows what can be the root cause of that error: ERROR: object '' from LD_PRELOAD cannot be preloaded: ignored. it was found on an ubuntu 12.04 64-bit machine.15:12
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-sdspcycdvhhowseg> has joined #yocto15:13
*** andyross <andyross!> has joined #yocto15:13
rburtonthere's a patch for that15:15
rburtoni thought it was merged already15:15
rburtonFAKEROOTBASEENV in bitbake.conf15:16
rburtonshould end in lib64 not lib15:16
rburton"Issue with pseudo on 64-bit build host" on oe-core15:16
rburtonseebs: was that resolved or still pending a fix from someone?15:16
ndeci have seen that on dylan.15:17
*** diego_ <diego_!> has quit IRC15:17
pevAnother (possibly) silly question I'm afraid...! In the simple Makefile I do a "CFLAGS -I. -fPIC" which works correctly. However when bitbake calls it, if I look at the output it seems that CFLAGS appears to have been overwritten!15:21
khemzecke: yes15:21
rburtonpev: yes, that's how make behaves15:22
rburtonthe environment definition overrides the makefile15:22
pevSo if I need to add to what yocto uses to override? Or just use a different env name in the makefile for the flags I dont want overriden?15:23
rburtonup to you. last time I wrote a makefile from scratch i think i used my own varname inside .15:23
pevthanks! Talk about learning curve :-)15:24
ndecrburton: about the pseudo issue, not all hosts seem to be impacted. is that expected? also we use dylan, not master, and FAKEROOTBASEENV has been added after dylan.15:26
pevOK, back to the doing an install... in my install rule I need to pass the location where to install to. Is that what in autotools land would have been dealt with by PREFIX?15:27
rburtonndec: i made the problem go away by switching from rpm to ipk, so i'm not sure it's entirely understood15:27
ndecwell, we use ipk.15:27
rburtonpev: no, prefix is the real location ("/usr") and DESTDIR is used to re-parent it temporarily for packaging15:28
rburtonso use $DESTDIR in all of your install commands15:28
rburtonthis is about the point when people realise that modern autotools isn't all that bad15:29
pevYep! Looks like $DESTDIR doesnt get set for some reason though...15:29
pevI've just been putting off learning how to use autotools for years... I'm told it shouldnt take long to figure out for something simple like this though...!15:30
rburtonpev: sure, you'll have to set something like DESTDIR yourself15:31
rburtonas i said, that's what autotools does15:31
rburtonif you're writing it yourself you get to define it yourself15:31
rburtoncall it I_HATE_MAKEFILES if you want :)15:31
pevSorry, I thought you meant it was automagically set by bitbake... Ack that!15:31
rburtonautotools_do_install is basically this: oe_runmake 'DESTDIR=${D}' install15:31
*** sameo <sameo!samuel@nat/intel/x-tqpwjhhciwjvdmhh> has quit IRC15:32
pevBollocks to it, I'll read the autotools chapter of 21st C C tonight....! :-D15:36
rburtonautotooling a small library is entirely trivial15:39
pevrburton: Hopefully it will be after I've read up on it :-)15:41
*** darknighte is now known as darknighte_znc15:46
*** cetola <cetola!> has joined #yocto15:46
*** zeeblex <zeeblex!apalalax@nat/intel/x-hcsdqkzwmyzoswiq> has left #yocto15:48
*** davest <davest!Adium@nat/intel/x-egzvjkvmqynospvo> has quit IRC15:54
*** davest <davest!~Adium@> has joined #yocto15:59
*** davest <davest!~Adium@> has quit IRC16:01
kergoth`my thoughts on autotools always come down to: they suck, but they suck in known, predictable ways we can workaround, which is more than we can say for some other homerolled systems :)16:03
*** kergoth` is now known as kergoth16:03
*** eballetbo <eballetbo!> has quit IRC16:04
*** zenlinux_ <zenlinux_!> has joined #yocto16:04
bluelightningndec: I'm not sure but I can see the same issue could happen with previous versions because we set PSEUDOLIBDIR to point to ..../lib rather than ..../lib64 in scripts/bitbake16:05
*** mihai <mihai!~mihai@> has quit IRC16:05
ndecbluelightning: my initial guess was that it relates to 32-bit vs 64-bit too, even before this discussion.16:06
zeckekhem: hi! i am rebuilding.. and rebuilding again (I added -mno-unalign... to the conf/machine/include for armv5 but removed it again).  Once my laptop reaches kernel compilation again I will check if my kernel compilation passes -march=armv5... properly16:06
ndecbluelightning: the problem is that it happens on someone's PC which i don't have access to.16:07
bluelightningndec: sure... as a workaround you could get them to try editing scripts/bitbake to use lib64 and see what happens16:08
bluelightningseebs: this is a bit puzzling... you said in the thread it should install to a lib64 subdirectory, so if that's the case how can we ensure PSEUDO_LIBDIR gets set correctly?16:08
ndecalso, is that clear why it doesn't happen to everyone? that guy isn't using a fancy distro... but ubuntu 12.04..16:09
ndecis there any 'host contamination' somehow?16:10
bluelightningndec: I'm not yet clear on that either16:10
* ndec never opened script/bitbake so far ... ouch...16:11
* kergoth chuckles16:11
bluelightningndec: yeah, it's gone in master :)16:11
ndecreally, that looks like one incentive to move ;-)16:11
bluelightningit existed to work around the issue that bitbake needed to be re-run under pseudo but pseudo wasn't initially built16:12
*** Jefro <Jefro!> has quit IRC16:12
bluelightningthen a few other things got thrown in there (e.g. fixes for broken host tar/git)16:12
bluelightningre master, I wouldn't switch to it for production16:13
ndecwell, 'few other things', that's a neat way to say it!16:13
ndecno, we can't use master for now.16:13
ndecfor sure.16:13
ndecok, so what you want me to try is to modify almost the very last line in script/bitbake. e.g.     PSEUDO_BINDIR=$PSEUDOBINDIR PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@16:14
bluelightningndec: right16:16
ndecinterestingly, on my machine where i don't get any issue (and running 13.04/64-bit), libpseudo is here tmp/sysroots/x86_64-linux/usr/lib/pseudo/lib64/libpseudo.so16:16
bluelightningndec: indeed, same here on my CentOS 6.4 build machine16:16
bluelightning(also 64-bit of course)16:16
bluelightningit might be some subtlety about LD_LIBRARY_PATH already pointing to the right location, except for on the affected systems16:17
ndecis pseudo bin supposed to 'link' against libpseudo?16:19
ndecmine doesn't.16:19
ndecat least not explicitely (objump -p)16:19
* kergoth mulls over altering binreloc to support macs16:20
*** doerrpau <doerrpau!> has joined #yocto16:20
bluelightningndec: no, I think that's expected16:21
ndecbluelightning: running from devshell, i get this:16:22
ndec# echo $LD_LIBRARY_PATH16:22
ndecso, something is indeed appending the right folder here16:23
bluelightningndec: hmm, interesting16:23
ndececho $PSEUDO_LIBDIR16:23
*** e8johan <e8johan!> has quit IRC16:27
*** Guest35071 <Guest35071!> has quit IRC16:28
*** mr_science <mr_science!> has joined #yocto16:37
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:37
*** plfiorini <plfiorini!> has joined #yocto16:43
*** Crofton <Crofton!> has joined #yocto16:44
*** seebs <seebs!> has quit IRC16:49
ndecbluelightning: ok, i have asked our dev to send me a lot of information (variable dumps, tarball of pseudo, ...). he is probably sleeping by now, but i should be able to study the logs tomorrow morning.16:50
*** seebs <seebs!> has joined #yocto16:50
ndeci really don't see where LD_LIBRARY_PATH is being modified... i suspect this can be related to the presence of 32-bit header files (stubs-32.h)...16:52
ndece.g. libc6-dev-i386 on ubuntu.16:53
bluelightningndec: hmm, that might possibly have something to do with it16:54
ndecpseudo build itself seems to be impacted by that, at least.16:54
bluelightningndec: FWIW I am setting up an Ubuntu 12.04 64-bit machine here to run some tests (and incidentally because we need another build machine)16:54
* ndec is doing that too locally ;-)16:55
ndecwell, a chroot, not a real machine.16:55
bluelightningI have a VM already but unfortunately I'm too short of space on my laptop to use it for a full build16:55
*** belen <belen!~Adium@> has quit IRC16:57
ndecbluelightning: i am going away now. i hope to get more data tomorrow. thanks a lot for your help.17:00
*** belen <belen!Adium@nat/intel/x-njueforoezzlyxkr> has joined #yocto17:02
bluelightningndec: no problem17:07
bluelightningcu later17:07
seebsAs I recall, pseudo has some code to try to fix up the library directory. I think we do have a known issue in some cases, but I haven't yet had a chance to go stare at it and try to figure out what's up.17:07
*** davest <davest!Adium@nat/intel/x-uwhnzejsnkshiayq> has joined #yocto17:10
*** mulhern <mulhern!> has quit IRC17:17
*** belen <belen!Adium@nat/intel/x-njueforoezzlyxkr> has quit IRC17:21
*** belen <belen!~Adium@> has joined #yocto17:23
*** mulhern <mulhern!> has joined #yocto17:25
*** belen <belen!~Adium@> has quit IRC17:27
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:30
*** agust <agust!> has quit IRC17:38
*** agust <agust!> has joined #yocto17:38
*** mulhern <mulhern!> has quit IRC17:42
*** mulhern <mulhern!> has joined #yocto17:44
*** roric <roric!~roric@> has quit IRC17:54
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has joined #yocto17:54
*** Jefro <Jefro!> has joined #yocto17:54
*** zenlinux_ <zenlinux_!> has quit IRC18:05
*** Jefro <Jefro!> has quit IRC18:07
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has quit IRC18:09
*** zecke <zecke!> has quit IRC18:21
-YoctoAutoBuilder- build #214 of nightly-arm-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #214 of poky-tiny is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #224 of nightly-intel-gpl is complete: Failure [failed Building Images Building Images_1] Build details are at
-YoctoAutoBuilder- build #211 of nightly-non-gpl3 is complete: Failure [failed Building Images] Build details are at
-YoctoAutoBuilder- build #212 of build-appliance is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #223 of nightly-mips-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
*** doerrpau <doerrpau!> has left #yocto18:45
*** tomz2 <tomz2!> has left #yocto18:50
*** mulhern <mulhern!> has quit IRC18:51
-YoctoAutoBuilder- build #64 of minnow is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
*** mulhern <mulhern!> has joined #yocto18:52
-YoctoAutoBuilder- build #205 of nightly-x86-64-lsb is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #24 of buildtools is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #210 of nightly-arm is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Building Images_3 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #214 of nightly-x86 is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Building Images_3 Publishing Artifacts] Build details are at
*** cetola <cetola!> has left #yocto18:56
-YoctoAutoBuilder- build #221 of nightly-x32 is complete: Failure [failed Building Images Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #211 of nightly-mips is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Building Images_3 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #208 of nightly-x86-64 is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #211 of nightly-ppc-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
*** merlin262 <merlin262!~workerbee@> has joined #yocto19:03
-YoctoAutoBuilder- build #50 of minnow-lsb is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
*** RichBayliss_ <RichBayliss_!524466ee@gateway/web/freenode/ip.> has joined #yocto19:06
*** mulhern <mulhern!> has quit IRC19:06
RichBayliss_hi guys19:06
RichBayliss_I have an issue with my Yocto build for RaspberryPi19:06
RichBayliss_basically, on first boot everything works fine, but any subsequent boots then networking stays down19:06
*** sameo <sameo!~samuel@> has joined #yocto19:06
kergothplease don't spam to multiple channels :)19:07
RichBayliss_I can manually bring it up, by logging in locally, then issuing "ifdown eth0" then "ifup eth0"19:07
merlin262hi kergoth, been a bit :)19:07
kergothhey, how goes it19:07
merlin262pretty good19:07
*** pidge <pidge!~pidge@> has joined #yocto19:08
merlin262you interested in doing some consulting work?19:08
RichBayliss_sorry - I tried in #poky but there wasnt many people in there19:08
kergothhere is best, indeed19:09
-YoctoAutoBuilder- build #182 of nightly-fsl-arm-lsb is complete: Failure [failed Building Images Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
kergothor contact the folks that maintain the raspberry pi layer, they might have hit it before19:09
RichBayliss_ok thanks19:10
kergothit sounds like your /etc/network/interface is misconfigured, unless you're using NetworkManager19:10
RichBayliss_google is giving me nothing - so I am just trying to rule out HW or something19:10
kergothits possible. try adding 'auto eth0' to /etc/ntework/interfaces and rebooting, as a starting point19:10
*** ftonello_ is now known as ftonello19:11
RichBayliss_does it get built/changed on first boot?19:11
*** plfiorini <plfiorini!> has quit IRC19:11
RichBayliss_I am based on minimal platform - so CLI only19:11
kergothfirst boot runs a ton of package postinst scripts which diodn't run at image creation time19:11
RichBayliss_ah ok19:11
kergothnot everything can be run at build time due to the cross-compilation19:11
RichBayliss_so maybe the initial interfaces file is good - but the post-inst one is bad (but looks fine)19:11
RichBayliss_of course19:12
kergothit sounds like the other way around. you said first boot worked, so it sounds like the postinst brought up the interface19:12
RichBayliss_yeah - so I wonder if something altered the interfaces file, after the bring up19:14
kergothunlikely, more likely the interfaces file just doesn't have 'auto' in it, which is what makes it automatically bring up the interface on boot19:14
*** slaine <slaine!~slaine@> has quit IRC19:14
kergothwhich is why i suggested adding it about 5 minutes ago19:14
RichBayliss_it did have auto in it19:15
RichBayliss_I have completely wiped and rebuilt the file now19:15
RichBayliss_just testing19:15
kergothcheck syslog, see if there were any errors when it tried to bring up the interface on boot19:15
RichBayliss_it did have some extra interfaces which I wont be needing19:15
RichBayliss_eth1, wlan0 etc19:15
kergothcould be a timing issue, trying to bring it up before its ready? *shrug*19:15
kergothtough to say, many variables19:15
-YoctoAutoBuilder- build #209 of nightly-multilib is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Running Sanity Tests_1 Building Images_2 Running Sanity Tests_2 Building Images_3 Running Sanity Tests_3 Building Images_4] Build details are at
RichBayliss_indeed - appreciate your thoughts19:16
RichBayliss_sometime it takes someone to point out the obvious :D19:16
kergothnp, good luck with it19:16
RichBayliss_seems that a "clean" file is working after reboot and power cycle19:16
RichBayliss_might need to alter the base image files to just keep it simple :)19:17
kergothprobably best off creating a new empty layer and adding a bbappend to base-files to provide your own default interfaces file without modfiying the core19:18
RichBayliss_im very very new to this (started on Monday) so still learning19:18
* kergoth nods19:18
RichBayliss_I gathered I can override certain things that way19:18
RichBayliss_hmm ok - powercycle and its not coming back up again19:18
kergothdoes sound like timing could be a concern. maybe you can drop the 'auto' from interfaces and see if it gets brought up by udev when the device shows up (used to be called coldplug)?19:19
* kergoth shrugs19:19
*** plfiorini <plfiorini!> has joined #yocto19:19
-YoctoAutoBuilder- build #183 of nightly-fsl-arm is complete: Failure [failed Building Images Building Images_1 Building Images_2 Building Images_3 Building Images_4 Publishing Artifacts] Build details are at
*** Jefro <Jefro!~jefro@> has joined #yocto19:20
RichBayliss_hmm - removed auto from eth0 and after a boot only lo came up19:23
*** Jefro <Jefro!~jefro@> has quit IRC19:24
RichBayliss_I will look at the timing - but I would imaging the RPi guys would be on this if it was a generic issue19:24
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto19:24
-YoctoAutoBuilder- build #214 of nightly-x86-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
kergothcouldn't hurt to talk with them, see if anyone else has hit a similar issue19:25
RichBayliss_just gotta find a way to reach them19:26
RichBayliss_mailing lists arn't my thing :(19:26
-YoctoAutoBuilder- build #176 of nightly is complete: Failure [failed Building Images Building Images_1 Building Images_2 Building Images_3 Building Images_4 Building Images_5 Building Images_6 Building Images_7 Building Images_8 Building Images_9 Building Images_10 Building Images_11 Building Images_12 Building Images_13 Building Images_14 Publishing Artifacts Building Images_15] Build details are at
*** ericben <ericben!> has joined #yocto19:28
*** merlin262 <merlin262!~workerbee@> has quit IRC19:30
*** merlin262 <merlin262!~workerbee@> has joined #yocto19:31
kergothheh, you won't get much done without using mailing lists around here19:32
RichBayliss_I can tell :D found the OE RPi link - let's see if anyone bites19:34
RichBayliss_thanks for your pointers - glad to know Im not just being thick19:34
*** agherzan <agherzan!> has joined #yocto19:40
*** agherzan <agherzan!> has quit IRC19:40
*** agherzan <agherzan!> has joined #yocto19:41
*** mario-goulart <mario-goulart!> has quit IRC19:41
*** agherzan <agherzan!> has quit IRC19:41
*** smartin_ <smartin_!> has joined #yocto19:43
*** mario-goulart <mario-goulart!> has joined #yocto19:48
*** tor <tor!> has quit IRC19:57
*** Circuitsoft <Circuitsoft!ccb603ed@gateway/web/freenode/ip.> has joined #yocto20:06
CircuitsoftHow can I make my image bigger so I have room for logfiles on the target?20:07
CircuitsoftI tried adding IMAGE_ROOTFS_EXTRA_SPACE="1048576" to my to no effect.20:07
RichBayliss_Circuitsoft I was just looking at this, how random :)20:15
*** bluelightning <bluelightning!> has joined #yocto20:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:15
RichBayliss_I think I read that it can be awkward20:15
RichBayliss_but that it about it20:15
*** Jefro <Jefro!> has joined #yocto20:15
mr_scienceawkward is the guy sitting next to you ragging on open source developers for things they can't even control...20:19
mr_sciencei guess other than one of our subs, i'm the only "open source" guy here now.20:20
RichBayliss_hey mr_sceince - thanks for the pointers the other night20:24
RichBayliss_got me sorted20:24
*** W1N9Zr0 <W1N9Zr0!> has quit IRC20:24
*** W1N9Zr0 <W1N9Zr0!> has joined #yocto20:25
mr_scienceRichBayliss_: np20:25
bluelightningmr_science: I've been that guy... can be difficult sometimes, hang in there :)20:26
*** jbaxter <jbaxter!> has quit IRC20:29
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC20:29
*** joeythesaint <joeythesaint!~jjm@> has quit IRC20:36
*** Bagder <Bagder!> has joined #yocto20:39
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has joined #yocto20:39
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto20:42
*** zeddii_home <zeddii_home!> has joined #yocto20:43
mr_scienceone more jenkins deployment enhancement...20:45
mr_sciencekinda like "just one more theeen leeetle mint..."20:45
*** smartin_ <smartin_!> has quit IRC20:49
*** zerus <zerus!> has quit IRC20:56
*** ant_home <ant_home!> has joined #yocto21:01
*** zerus <zerus!> has joined #yocto21:01
*** RichBayliss_ <RichBayliss_!524466ee@gateway/web/freenode/ip.> has quit IRC21:03
*** exosyst <exosyst!~nick@> has quit IRC21:07
* mr_science wonders why someone's ant build config would suppress all compiler warnings...21:09
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC21:09
mr_sciencemaybe the IDE interface is just too scary with all those warning hihjlights21:18
mr_science*highlights even21:18
-YoctoAutoBuilder- build #225 of nightly-intel-gpl is complete: Success [build successful] Build details are at
*** zenlinux <zenlinux!> has quit IRC21:24
*** zenlinux <zenlinux!> has joined #yocto21:26
*** Circuitsoft <Circuitsoft!ccb603ed@gateway/web/freenode/ip.> has quit IRC21:26
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto21:30
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC21:49
*** tlwoerner <tlwoerner!~tlwoerner@linaro/tlwoerner> has quit IRC21:52
*** ant_home <ant_home!> has quit IRC22:01
*** ericben <ericben!> has quit IRC22:03
*** ericben <ericben!> has joined #yocto22:05
-YoctoAutoBuilder- build #212 of nightly-non-gpl3 is complete: Success [build successful] Build details are at
*** ant_home <ant_home!> has joined #yocto22:10
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-sdspcycdvhhowseg> has quit IRC22:12
*** agust <agust!> has quit IRC22:17
*** andyross <andyross!> has quit IRC22:36
*** doerrpau <doerrpau!> has joined #yocto22:36
*** mulhern <mulhern!> has joined #yocto22:38
*** JimNH3 <JimNH3!> has joined #yocto22:40
*** zenlinux <zenlinux!> has quit IRC22:41
*** W1N9Zr0 <W1N9Zr0!> has quit IRC22:41
*** W1N9Zr0 <W1N9Zr0!> has joined #yocto22:42
*** _julian_ <_julian_!> has joined #yocto22:42
*** jukkar1 <jukkar1!jukka@nat/intel/x-bwhkeabxdzxogcaj> has joined #yocto22:45
*** nitink1 <nitink1!nitink@nat/intel/x-fpvligariwpibuie> has joined #yocto22:45
*** jukkar <jukkar!~jukka@> has quit IRC22:47
*** nitink <nitink!~nitink@> has quit IRC22:47
*** JimNH2 <JimNH2!> has quit IRC22:47
*** _julian <_julian!> has quit IRC22:47
*** zenlinux <zenlinux!> has joined #yocto22:51
*** seebs <seebs!> has quit IRC22:51
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has quit IRC22:56
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC22:56
*** mulhern <mulhern!> has quit IRC23:00
*** ndec <ndec!~ndec@linaro/ndec> has quit IRC23:06
*** smartin <smartin!> has quit IRC23:08
*** mulhern <mulhern!> has joined #yocto23:09
*** sameo <sameo!~samuel@> has quit IRC23:12
*** smartin <smartin!> has joined #yocto23:13
*** ndec <ndec!~ndec@linaro/ndec> has joined #yocto23:13
*** joshc <joshc!~joshc@rhlug/joshc> has quit IRC23:19
*** seebs <seebs!> has joined #yocto23:21
*** mulhern <mulhern!> has quit IRC23:35
*** tlwoerner <tlwoerner!> has joined #yocto23:41
*** tlwoerner <tlwoerner!~tlwoerner@linaro/tlwoerner> has joined #yocto23:41
*** ant_home <ant_home!> has quit IRC23:41
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC23:49
*** joshc <joshc!~joshc@rhlug/joshc> has joined #yocto23:55
*** jonmasters <jonmasters!> has quit IRC23:55
*** jonmasters <jonmasters!> has joined #yocto23:59

Generated by 2.11.0 by Marius Gedminas - find it at!