Thursday, 2013-08-01

*** hollisb <hollisb!> has quit IRC00:11
*** munch <munch!> has quit IRC00:16
*** jchonig <jchonig!~jch@> has joined #yocto00:18
*** _julian_ <_julian_!> has joined #yocto00:49
*** _julian <_julian!> has quit IRC00:52
*** mulhern <mulhern!> has joined #yocto00:59
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:03
*** seebs <seebs!~seebs@> has quit IRC01:07
CircuitsoftIs there a proper place to add files to /etc/profile.d/01:10
*** seebs <seebs!~seebs@> has joined #yocto01:10
*** mulhern <mulhern!> has quit IRC01:35
*** mulhern <mulhern!> has joined #yocto01:42
*** mulhern <mulhern!> has quit IRC01:45
*** challinan <challinan!> has quit IRC01:53
*** mitz <mitz!> has quit IRC02:06
*** mitz <mitz!> has joined #yocto02:07
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has left #yocto02:10
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto02:10
nerdboyCircuitsoft: i see a few things in meta/ that install a file there02:11
nerdboythat's pretty much it...02:12
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC02:20
sgw_Circuitsoft: new files for a recipe you are writing or in general?  You can use a .bbappend file for base-files or create your own recipe that will install the ${sysconfdir}/profile.d and then install your file or files to that dir.  Then in your image install that recipe.02:21
*** nitink <nitink!~nitink@> has quit IRC02:26
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto02:36
*** jchonig <jchonig!~jch@> has quit IRC02:37
*** Squix <Squix!> has quit IRC02:40
*** andyross <andyross!> has joined #yocto02:50
*** andyross <andyross!> has quit IRC02:54
*** andyross <andyross!> has joined #yocto02:56
*** andyross <andyross!> has quit IRC03:27
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC03:29
*** andyross <andyross!> has joined #yocto03:34
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto03:42
-YoctoAutoBuilder- build #232 of nightly-non-gpl3 is complete: Failure [failed Building Images] Build details are at
*** zenlinux <zenlinux!> has quit IRC04:40
*** zenlinux <zenlinux!> has joined #yocto04:40
*** behanw <behanw!> has quit IRC04:47
nerdboysgw_: i was thinking base-files, but it doesn't seem to create it on its own04:52
nerdboyso would recipe be preferred over base-files.bbappend?04:53
*** agust <agust!> has joined #yocto04:59
*** ericben <ericben!> has quit IRC05:04
*** ericben <ericben!> has joined #yocto05:05
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC05:09
*** andyross <andyross!> has quit IRC05:12
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto05:23
*** zecke <zecke!> has joined #yocto05:34
*** melonipoika <melonipoika!> has joined #yocto05:35
*** Jefro <Jefro!> has joined #yocto05:37
*** tor <tor!> has joined #yocto06:14
*** mihai <mihai!~mihai@> has joined #yocto06:29
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto06:46
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto06:46
*** zeeblex <zeeblex!~apalalax@> has joined #yocto06:49
*** AlexG <AlexG!c0c6972c@gateway/web/freenode/ip.> has joined #yocto06:53
*** elmi82 <elmi82!> has joined #yocto06:53
AlexGis Beth around?06:53
*** eballetbo <eballetbo!> has joined #yocto06:57
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:59
*** mprica <mprica!c0c69724@gateway/web/freenode/ip.> has quit IRC07:03
*** eciobanu <eciobanu!c0c69724@gateway/web/freenode/ip.> has quit IRC07:03
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto07:17
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto07:17
*** mckoan|away is now known as mckoan07:21
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC07:25
-YoctoAutoBuilder- build #234 of build-appliance is complete: Failure [failed Building Images_1 Publishing Artifacts] Build details are at
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto07:29
*** levi <levi!> has quit IRC07:31
*** slaine <slaine!~slaine@> has joined #yocto07:35
*** ant_work <ant_work!> has joined #yocto07:36
*** blitz00 <blitz00!stefans@nat/intel/x-frazqytaaynhjwfz> has joined #yocto07:36
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto07:36
*** slaine <slaine!~slaine@> has quit IRC07:41
*** ericben <ericben!> has quit IRC07:42
*** Jefro <Jefro!> has quit IRC07:45
*** levi <levi!> has joined #yocto07:48
*** bluelightning <bluelightning!~paul@> has joined #yocto07:52
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:52
-YoctoAutoBuilder- build #203 of nightly-fsl-arm-lsb is complete: Failure [failed Building Images Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
*** florian_kc <florian_kc!> has joined #yocto07:56
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:56
*** florian_kc is now known as florian07:56
*** swex <swex!~swex@> has quit IRC07:57
*** swex <swex!~swex@> has joined #yocto07:58
*** ericben <ericben!> has joined #yocto07:59
bluelightningmorning all08:02
-YoctoAutoBuilder- build #204 of nightly-fsl-arm is complete: Failure [failed Building Images Building Toolchain Images Building Toolchain Images_1 Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #245 of nightly-intel-gpl is complete: Success [build successful] Build details are at
*** Saur1 <Saur1!pkj@nat/axis/x-xeffojlhkjontlrw> has quit IRC08:27
*** honschu <honschu!> has joined #yocto08:28
*** honschu <honschu!> has quit IRC08:28
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto08:28
*** Saur <Saur!pkj@nat/axis/x-zosixknlnywhvczb> has joined #yocto08:28
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC08:31
rburtonabelloni: about network config for sato, you should have a network icon at the top that will configure basic stuff (its a UI to connman)08:34
*** panda84kde <panda84kde!> has joined #yocto08:42
*** slaine <slaine!~slaine@> has joined #yocto08:47
*** belen <belen!Adium@nat/intel/x-lfjnhtsktqtabttv> has joined #yocto08:53
*** belen <belen!Adium@nat/intel/x-lfjnhtsktqtabttv> has quit IRC08:59
abellonirburton: I didn't see anything08:59
abelloniis connman part of core-image-sato ?08:59
rburtonthere's a network icon in the titlebar thingy09:00
rburtonwell, should be!09:00
*** belen <belen!~Adium@> has joined #yocto09:00
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto09:01
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:03
ant_workrburton: you once said sato could maybe fit on qvga screens with a bit of work?09:03
rburtonant_work: depends how much you want to use09:05
rburtonant_work: the desktop and panel should scale fine09:05
rburtonjust don't expect other gtk+ widgets to work on qvga09:05
rburtonthere's an ancient patch against gtk2 to make a qvga-friendly file selector09:06
rburtonincredibly bitrotted though09:06
rburtonbut if you just want to use the panel or desktop, changing the font and icon size should do enough09:06
ant_worktbh my last try was done long ago...back then the desktop did not fit on 32009:08
ant_workwell, exactly I've rotated qvga so th etopbar is rendered in 240pix09:08
rburtonant_work: fwiw, i'm porting the desktop and panel to gtk3 right now09:09
rburtonant_work: so if you have any feature requests tell me now while the code is still changing :)09:09
rburton(the panel's positioning code was just simplified massively)09:09
ant_workI'll send you couple of screenshots09:17
*** amarsman <amarsman!~marsman@> has quit IRC09:18
*** jackmitchell <jackmitchell!> has quit IRC09:20
*** jackmitchell <jackmitchell!> has joined #yocto09:21
*** vicky <vicky!~vicky@> has joined #yocto09:25
vickyhi yocto. How to clean all packages compiled even downloads and start a fresh build?09:25
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto09:29
-YoctoAutoBuilder- build #2 of eclipse-plugin-juno is complete: Failure [failed Building Eclipse Plugin Publishing Artifacts] Build details are at
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC09:30
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto09:31
Noorhello guys09:35
Nooris there any plan to replace qt4 with qt5 in yocto layer for 1.5 release09:35
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:39
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto09:41
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:41
rburtonNoor: not for 1.5, no09:46
Noorrburton: thanks09:46
rburtonNoor: feel free to start that debate when 1.5 freeze for 1.6 though :)09:46
Noorso we have to use meta-qt5 layer then09:46
rburtonthat's what we'd be pulling directly in anyway09:47
rburtonhooray layer model :)09:47
Noorrburton: is there any link which describe what is planned for the release09:47
rburtontarget features are all in bugzilla09:48
*** dRp3pP3r <dRp3pP3r!d5bf22ee@gateway/web/freenode/ip.> has joined #yocto09:50
Noorrburton: thanks it helps09:50
dRp3pP3rhello everybody. i got a little problem with gnutls and libtasn on branch master...09:50
dRp3pP3rgnutls provides but libtasn needs
dRp3pP3rcreating a softlinks lets it compile, but the build fails at do_rootfs() because bitbake realises no one provides
rburtondRp3pP3r: just rebuilding tasn should solve that09:52
rburtonthe question is why didn't it rebuild itself :(09:52
rburtondRp3pP3r: so try cleaning and rebuilding tasn09:53
dRp3pP3ron it. thanks in advance. :)09:53
dRp3pP3rok, how exactly do i do that? (whats the name of the package?) refetching and compiling gnutls didn't work, even though the recipes are in the same directory...09:58
dRp3pP3rgot it, libtasn1, not libtasn09:59
*** fgretief <fgretief!~chatzilla@> has joined #yocto10:00
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC10:03
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto10:05
dRp3pP3rwell, didn't work. gnutls compiles, as always, but compiling wpa_supplicant fails due to missing dependencies of libgnutls (libtasn1.s0.3)10:05
dRp3pP3rthe exact error is: .../ld: warning:, nedded by ..../yocto/build/tmp/sysroots/imx6qsabrelite/usr/lib/, not found10:10
rburtonah the dep was the wrong way around10:11
rburtonrebuild gnutls10:11
rburtonhave you been switching versions up and down?10:11
rburtonthat can cause issues like this if you're not careful10:11
dRp3pP3rnot up and down, only up :)10:12
*** JimBaxter <JimBaxter!> has joined #yocto10:12
dRp3pP3rgnutls rebuilded when i refetched and builded libtasn10:12
*** amarsman <amarsman!~marsman@> has joined #yocto10:13
*** igrigorx <igrigorx!c0c69725@gateway/web/freenode/ip.> has quit IRC10:17
*** dRp3pP3r_ <dRp3pP3r_!d5bf22ee@gateway/web/freenode/ip.> has joined #yocto10:18
*** dRp3pP3r <dRp3pP3r!d5bf22ee@gateway/web/freenode/ip.> has quit IRC10:19
dRp3pP3r_seems to have worked when i cleand gnutls, libtasn and wpa-supplicant and rebuilt. thanks. :)10:20
rburtondRp3pP3r_: hopefully it doesn't happen again. linkage gets noticed and will cause re-builds, so something *odd* happened10:27
dRp3pP3r_hm. can't really explain that one to me, because the package that was updated was wpa-supplicant. the linkage between gnutls and libtasn1 should not have been touched...10:28
rburtonlets just pretend nothing happened ;)10:29
*** JimBaxter <JimBaxter!> has quit IRC10:30
dRp3pP3r_happened? did i miss sonething? ;) btw: got the next one with tslib (no one provides libts >= 1.0+gitr0+<git-hash>) and cleaning won't work. can one compare version numbers including a git-hash using relative operators?10:31
rburtonthe gitr0 will be gitr1 on the next build10:32
rburtonthough, what platform are you using that is using tslib?  there was discussion here yesterday about what is remaining that still uses it.10:32
dRp3pP3r_ah. than that's odd. tslib-calibrate wants libts, which is provided by libts. both in the same version.10:32
dRp3pP3r_my platform is a Freescale i.Mx6Quad on a BoundaryDevices Sabrelite Eva-Board10:33
rburtonits at times like this that i blow away my deploy directory and relevant stamps10:33
rburtonqt on framebuffer?10:33
rburtonor what ui stuff10:33
dRp3pP3r_qt 4.8.x on a framebuffer, yes. matchbox-desktop on X-Server...10:34
dRp3pP3r_doesn't matter, kicked the touchscreen out of the image, don't have one here right now. problem for future-dRp3pP3r :)10:37
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:39
*** joeythesaint <joeythesaint!~jjm@> has joined #yocto10:41
*** amarsman <amarsman!~marsman@> has quit IRC10:50
*** bluelightning_ is now known as bluelightning10:56
*** swex <swex!~swex@> has quit IRC11:07
*** GunsNRose <GunsNRose!~GunsNRose@> has joined #yocto11:16
*** zecke <zecke!> has quit IRC11:25
*** acidfoo <acidfoo!~nib@> has quit IRC11:33
*** mulhern <mulhern!> has joined #yocto11:34
dRp3pP3r_rvurton: correction. shows up again.11:34
dRp3pP3r_im meant rburton11:34
dRp3pP3r_i mean libtasn11:35
-YoctoAutoBuilder- build #235 of nightly-x86 is complete: Success [build successful] Build details are at
dRp3pP3r_i'll fix it and come back with the solution, but for now, i need to change the line...11:41
ant_workzombie in your kitchen?11:41
*** dRp3pP3r_ <dRp3pP3r_!d5bf22ee@gateway/web/freenode/ip.> has quit IRC11:41
*** zecke <zecke!> has joined #yocto11:41
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto11:44
*** zecke <zecke!> has quit IRC11:49
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC11:55
*** mihai <mihai!~mihai@> has quit IRC11:59
*** joseppc <joseppc!> has joined #yocto12:00
*** behanw <behanw!> has joined #yocto12:10
*** chris__ <chris__!> has quit IRC12:20
*** elmi82 <elmi82!> has quit IRC12:27
*** elmi82 <elmi82!> has joined #yocto12:29
*** darknighte_znc is now known as darknighte12:29
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto12:31
*** elmi82 <elmi82!> has joined #yocto12:31
*** Crofton|work <Crofton|work!> has joined #yocto12:39
*** eren <eren!~eren@unaffiliated/eren> has quit IRC12:41
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto12:44
-YoctoAutoBuilder- build #194 of nightly is complete: Failure [failed Building Images Building Images_10] Build details are at
*** zenlinux <zenlinux!> has quit IRC12:56
*** zecke <zecke!~ich@> has joined #yocto12:57
*** mihai <mihai!~mihai@> has joined #yocto13:00
*** jchonig <jchonig!~jch@> has joined #yocto13:09
*** mitz <mitz!> has quit IRC13:10
*** dRp3pP3r <dRp3pP3r!d5bf22ee@gateway/web/freenode/ip.> has joined #yocto13:10
*** fgretief <fgretief!~chatzilla@> has quit IRC13:12
*** mitz <mitz!> has joined #yocto13:12
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC13:21
*** tbn <tbn!~tbn@> has joined #yocto13:22
*** tbn is now known as Guest6844713:22
*** tasslehoff <tasslehoff!~tasslehof@> has quit IRC13:30
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zdjpywppdhhadred> has joined #yocto13:33
*** nitink <nitink!~nitink@> has joined #yocto13:45
*** dRp3pP3r <dRp3pP3r!d5bf22ee@gateway/web/freenode/ip.> has left #yocto13:45
*** Guest93981 <Guest93981!86bfdd4a@gateway/web/freenode/ip.> has quit IRC13:54
*** zecke_ <zecke_!~ich@> has joined #yocto14:06
*** zecke <zecke!~ich@> has quit IRC14:09
*** jchonig <jchonig!~jch@> has quit IRC14:09
*** munch <munch!> has joined #yocto14:17
*** ErkiS <ErkiS!> has joined #yocto14:25
*** jmdelos_ <jmdelos_!> has quit IRC14:28
*** Jefro <Jefro!> has joined #yocto14:30
ErkiSis there a convenient way of installing RPMs on my target device? I'm trying to get build-essentials installed (on Gumstix Overo), but chasing down each needed RPM with all its dependencies is hopeless14:31
*** jmpdelos <jmpdelos!> has joined #yocto14:34
bluelightningErkiS: packagegroup-core-buildessential should contain what you want14:36
bluelightningwell, s/contain/pull in/14:36
ErkiSbluelightning, I should bitbake packagegroup-core-buildessential?14:38
ErkiSgetting "ERROR: Nothing PROVIDES 'packagegroup-core-buildessential' "14:38
*** tor <tor!> has quit IRC14:38
bluelightningErkiS: you can, or you can just add it to IMAGE_INSTALL if you want it in the image by default14:39
*** elmi82 <elmi82!> has quit IRC14:46
*** ErkiS <ErkiS!> has quit IRC15:10
*** mulhern <mulhern!> has quit IRC15:17
*** zenlinux <zenlinux!> has joined #yocto15:18
*** hollisb <hollisb!> has joined #yocto15:18
*** mulhern <mulhern!> has joined #yocto15:19
*** ant_work <ant_work!> has quit IRC15:23
*** slaine <slaine!~slaine@> has quit IRC15:25
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zdjpywppdhhadred> has quit IRC15:28
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-piyqhodkhrcygiku> has joined #yocto15:29
*** TuTizz <TuTizz!~TuTizz@> has quit IRC15:31
*** amarsman <amarsman!~marsman@> has joined #yocto15:43
*** andyross <andyross!> has joined #yocto15:44
*** zecke_ <zecke_!~ich@> has quit IRC15:48
*** seebs <seebs!~seebs@> has quit IRC15:48
*** mulhern <mulhern!> has quit IRC15:52
*** seebs <seebs!~seebs@> has joined #yocto15:54
*** davest <davest!Adium@nat/intel/x-azpndujhybsycxcm> has quit IRC15:55
*** eballetbo <eballetbo!> has quit IRC15:59
*** zeeblex <zeeblex!~apalalax@> has left #yocto16:00
*** mulhern <mulhern!> has joined #yocto16:01
*** mckoan is now known as mckoan|away16:01
*** GunsNRose <GunsNRose!~GunsNRose@> has quit IRC16:02
*** belen <belen!~Adium@> has quit IRC16:03
*** belen <belen!~Adium@> has joined #yocto16:05
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:05
*** mihai <mihai!~mihai@> has quit IRC16:05
*** AlexG <AlexG!c0c6972c@gateway/web/freenode/ip.> has quit IRC16:06
*** Guest68447 <Guest68447!~tbn@> has quit IRC16:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:07
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-piyqhodkhrcygiku> has quit IRC16:08
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-pynhotmejkjeizlt> has joined #yocto16:16
*** eren <eren!~eren@unaffiliated/eren> has quit IRC16:17
*** bluelightning_ is now known as bluelightning16:21
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:21
*** mr_science <mr_science!> has joined #yocto16:22
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:22
*** zecke <zecke!> has joined #yocto16:28
*** belen <belen!~Adium@> has quit IRC16:35
*** zedd_ <zedd_!~ddez@> has quit IRC16:43
*** pidge <pidge!~pidge@> has joined #yocto16:45
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:51
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:54
*** belen <belen!~Adium@> has joined #yocto16:54
*** zeddii <zeddii!~ddez@> has joined #yocto16:56
*** yocti sets mode: +o Jefro17:03
*** joseppc <joseppc!> has quit IRC17:13
*** yocti sets mode: -o Jefro17:16
*** khem <khem!> has joined #yocto17:19
*** ka6sox is now known as ka6sox-farfarawa17:23
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:27
*** Jefro <Jefro!> has quit IRC17:29
*** Jefro <Jefro!> has joined #yocto17:30
*** belen <belen!~Adium@> has quit IRC17:34
*** vicky <vicky!~vicky@> has quit IRC17:34
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto17:36
*** amarsman <amarsman!~marsman@> has quit IRC17:39
*** ash_charles <ash_charles!> has joined #yocto18:01
*** eren <eren!~eren@unaffiliated/eren> has quit IRC18:07
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC18:07
*** gmacario <gmacario!> has quit IRC18:13
*** quatre <quatre!c0926547@gateway/web/freenode/ip.> has quit IRC18:14
*** panda84kde <panda84kde!> has quit IRC18:15
*** mulhern <mulhern!> has quit IRC18:18
*** mulhern <mulhern!> has joined #yocto18:23
-YoctoAutoBuilder- build #3 of eclipse-plugin-juno is complete: Success [build successful] Build details are at
*** davest <davest!Adium@nat/intel/x-jcfupoeldehmojyw> has joined #yocto18:29
*** jackmitchell <jackmitchell!> has quit IRC18:38
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC18:38
*** jackmitchell <jackmitchell!> has joined #yocto18:40
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto18:40
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto18:41
*** swex <swex!~swex@> has joined #yocto18:52
*** Crofton|work <Crofton|work!> has quit IRC18:53
* kergoth mutters18:55
*** Crofton|work <Crofton|work!> has joined #yocto19:00
*** smartin <smartin!> has quit IRC19:01
mr_sciencei pretty much do that every day...19:11
mr_scienceif you get close enough to hear, i kinda sound like popeye...19:12
*** joeythesaint <joeythesaint!~jjm@> has quit IRC19:15
kergothone of those frustrating days..19:16
seebsOh, kergoth. I may be about to send a flurry of suggested patches to meta-sourcery. Where "about-to" means a month from now I'll be saying "haha no I haven't got that working yet". :)19:20
kergothheh :)19:21
kergothwhat will they do?19:22
seebsWell, long story there! We're now getting CS toolchains which also have a layer that provides bbappends to build "normally" (for Yocto) using the CS patches.19:22
seebsOur plan is to drop all the local stuff we had for supporting partial rebuilds, and messing around with binutils on targets, and just use that layer for all those things.19:22
seebsBut, there is a cleanup pass I'd done to external-csl-toolchain once, which I'd like to recreate, which did a better job of separating out "copy the multilib files we care about somewhere useful" from "install these files and package them".19:23
seebsWhich the leads to support for an alternative distribution model, where instead of a completely unpacked libc directory, we have a selection of cpio.gz archives which correspond to multilibs.19:24
seebsFor MIPS, the libc directory for our unweildy selection of multilibs is about 1.8GB as-shipped, and bloats to over 5GB if it goes through a git server (breaking all the hard links).19:24
*** zecke <zecke!> has quit IRC19:25
seebsIn our distribution, we're distributing about 750MB of compressed archives, with the useful trait that any *given* install only has to decompress about 100MB of that, and it ends up being faster in total than unpacking the original archive would have been.19:25
seebsSo basically, it checks for actual unpacked files, and does the same thing external-csl-toolchain did (roughly) if it finds those, but also supports a faster/smaller unpacking mechanism when appropriate.19:26
seebs… unwieldy. I can spell, really.19:27
seebsI also had stuff to make the toolchain wrappers (which exist separately) become enabled mostly-automatically with binary toolchains, which simplifies life for packages which end up failing to specify the right CCARGS, although I think all the known cases got fixed, so I might just drop that.19:28
* mr_science adds USE="aspell" to seebs irc client19:30
seebsI can't use spell checkers, they drive me batty.19:30
seebsTheir failure rate is usually higher than mine, at least for what I write.19:31
mr_sciencei wasn't suggesting anything like M$ autocorrect19:31
mr_sciencejust some red squiggly highlights...19:32
sgw_oh, is that whta those are for ;-)19:33
seebsI hate the red squiggles. They're … not very reliable. Also, I occasionally do real proofreading, and apparently most proofreaders find that if you get in the habit of having those on, you stop being able to proofread as reliably.19:34
seebsI will occasionally run a spell checker over a document, but I don't like having it always-on, because they really aren't very good at it.19:35
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:37
mr_scienceonly as good as their dictionaries...19:37
mr_sciencealso kinda humorous how firefox defaults to crazy language that's completely unrelated to my locale settings19:38
mr_sciencecurrently cuban spanish...19:39
*** jchonig <jchonig!> has joined #yocto19:48
kergothhuh, kind of surprised 'tac' isn't posix/sus19:53
*** zenlinux <zenlinux!> has quit IRC19:53
*** zenlinux <zenlinux!> has joined #yocto19:54
-YoctoAutoBuilder- build #3 of eclipse-plugin-kepler is complete: Success [build successful] Build details are at
*** levi <levi!> has quit IRC19:56
*** darknighte is now known as darknighte_znc19:59
*** jmpdelos <jmpdelos!> has quit IRC20:00
*** jmpdelos <jmpdelos!> has joined #yocto20:01
seebsI think it may be because tac is obviously not possible to generically implement for stdin.20:06
*** levi <levi!> has joined #yocto20:07
kergothtrue, can't treat everything as a file if that's the operation you want to do20:13
kergothgood point20:13
kergothstill, quite handy :)20:13
*** silviof2 <silviof2!> has joined #yocto20:16
seebsI wrote an unsort(1) utility.20:16
seebsI have, on my very low priority list of things to do: making it correctly parse, and warn about errors in the specification of, all the sorting options available to the POSIX sort(1).20:17
mr_scienceseebs: stop, you're making me all goose-pimply...20:18
seebsObviously, implementing the functionality would be much, much, easier than parsing the options.20:18
seebsOption parsing is one of those problems which sounds REALLY easy until you do it.20:19
seebs… argh20:19
seebsI was thinking about that, and now I've realized that there is an obvious way in which I could make my option parser more useful in an interesting way.20:20
seebsIt supports getopt-like strings, with the extension that, just as "f:" means "option f takes an argument", "f#" means "option f takes a numeric argument". Good so far.20:20
mr_scienceif it's anything above "trivial" i tend to use getopts20:21
seebsI have now realized that I might find life easier if it also supported "f::" meaning "option f takes exactly two arguments".20:21
seebsIn sh, I use getopts. Or, in some cases, a very clever portable near-reimplementation of it in sh I got from Gary Vaughan during the work on the shell book.20:21
mr_sciencebut i'll admit to writing a lot of shell script with custom check_input functions and no getopts...20:22
seebsBut being a sort of compulsive programmer, and playing a game that has a Lua-based addon development environment, I also maintain a getopts-alike for parsing commands in that.20:22
* mr_science should take his own advice more often20:22
seebsAnd there I feel some freedom to experiment.20:22
seebsI actually maintain an options library in C, although most of its features turned out to be ill-considered. But it was an interesting idea.20:23
mr_sciencebut i'll bet you learned something from your "ill-considered" implementation...20:23
seebsIn particular, it has the fancy feature of letting you save options to a .foorc file, or load them from such a file, so you can trivially set default options. This seemed like SUCH a good idea at the time. I think I've used it twice.20:23
seebsOh, heck yeah. This is why I am always happy to make an excuse to go write something. I know people who write prose, and they insist that no words you write are a waste. I have found this to be true of code, also.20:24
mr_sciencethe main difference being the concept of throwing out implementation #120:25
mr_sciencesince *not* throwing out rough drafts of prose is much less likely to bite you in the ass later20:25
seebsSomeone, and I forget who, but… Might have been Joel Spolsky? Argued recently, and moderately persuasively, that sometimes refactoring may be better than throwing away the first implementation.20:27
seebsBecause some significant amount of the "cruft" is actually handling real problems.20:27
seebs <-- yup20:27
mr_sciencei wouldn't disagree with that20:27
mr_scienceprobably depends a lot on the individual person/code20:28
seebsIt does. Also on scale, timing, scheduling, and how far off the original requirements were.20:29
mr_sciencemany variables...20:29
seebsIn general, my experience has been that all the clear rules as to what to do are wrong, and you are better off having multiple factors and weighing them.20:29
seebsThis is a good strategy especially because it is easy to explain how to do it so novices can start using it right away. *nods wisely*20:30
kergothseebs: its a good article, he makes a good point about the implicit knowledge carried in the code. i know i've attempted rewrites on things before and ended up re-rolling the workarounds for the ocrner cases again which i didn't pull over at first thinking they weren't necessary20:34
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto20:36
seebsThis is highly relevant to the task I've just started on of trying to figure out whether to (1) uprev my wr-toolchain layer, or (2) try to get the fixes in it that I actually still need into meta-sourcery.20:37
seebsI think I am going with #2.20:37
*** silviof2 <silviof2!> has quit IRC20:40
*** silviof2 <silviof2!> has joined #yocto20:41
mr_sciencethat's one of the points i've tried to explain repeatedly over the years...20:44
*** silviof2 <silviof2!> has quit IRC20:44
mr_scienceusually not very successfully for one reason or another20:45
*** silviof2 <silviof2!> has joined #yocto20:46
leviRegarding the Joel on Software article, there are also industry examples of market-leading companies having their lunch handed to them because they *didn't* rewrite their software.20:46
mr_scienceit just seems harder than it should be to get some people to understand that20:46
mr_scienceie, that writing code is fundamentally a knowledge-capturing activity20:47
mr_sciencemaybe i just need a bigger clue stick20:47
levimr_science: I worked for a while with a jr. engineer who seemed really weak at figuring out how to do things. After talking with him for a while, it became apparent to me that his main problem was that he went out of his way to avoid *reading* code.20:49
leviHow people expect to *write* coherent things in a language they're not adept at *reading* first is beyond me.20:50
mr_sciencebut yeah, Joel's mom didn't raise no dummies20:51
mr_sciencenot that i couldn't argue with over some things...20:51
mr_science*him even20:51
leviI guess it doesn't help much that low-level languages like C make it very easy to write highly imperative code, in which the actual code provides a lot of tiny explicit details without ever making clear *why* those operations are being ordered.20:52
mr_scienceyeah, some tools (like that example) require extra thought/work/effort to mitigate those kinds of things20:53
mr_sciencewhich is why i like helpful languages like Ada...20:53
* mr_science waits for the groans and jaw-popping20:54
* kergoth chuckles20:54
levimr_science: I really need to learn Ada. I mostly enjoy statically-typed functional languages (Haskell, OCaml) for exploratory/modeling programming, because it helps you get the design hashed out and coherent before you get around the the implementation details.20:57
leviFrom what I've seen of Ada, it's highly verbose but does provide a flexible set of tools for describing the way you expect things to work and having the compiler verify that you're operating within those constraints.20:58
mr_scienceAda has some lovely features that are still missing from most other languages20:59
mr_sciencesince Ada 83 even20:59
mr_sciencewhy they're still missing is very good question20:59
* fray suspects because of the reputation of Ada21:00
mr_scienceprobably goes along with the whole "software engineering do as we say not as we do" thing21:00
frayand specifically the reams of documentation when Ada is used in gov't contracted software21:00
*** zenlinux <zenlinux!> has quit IRC21:00
mr_sciencereams of govt documentation software docs are pretty much independent of the implementation language...21:01
*** zenlinux <zenlinux!> has joined #yocto21:01
mr_scienceer, "software documentation"21:01
frayya.. but Ada was designed around that21:01
mr_sciencenot really21:01
leviI think they're primarily missing because no one has done any R&D at the level of C/Ada languages in a long time. You just use C or C++ and deal with it, and those can't change much due to massive amounts of code and trained programmers that can't be obsoleted.21:02
mr_sciencethe "myths" of Ada revealed...21:02
frayfrom what I saw it was.. (I saw it from a Honeywell perspective in the late 1980s)21:02
*** ant_home <ant_home!> has joined #yocto21:02
fraythe wall of Ada manuals was insane.. the reams of "you must do it this way" docuemnts from the gov't were insane..21:03
* mr_science spent 20+ years doing IV&V on DoD launch range systems21:03
leviAda was designed around the idea of reliable, deterministic systems.21:03
frayit led to a bad taste in new programers, who said I won't work on system slike that21:03
fraylevi, absolutely.. and I think it had it's place21:03
mr_scienceAda was designed to handle several different problem domains, but mostly the design is meant to iprove software quality21:04
leviThe current 'state of the art' way to do that is apparently gigantic software systems like UML modeling and code extraction tools.21:04
mr_sciencenothing specific to DoD about that21:04
frayya, I'm not saying what we have today is any better frankly..21:04
mr_scienceif there's one thing i've seen over those 20+ years, it's that almost nobody knows the Ada standards or design criteria21:05
mr_sciencebut they all likt to talk about it...21:05
*** ynezz <ynezz!> has quit IRC21:06
*** ynezz <ynezz!> has joined #yocto21:06
mr_sciencei also get that some people just don't like things like range variables that won't allow out-of-bounds indeces and things like that21:07
mr_sciencepersonally, i need all the help i can get to eliminate bugs21:07
frayheh, from my experience language usage is very cyclical..21:07
leviAmen to that.21:07
fraythere seems to always be the language of the month behavior.. and then longer term languages..21:08
fray(C, Ada, Fortran, Cobol...)21:08
ant_homelet's port INTERCAL21:08
leviAs Alan Kay observed, we have a programming 'pop culture'.21:08
mr_sciencei think Fortran wins the geriatric language prize21:08
fraybut wow, it's still being used for new development.. :/21:09
fray(I'd rather program Fortran then cobol though)21:09
mr_sciencevery useful for certain things, yet still a 50's language...21:09
leviIt's easier to write high-performance numeric code in Fortran than C, though.21:09
leviYou don't have to write a bunch of aliasing annotations all over the place.21:10
leviI was in the supercomputing industry for a few years, and Fortran is very much alive and well there.21:10
frayI have a hated for AS/400 & Cobol due to a course I took at my university..21:10
mr_sciencethe only real knock on Ada i can think of is that they just did a crappy job selling it21:11
leviCobol was just kind of a bad idea that gets re-discovered every so often.21:11
mr_sciencegiven the prevalence of myths still floating around...21:11
levi"Let's write a programming language that untrained managers can understand!"21:11
*** Jefro <Jefro!> has quit IRC21:11
mr_sciences/programming language/magazine ad/21:12
fraylevi (and in my university case) be sure to tell all of the "programmers in the room" that you are going to show them the 'right way to program'..21:12
* fray is still annoyed (or worse) at that professor... and that was about 18 years ago21:12
levimr_science: Well, compared to other languages of its vintage, it was a relatively large and complex language. Also, from my understanding there was a long period where there were no free compilers available for it.21:13
mr_sciencelevi: the latter period was mostly while the original 83 standard was still under development21:13
frayheh CDC's uTutor was better then Cobol IMHO21:13
leviI don't think it's possible to understate the importance of the open, freely-sharable nature of Unix and C to their current ubiquity.21:14
mr_scienceit's probably still the only language with a compiler validation test suite *or* a standard before compiler implementation21:14
mr_scienceboth of which are Good Things21:15
leviThey are not ubiquitious because they're the *best*, but because they're relatively small, simple, portable, and freely available.21:15
mr_scienceyeah, but have you tried any of the "free" non-GNU C compilers?21:16
mr_sciencepretty easy to find compiler bugs in them21:16
mr_scienceat least it used to be...21:16
*** lpapp_ <lpapp_!> has joined #yocto21:16
*** lpapp_ <lpapp_!~lpapp@kde/lpapp> has joined #yocto21:16
leviIf you haven't read the UNIX-HATERS Handbook, it's entertaining reading even if you like Unix.21:16
lpapp_levi: why21:17
mr_sciencei pretty sure i read that stuff a loooong time ago, along with the original BOFH stories...21:17
levimr_science: On the other hand, it's also not uncommon to find bugs in obscure parts of gcc. I ran into one or two many years ago while doing work on a NIOS2-based system.21:18
mr_sciencemaybe it's time to skim it again in the cold light of ...  something...21:18
mr_sciencelevi: didn't say gnu code was bug-free21:19
levilpapp_: It's filled with humorous rants, many of which come from users of other contemporary systems that were more advanced in a lot of ways.21:19
mr_sciencejust orders of magnitude cleaner usually...21:19
leviMy initial experience with C code bases was actually from reading the code for MUD-style games.21:20
mr_scienceokay, i think i finished this bash script about 25 minutes ago...21:20
leviSpecifically the Tiny- variety.21:20
mr_scienceoops, forgot my die() function21:21
seebsI mostly learned C from roguelikes.21:21
leviIt was very enlightening to see how a couple of programs that appeared very similar to users could be implemented so differently, and how much clearer one was than the other.21:21
leviOddly enough, the clearer one tended to crash a lot less...21:21
mr_sciencefunny how that works...21:22
mr_sciencecan you say "obfuscated C contest"?21:22
*** swex <swex!~swex@> has quit IRC21:24
*** swex <swex!~swex@> has joined #yocto21:24
mr_sciencejust the fact that you can actually do some of that stuff with C is pretty scary21:26
*** Jefro <Jefro!> has joined #yocto21:31
*** dvhart <dvhart!> has quit IRC21:32
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC21:32
mr_sciencewhen i weigh making a .emacs (again) against paying $79 for sublime21:32
mr_sciencei'm thinking the $79 is a good investment...21:32
mr_sciencesince i haven't made a custom .emacs in years21:33
kergothi picked it up, but i do too much remotely over ssh to make much use of it :(21:34
mr_scienceworks okay over ssh -Y21:35
mr_sciencedamn, it's like those guys read my mind...21:35
* mr_science gets out his foil hat again21:36
mr_sciencejust in case...21:36
*** Jefro <Jefro!> has quit IRC21:42
leviI like sublime. The editor GUI is very slick/optimized, and it's extensible.21:51
leviOn the other hand, emacs is very familiar, so I mostly just use emacs.21:51
leviThere are a couple of pre-made .emacs directories that are nice.21:51
leviLike the Emacs Starter Kit21:52
*** mulhern <mulhern!> has quit IRC21:56
mr_scienceyeah, i specific things in mine so i had to make my own22:04
mr_science*wanted even22:04
*** Jefro <Jefro!> has joined #yocto22:05
mr_sciencesublime seems to have almost exactly what i need working out-of-the-box22:05
mr_scienceplus other stuff i haven't even played with yet22:05
leviFor me, it's not the nice features but the muscle memory for standard emacs bindings that's got me stuck with emacs. :)22:06
leviAlthough I sometimes make extensive use of org-mode22:06
mr_sciencelike kergoth, i ended up doing so much work over shell connections i got used to simple22:07
*** mulhern <mulhern!> has joined #yocto22:07
mr_sciencei need to break out of that mold...22:08
seebsOkay, before I spend a huge amount of time tracking this down… Had a build fail because <rpc/rpc.h> was absent. Using binary toolchain which may well not have it. Just wondering whether that's "report to vendor", or "don't be silly, turn on rpc in DISTRO_FEATURES", or what...22:10
mr_scienceheh, my sdk build failed last night with a missing /bin/sed in the native sysroot22:11
mr_sciencei filed a bug, but it sort-of felt wrong...22:11
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-pynhotmejkjeizlt> has quit IRC22:18
*** Jefro <Jefro!> has quit IRC22:26
*** Jefro <Jefro!> has joined #yocto22:26
*** hans <hans!> has joined #yocto22:36
*** mulhern <mulhern!> has quit IRC22:42
*** mulhern <mulhern!> has joined #yocto22:46
*** mulhern <mulhern!> has quit IRC22:47
*** agust <agust!> has quit IRC23:01
-YoctoAutoBuilder- build #4 of eclipse-plugin-juno is complete: Failure [failed Building Eclipse Plugin Publishing Artifacts] Build details are at
mr_scienceso now that i look again, sublime does fall short of vi in several areas23:11
seebsI seem to recall having tried sublime some, and not been especially happy, but… It is hard for me to learn editors.23:15
mr_scienceit looks pretty nice at first, and i do like the fact that certain things Just Work without any fiddling23:16
mr_sciencewhen you look a little closer, it's short on language sensitivity and a few other things23:17
seebsI mostly don't use language-sensitive features in editors, and actually go around turning them off. I never got used to things like syntax highlighting, and tend to find them distracting.23:18
levimr_science: If you do much C programming, there's an interesting integration of clang with sublime to catch errors on the fly.23:28
mr_sciencedepends on the color scheme, but i *do* find syntax highlighting helpful23:28
mr_sciencelevi: now yer talkin'23:29
mr_sciencemore analysis tools should be "built-ins"23:29
mr_scienceof course, with Ada the compiler pretty much does that23:30
mr_sciencepersonally, i would much rather fix compile errors than chase runtime bugs...23:31
*** nitink <nitink!~nitink@> has quit IRC23:35
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:42
*** zenlinux <zenlinux!> has quit IRC23:46
*** hollisb <hollisb!> has quit IRC23:46
*** nitink <nitink!~nitink@> has joined #yocto23:50
*** zeddii <zeddii!~ddez@> has quit IRC23:50
*** andyross <andyross!> has quit IRC23:51
khemrburton: I am running into an issue which boils down to this fix
yoctiBug 2597: normal, Medium+, 1.3 M5, constantinx.musca, VERIFIED FIXED, intltool is missing intltool.m423:52
khemrburton: why is RDEP on a -dev package added ?23:52
khemIMO needed files should have been moved into gettext main package23:52
khemand dependency on gettext be created23:52
khemthe description in bug its not clear what it fixed and what was broken23:53
*** zeddii <zeddii!~ddez@> has joined #yocto23:55
*** swex <swex!~swex@> has quit IRC23:56

Generated by 2.11.0 by Marius Gedminas - find it at!