**** BEGIN LOGGING AT Tue Mar 18 02:59:58 2014 Mar 18 07:58:04 *gäsp* morning Mar 18 07:58:43 gomorron Mar 18 08:04:06 good morning Mar 18 08:06:40 kergoth: fedora is doing it the otherway around, /bin is a symlink to /usr/bin Mar 18 09:32:18 morning all Mar 18 09:48:59 bluelightning, morning Mar 18 09:49:07 hi kroon Mar 18 12:12:08 koen Mar 18 12:12:37 ERROR: ExpansionError during parsing /home/griftw/w/danny/setup-scripts/sources/meta-openembedded/meta-efl/recipes-efl/e17/flame_svn.bb: Failure expanding variable autotools_do_configure: ShellSyntaxError: LexToken(LPARENS,'(',0,0) Mar 18 12:12:37 followed by: Mar 18 12:12:38 LexToken(TOKEN,'False,',0,0) Mar 18 12:12:38 LexToken(TOKEN,"'82070'",0,0) Mar 18 12:12:38 LexToken(RPARENS,')',0,0) Mar 18 12:12:38 LexToken(TOKEN,'-r0.0/E-MODULES-EXTRA/flame/configure.in',0,0) Mar 18 12:12:38 LexToken(TOKEN,'-o',0,0) Mar 18 12:13:04 something went wrong Mar 18 12:13:44 my cmake was doing strange sysroots directory concatination so I decided to oebb.update and seems like we went to yocto 1.5 with error Mar 18 12:33:47 what is even more bizarre Mar 18 12:33:53 if I do a bitbake -D Mar 18 12:33:58 it then give another file Mar 18 12:34:05 ERROR: ExpansionError during parsing /home/griftw/w/danny/setup-scripts/sources/meta-openembedded/meta-efl/recipes-efl/e17/exalt-client_svn.bb: Failure expanding variable autotools_do_configure: ShellSyntaxError Mar 18 12:34:08 bizarre! Mar 18 13:59:18 aaarhg I need help Mar 18 13:59:58 pompomJuice: branch mismatch perhaps? Mar 18 14:00:05 I have no idea Mar 18 14:00:23 well, are you using branch "danny" for all of the layers in your configuration? Mar 18 14:00:28 From what I understand it's a bitbake issue Mar 18 14:00:35 not danny Mar 18 14:00:44 used to be dylan Mar 18 14:00:47 now its dora Mar 18 14:01:07 pompomJuice: well, s/danny/dora/ then Mar 18 14:01:20 the major change is that on setup-scripts inside layers bitbake changed to ref 1.20 Mar 18 14:01:26 thats the biggest change I could see Mar 18 14:01:42 and now I have bitbake malfunctioning on my recipies but I am not sure what this error is Mar 18 14:02:27 if this is angstrom's setup scripts it's probably something for koen to look into Mar 18 14:02:50 this was the old layer -> bitbake,git://github.com/openembedded/bitbake.git,master,c47088a86fd8ad06c1810d04d9537c4cd01e8bef Mar 18 14:03:05 this is the new layer -> bitbake,git://github.com/openembedded/bitbake.git,1.20,HEAD Mar 18 14:03:17 so it went from master to 1.20 Mar 18 14:04:08 looks like python is back on the menu the Mar 18 14:04:15 then* Mar 18 14:04:46 I ahve checked the recipies themselves Mar 18 14:04:51 nothing major Mar 18 14:05:00 they dont even inherit autotools Mar 18 14:05:24 so why its complaining about autotools_do_configure no idea Mar 18 14:06:02 and I have only been baking for a year Mar 18 14:06:05 I am noob Mar 18 14:06:30 cant handle parse errors and tokens and things Mar 18 14:06:54 try deleting cache/bb_codeparser.dat Mar 18 14:07:01 that's the cureall for parsing problems Mar 18 14:07:12 on it Mar 18 14:07:18 I'm not sure what that file does, but deleting it makes everything better Mar 18 14:07:21 koen: is that an unreported bug? Mar 18 14:07:30 memory usage goes down from 10G to 1G Mar 18 14:07:53 same issue Mar 18 14:07:55 bluelightning: dunno, when I asked around multiple people said "we delete it periodically as well" Mar 18 14:08:04 koen: well, I don't... Mar 18 14:08:31 point being, if issues like this never get reported, they will never be fixed Mar 18 14:08:36 can I trash the entire cache? Mar 18 14:09:00 nope Mar 18 14:09:08 that also give same problem Mar 18 14:09:27 NOTE: Error during finalise of /home/griftw/w/danny/setup-scripts/sources/meta-openembedded/meta-efl/recipes-efl/e17/exalt-client_svn.bb Mar 18 14:09:40 and many other in that folder Mar 18 14:09:48 they have not been changed recently Mar 18 14:10:03 who moved bitbake to 1.20? Mar 18 14:10:24 you need 1.20 for oe-core 1.5 Mar 18 14:10:31 makes sense Mar 18 14:10:41 but those recipies are in meta-oe Mar 18 14:10:47 I ahve not touched them Mar 18 14:10:52 they are yocto1.5 Mar 18 14:11:03 not messing with the layers file Mar 18 14:11:11 I have commented some layers out tough Mar 18 14:11:14 though* Mar 18 14:11:31 that wont be it right? Mar 18 14:13:29 also removed some in my bblayers Mar 18 14:14:55 stuff like minno Mar 18 14:15:00 and dominion Mar 18 14:15:07 since I don't know what that is Mar 18 14:18:24 wait Mar 18 14:18:56 setup scripts you should me on master/HEAD? Mar 18 14:19:11 to get the latest working angstrom? Mar 18 14:19:59 because there is a angstrom-v2013.12-yocto1.5 aswell Mar 18 14:20:09 and master is 22 behind Mar 18 14:32:01 noone here knows about a bitbake reset command Mar 18 14:32:03 something like Mar 18 14:32:09 btibake -c cleansstate pseudo Mar 18 14:32:35 that makes it all start over Mar 18 14:32:51 cleansstate on the image is pointless Mar 18 14:32:56 I want a distclean move Mar 18 14:36:41 pompomJuice: completely throwing everything out (if that's what you want) is just a matter of deleting TMPDIR Mar 18 14:36:49 or renaming it Mar 18 14:36:53 thats what I will do then Mar 18 14:36:56 perfect Mar 18 14:37:03 that is what I wanted to know Mar 18 14:37:04 I suspected it Mar 18 14:37:08 but I needed confirmation Mar 18 14:38:55 nope Mar 18 14:38:58 zero effect Mar 18 14:39:23 ok so that latest angstrom version must be experiencing difficulty Mar 18 14:44:27 koen: are you not seeing this failure at all? ^ Mar 18 14:44:33 nope Mar 18 14:57:40 basically all i did was oebb update Mar 18 14:57:54 I just deleted almost everything Mar 18 14:58:07 but it fails right at the beginning when it is parsing the recipies Mar 18 14:58:14 so it has to be a bitbake issue Mar 18 14:58:23 il look at it tomorrow Mar 18 14:58:55 pompomJuice: which host distro are you using out of interest? Mar 18 15:00:03 Linux ubantu 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Mar 18 15:00:33 I did an apt-get upgrade also Mar 18 15:00:39 no effect Mar 18 15:00:51 I am starting over now with just the setup-scripts Mar 18 15:00:55 lets see what happens Mar 18 15:01:10 just cloned it into another directory Mar 18 15:01:34 so you cant get fresher than this Mar 18 15:01:36 and Mar 18 15:01:59 I started doing this 2 montsh ago when I moved our stuff from denzil to dylan Mar 18 15:02:07 so I know kind of what I am doing Mar 18 15:03:03 just as a side note Mar 18 15:03:12 how could I contribute to the recipies Mar 18 15:03:29 say for example I bumped sqlite3 version Mar 18 15:03:40 could I submit the patch somehere? Mar 18 15:04:05 never really done opensource contribution before Mar 18 15:06:08 pompomJuice: we definitely appreciate patches like that (although we typically upgrade core recipes like sqlite ourselves on a regular basis) Mar 18 15:06:16 pompomJuice: which Ubuntu release is that though? Mar 18 15:06:43 pompomJuice: this may be of interest: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Mar 18 15:10:14 oh Mar 18 15:10:40 I think it was originally Ubuntu 12.03 LTS Mar 18 15:10:48 Desktop Mar 18 15:12:17 I mean 12.04.3 Mar 18 15:12:26 ok, so pretty standard then Mar 18 15:12:48 yea Mar 18 15:12:50 nothing fancy Mar 18 15:13:01 I am going home now Mar 18 15:13:06 boss is jumping up and down Mar 18 15:13:18 he wants his image I cannot give it to him Mar 18 15:13:24 thanks for the help though Mar 18 15:13:31 really learnt alot already Mar 18 15:13:47 good to hear from experience ppl then you can use it as facts Mar 18 15:13:55 ive bee guessing mostly Mar 18 16:36:37 so... I just ran bitbake core-image-minimal and it completed successfully Mar 18 16:36:41 now, where exactly did it put the image? Mar 18 16:37:24 tmp/deploy/images/, see also the documentation at yoctoproject.org Mar 18 16:46:21 huh, I would never have guessed to look in 'tmp' for the final product Mar 18 16:46:52 yeah, not ideal, tmp implies intermediate artifacts, not output Mar 18 16:47:05 but we're stuck with it for now Mar 18 16:47:16 deploy has the output. binary packages, images, etc Mar 18 16:48:47 kergoth: wouldn't be that hard to change on a per distro basis I guess Mar 18 16:48:51 hi. i need to use COMBINED_FEATURES for my own 'features'. is that ok to do so? I think I need to append ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "xxx", d)} in my distro .conf. should i expect any issue? Mar 18 16:49:02 The tmp part, not TMPDIR which would be much harder Mar 18 16:49:32 I have features in my distro that require 'machine' support. so my recipe need to test for the feature to be both in DISTRO and MACHINE features. Mar 18 16:50:07 yeah, moving outside of TMPDIR would be very difficult due to sstate archives, unless we could change it to operate entirely relative to ${TOPDIR} instead, or something Mar 18 16:52:05 w00t. kernel ran just fine with qemu. It kernel panicked immediately due to no root FS, but that's probably because I didn't make one Mar 18 16:54:13 bitbake core-image-minimal would have given you a rootfs as well as a kernel, though :) Mar 18 17:08:21 kergoth: yes, and I saw the rootfs, but first I wanted to make sure I could boot the damn kernel :P Mar 18 17:08:41 hehe, fair enough Mar 18 17:21:22 Should depexp.py use bb.warn/note instead of prints for the error messages ? I'm looking into why bitbake -g -u depex comaplins with "Unable to cleanly stop: No such command" on exit Mar 18 20:15:33 https://github.com/openembedded/openembedded/blob/master/conf/distro/openwrt-sdk.conf . . . "You should install and have in path an SDK from the www.openwrt.org." Mar 18 20:15:56 I built an OpenWrt SDK, but what does "have in path" mean? Mar 18 20:18:51 if it means PATH, I don't see what good that would do, since it's all MIPS binaries, it looks like Mar 18 20:34:43 Hodapp, I'd guess you have to source the included env-script to setup PATH correctly Mar 18 20:35:04 Hodapp, if the host binaries are not what you expected, maybe you build the SDK for the wrong host ? Mar 18 20:36:09 kroon: I haven't tried to build anything yet; I am just wondering what those instructions mean Mar 18 20:36:17 Hodapp: thats OE-classic and arcane Mar 18 20:36:29 you might not get much mieage on it Mar 18 20:36:44 khem: ohhh... I Was just looking around for any sort of information on using OE to build OpenWrt packages Mar 18 20:36:52 as I'd read it could be done Mar 18 20:36:58 yes it could be Mar 18 20:37:10 your best bet is to use 2011.03 release Mar 18 20:37:37 ahh, I just checked out oe-core a week or two ago and was building from that Mar 18 20:37:39 why 2011.03? Mar 18 20:37:47 and yet there might be fewer folks who would have similar setups Mar 18 20:38:02 since that was last release out of OE-classic Mar 18 20:38:15 and is much stable compared to master/oe-classic Mar 18 20:38:22 now a days we use layered model Mar 18 20:38:40 where we have oe-core as a small core subset of metadata Mar 18 20:38:50 and everyting else is in layers around it Mar 18 20:39:15 I have been meaning to create a openwrt distro layer Mar 18 20:39:45 but then I see that angstrom is good enough for openwrt platforms so why bother Mar 18 20:40:50 angstrom is good enough for openwrt platforms? what do you mean? Mar 18 20:43:54 Hodapp: yes it could generate ipks Mar 18 20:44:03 that one could use on openwrt Mar 18 20:45:23 good to know Mar 18 20:45:44 I'm looking at doing this, but I am also looking at perhaps just using OE to make the system in the first place and not bothering with OpenWrt Mar 18 20:51:00 that works too Mar 18 20:51:11 I have taken angstrom generated images and booted them Mar 18 20:51:24 but it was few years ago Mar 18 20:52:03 I guess I'm just trying to see whether OpenWrt for this application is even getting me anything Mar 18 20:52:27 it looks like I could get a much more minimal system, and pretty much any package I need, with OE Mar 18 20:56:00 would you happen to have any good references on how to use Angstrom to generate OpenWrt packages? Mar 18 20:56:50 well choose close enough machine Mar 18 20:56:57 and bitbake the package you need Mar 18 20:57:17 bluelightning: howdy? Mar 18 20:57:42 khem: hey Mar 18 20:57:44 bluelightning: you pinged me yesterday Mar 18 20:57:57 is the ping still valid :) Mar 18 20:57:58 right, yes... nm, figured it out Mar 18 20:58:03 OK Mar 18 20:58:25 basically eglibc-initial failing due to lack of binutils-cross in dylan; but there was a master patch that fixed it Mar 18 20:58:35 I see Mar 18 20:58:46 yes its sstate related IIRC Mar 18 20:59:06 build from scratch always works right ? Mar 18 20:59:42 yep, that's the one Mar 18 21:00:02 I did wonder if eglibc-initial should explicitly have a DEPENDS on binutils-cross since that also fixes it Mar 18 21:01:06 bluelightning: yes explicit depend is needed Mar 18 21:01:16 I added that to kernel as well Mar 18 21:01:31 send a patch for eglibc-initial as well Mar 18 21:01:54 may be gcc-initial should have the dep too Mar 18 21:02:06 and that will fix all bootstrap recipes Mar 18 21:08:20 I am trying to find where to start for some basic high-level stuff and the documentation I have found mostly just confuses me... Mar 18 21:08:37 if all I'm aiming for is something like "core-image-minimal, but with GCC added to it", where do I start? Mar 18 21:20:59 well, I suppose that's a moot point when I can't build gcc... "undefined reference to pass_branch_target_load_optimize1" Mar 18 22:27:25 Is it possible to append/remove PACKAGECONFIG for a package in distro.conf ? Mar 18 22:28:01 I tried PACKAGECONFIG_append[qtbase] in my distro.conf, but it doesn't seem to bite Mar 18 22:28:25 kroon: absolutely... PACKAGECONFIG_append_pn-qtbase = " something" Mar 18 22:28:42 bluelightning, aha, thanks! Mar 18 22:45:29 and it seems to work EXTRA_OECONF too Mar 18 22:55:26 Hodapp: try oe-core directly Mar 18 23:00:34 khem: what do you mean? Mar 18 23:15:45 Hodapp: I mean use latest Mar 18 23:16:11 http://git.openembedded.org/openembedded-core/ Mar 18 23:16:22 thats the next generation OE Mar 18 23:16:28 core layer Mar 18 23:16:34 then you can add layers to it Mar 18 23:16:39 as you need Mar 18 23:16:55 look at http://layers.openembedded.org/layerindex/branch/master/layers/ Mar 18 23:17:02 for extra stuff you might need Mar 18 23:20:36 khem: that's what I'm using already Mar 18 23:24:24 what I'm trying to figure out is "what do I even look up to figure out how to accomplish this?" Mar 18 23:26:14 I see a lot of documentation, and I have just no idea where to start Mar 18 23:27:52 Hodapp, you want to use OE to build just the application for an existing already built image ? Mar 18 23:28:23 kroon: I don't care if I have to rebuild the image Mar 18 23:31:56 Hodapp, for a minimal system I'd just go with plain OE and a custom image/distro Mar 18 23:32:18 and not bother with angstroem/openwrt/whatever Mar 18 23:32:40 do you need package feeds? Mar 18 23:33:49 kroon: this is what I'm trying to start out with, but I was interested in how one goes about getting other packages into an image. Mar 18 23:34:16 kroon: this is without Angstrom or OpenWrt; all I've done so far is go through 'Getting Started' in the wiki and made core-image-minimal Mar 18 23:34:45 Hodapp: EXTRA_IMAGE_INSTALL in local.conf (there's commented out info about that in local.cnf.sample or local.conf.sample.extended), or IMAGE_INSTALL in an image recipe (you can copy one to create your own image) Mar 18 23:34:57 erm, CORE_IMAGE_EXTRA_INSTALL, that is Mar 18 23:35:52 so, I would perhaps find the core-image-minimal recipe, copy it, and customize it? Mar 18 23:36:51 if all you need to do is change what packages go into your filesystem, yep, thats what image recipes are for. best to create your own layer and add it to bblayers.conf, and put the new recipe there, to avoid maintenance headaches Mar 18 23:37:31 is there documentation that covers 'layers' and 'recipes' at a high level? Mar 18 23:40:18 perhaps I'll start at http://www.openembedded.org/wiki/Layers_FAQ and hope it's up to date Mar 19 00:21:49 Hodapp: want some examples to look at? Mar 19 00:23:35 mr_science: if you have some on hand, sure, I'll look at work tomorrow when I'm on the actual build machine Mar 19 00:23:53 all my stuff is on github Mar 19 00:24:18 what kergoth was talking about, custom layer with custom image recipes, etc Mar 19 00:25:20 https://github.com/sarnold => meta-raspberrypi and meta-alt-desktop-extras Mar 19 00:25:37 the interesting images are in the second one **** ENDING LOGGING AT Wed Mar 19 02:59:58 2014