**** BEGIN LOGGING AT Tue Aug 21 02:59:58 2012 Aug 21 07:49:54 morning all Aug 21 08:30:36 hi, all! I have an issue with python.pc while i'm trying to bitbake some package (monit for example). It says that there is no such file... How can I fix it? Aug 21 08:39:46 It tells me that the symlink to the python-2.6.pc is broken... Aug 21 10:42:29 hi all Aug 21 10:48:05 hi pb_ Aug 21 14:57:28 hi all Aug 21 14:59:29 I have a problem with gcc-cross-intermediate in the meta-oe overlay.. it seems to be missing a gcc-cross-intermediate.inc file. What am I doing wrong? Aug 21 15:00:13 I also see no such file in the git history.. Where should this file reside? Or is it wrongly 'require'd in the bb file? Aug 21 15:03:09 Hmm, I konw I used to be able to do builds with 1gb of ram, but it doesn't appear to function anymore. hmm Aug 21 15:03:15 accu: it was removed in latest oe-core Aug 21 15:03:25 accu: and nobody updated toolchain-layer to cope with that Aug 21 15:03:41 aha. thanks, but how di I proceed then? Aug 21 15:03:54 accu: http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/028345.html Aug 21 15:04:10 accu: add it to toolchain-layer (from older oe-core) and send patch Aug 21 15:04:42 JaMa: thanks, will do that Aug 21 15:04:43 or wait for someone else to fix that.. I've dropped toolchain-layer from my setups as I wasn't using gcc-4.6 anyway Aug 21 15:09:18 I'm using the raspberry-pi overlay from David Willis. Maybe it builds without toolchain-layer, so I will try that first. 'toolchain-layer' sounds pretty mandatory though, so with my limited OE experience I didn't think of excluding it :) Aug 21 15:14:59 JaMa: seems to build fine now, without the toolchain-layer. thanks Aug 21 18:47:17 Does anyone know if there exists a recipe for unixODBC in oe ? Aug 21 18:48:37 has anyone got an example of a working image recipe that inherits from boot-directdisk? Aug 21 20:03:18 hi Aug 21 20:05:05 what is the best way to start a new project/distribution from oe-core ? to make a fork from oe-core and start adding more stuff or embedded oe-core in another git using a submodule or something similar ? Aug 21 20:06:35 wakko: add a new layer Aug 21 20:06:51 directly inside oe-core/ ? Aug 21 20:07:00 like oe-core/meta-mymeta Aug 21 20:07:37 euh no.. in addition to oe-core Aug 21 20:07:43 so next to it Aug 21 20:07:48 or well.. Aug 21 20:08:06 depends on how you look at it.. it really doesn't matter where it is, as long as you configure the path to it in bblayers.conf i think Aug 21 20:08:24 normally, you have your oe-core dir.. under that is meta, conf, etc... from oe-core Aug 21 20:08:33 and then in that some root, i put the layers.. Aug 21 20:08:55 that's what i thought, but i find it kinda difficult to put my layer next to oe, without breaking all the scripts and classes Aug 21 20:09:02 like runqemu for example Aug 21 20:09:22 so for eg, this is what i have in one of my projects right now: Aug 21 20:09:23 bitbake build LICENSE meta meta-angstrom meta-hob meta-openembedded meta-skeleton meta-tomtom oe-init-build-env README scripts setup-scripts Aug 21 20:09:37 i really have to look inside runqemu script and find wath ENV vars are used and stuff Aug 21 20:09:41 so meta-angstrom, meta-hob, meta-openembedded, meta-tomtom are all extra layers Aug 21 20:10:08 oh yes, it's a pretty steep learning curve :) Aug 21 20:10:13 :) Aug 21 20:10:18 i see Aug 21 20:10:26 i tend to only use .bbappend files though, unless i really add something that's not there at all Aug 21 20:10:56 plus some config files that usually include what's already there for common arm stuff and all Aug 21 20:11:01 ok Aug 21 20:11:06 what is it exactly you want to do in your new layer? Aug 21 20:11:15 just some tweaks, or a whole new machine or distro? Aug 21 20:11:32 you are using meta-openembedded , it does not look like you are using oe-core Aug 21 20:11:43 whole new distro Aug 21 20:13:40 http://cgit.openembedded.org/openembedded-core/ Aug 21 20:13:57 wakko, meta-oe extends oe-core Aug 21 20:14:04 it is not a whole new thing Aug 21 20:14:12 ha Aug 21 20:16:07 gmc, could i have a look at your oe-init-build-env ? Aug 21 20:16:50 wakko: i haven't changed it Aug 21 20:17:13 so from where did you copy it ? Aug 21 20:17:25 hmm didn't it come with oe-core then? Aug 21 20:17:27 i feel kinda lame Aug 21 20:17:29 :p Aug 21 20:17:53 i know that feeling :) Aug 21 20:18:07 i know the one in oe-core/oe-init-build-env Aug 21 20:18:22 it's kinda complex how all the recipes and bbappends and classes and confs etc interact, still baffles me regularly :) Aug 21 20:18:55 yep, it's the stock oe-init-build-env from the oe-core git repos Aug 21 20:19:01 yes it's not like like there is one way to go Aug 21 20:19:23 so you just made a copy ? Aug 21 20:19:37 well.. i first cloned oe-core Aug 21 20:19:46 haaa Aug 21 20:20:02 then in the root dir i added oe-tomtom et al as git submodules (basically the same as cloning oe-core, then cloning the other layers inside the oe-core dir) Aug 21 20:20:36 it's the answer of my first question Aug 21 20:21:18 you are doing some kind of fork (aka clone and edit) Aug 21 20:21:45 that's right ? Aug 21 20:21:53 well... no.. i never touch oe-core itself Aug 21 20:21:59 well ok Aug 21 20:22:16 if i need to change something in oe-core, i use a .bbappend or whatever in my own layer Aug 21 20:22:18 in a git point of you, it could look like you are... but i get it know, thx Aug 21 20:22:19 :p Aug 21 20:22:25 that's the only layer i touch Aug 21 20:22:30 how do I add a specific build time dependency for a native perl module (Proc::ProcessTable) Aug 21 20:22:44 i could, in theory, edit stuff in oe-core files, but i tend to avoid that because i want to be able to cleanly git pull Aug 21 20:23:22 awozniak: does Proc::ProcessTable have a recipe? Aug 21 20:23:42 I don't know. I sort of assumed it did, but that could be incorrect. Aug 21 20:24:11 tbh i never did anything with perl in openembedded so far :) Aug 21 20:24:34 some other thing I'm working with needs it to build, apparantly. Aug 21 20:24:40 its strange, boot-directdisk.bbclass exists but it doesn't seem like anyone actually uses it, at least publically Aug 21 20:24:45 wakko: if github would be up, i could show you the override things i did Aug 21 20:25:11 awozniak: generally, you add dependencies by adding stuff to DEPENDS in the recipe Aug 21 20:25:45 awozniak: but really, i have no clue how openembedded deals with cpan modules Aug 21 20:25:50 gmc: nice Aug 21 20:25:58 I was hoping there was an example of that somewhere gmc Aug 21 20:26:46 awozniak: apparently, there's a cpan.bbclass in oe-core Aug 21 20:27:41 awozniak: which is being used by recipes-extended/perl/libtimedate-perl_1.20.bb for example Aug 21 20:27:58 gmc: kthx, I think that's got me headed in the right direction. Aug 21 20:28:23 awozniak: welcome :) Aug 21 20:28:31 wakko: https://github.com/sonologic/meta-tomtom Aug 21 20:28:36 it's still very much work in progress though Aug 21 20:29:16 and so far only has a machine conf and a kernel recipe Aug 21 20:29:40 ok Aug 21 20:29:48 i have more complex layers, but sadly i can't show those or i would have to kill you :) Aug 21 20:30:50 where are the meta-oe meta-angstrom ? Aug 21 20:30:57 i dont see them in your repo Aug 21 20:31:07 oh they are not mine Aug 21 20:31:14 i know Aug 21 20:31:28 http://www.openembedded.org/wiki/LayerIndex Aug 21 20:31:37 i know Aug 21 20:31:40 :/ Aug 21 20:31:56 i just checked them out in oe-core... the github link is only meta-tomtom.. Aug 21 20:32:21 ok Aug 21 20:32:51 how do you work with both at the same time if they are not in the same repo ? Aug 21 20:33:14 you must have other stuff outside of this repo to make the whole machine up and running Aug 21 20:33:35 git magic ? Aug 21 20:45:21 wakko: well... not really Aug 21 20:45:38 in the simplest form it is git clone oe-core, then cd oe-core, and git clone whateverlayersiwant Aug 21 20:45:48 ok Aug 21 20:45:53 although it's cleaner imho to cd oe-core and then add git submodules for the layers Aug 21 20:46:15 using oe-core as the upstream ? Aug 21 20:49:17 yep Aug 21 20:49:26 (or whatever the upstream is for the layers of course) Aug 21 20:49:48 i've been thinking about writing all i learned on the wiki sometime.. as i find the docco.. lacking.. sometimes.. :) Aug 21 20:50:18 khem: what are you thoughts on updating denzil to latest eglibc 2.15 from svn? Aug 21 20:57:03 mbroadst: meta/classes/image-vmdk.bbclass uses it Aug 21 20:57:25 it used to be used by the old directdisk images but those got canned Aug 21 20:57:38 sub modules leads to madness :) Aug 21 20:58:19 anyone see this on master when rebasing: https://gist.github.com/3419360 Aug 21 20:58:36 combo-layer or repo would be the recommended solutions for multiple-repos-in-one-repo Aug 21 20:59:43 msm: sounds like this bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=2774 Aug 21 21:00:08 bluelightning: seems likely Aug 21 21:04:32 Crofton: madness for the win! Aug 21 21:07:35 gmc: have a recipe for libproc-processtable-perl now. I'm not sure what exactly to put in the DEPENDS line in my other recipe though; I want to make sure perl-native has that cpan module available to it Aug 21 21:09:24 awozniak: there's more knowledgable ppl on this list, but i'd say something like 'libproc-processtable-perl-native' or whatever the PN in the recipe is Aug 21 21:09:40 s/list/channel/ Aug 21 21:09:59 or maybe you can drop the -native since it is a build dep Aug 21 21:10:03 experiment :) Aug 21 21:21:36 bluelightning: I noticed that, but nothing uses that either :| Aug 21 21:43:03 msm: I consider gcc/glibc/binutils as core components which should not get upgraded on release branches Aug 21 21:43:23 unless we have very serious issues which I believe we dont Aug 21 21:43:29 khem: isn't the release branch just stable fixes? Aug 21 21:43:58 oh I thought you meant 2.13 -> 2.15 Aug 21 21:44:07 nah Aug 21 21:44:29 yes getting bug fixes from branch should be fine Aug 21 21:44:32 * a4d55aa eglibc-2.15: Update to latest on 2.15 branch Aug 21 21:44:38 as long as they are well tested in our combos Aug 21 21:44:38 for example Aug 21 21:44:45 sure Aug 21 21:45:07 keep in mind that they need to be tested with toolchain in denzil Aug 21 21:45:32 khem: ya, i'll see how things go Aug 21 21:45:42 khem: im trying to fix eglibc 2.15 for our parts Aug 21 21:45:51 it seems broken ;) in master and denzil Aug 21 21:46:15 i think it might be this patch: meta/recipes-core/eglibc/eglibc-2.16/ppc_slow_ieee754_sqrt.patch Aug 21 21:46:45 broken or buggy Aug 21 21:47:18 compile issue Aug 21 21:47:53 different issues on master and denzil to boot Aug 21 21:49:08 khem: actually, did you test eglibc 2.15 with all your other recent changes? Aug 21 21:49:36 i got this on 2.15: | /local/home/mattsm/git/poky/build-master/tmp/sysroots/x86_64-linux/usr/libexec/ppce5500-poky-linux.gcc-cross-initial/gcc/powerpc-poky-linux/4.7.2/ld: cannot find -lgcc_eh Aug 21 21:49:37 only 2.16 Aug 21 21:49:45 since thats what is default on master Aug 21 21:49:54 2.15 wont work Aug 21 21:50:12 infact I should post a patch to delete 2.15 recipes from OE-Core/master Aug 21 21:51:07 khem: ok… so just one eglibc for the next release then? Aug 21 21:51:10 msm: 2.16 should work fine I guess Aug 21 21:51:15 yes Aug 21 21:51:25 khem: 2.16 is working fine, because I think you fixed it up ;) Aug 21 21:51:28 it boots fine on p5020 Aug 21 21:51:34 yes I did :) Aug 21 21:51:45 i'd like 2.15 to work on denzil… for various odd reasons Aug 21 21:51:52 but anyways, that's more my problem ;) Aug 21 21:51:54 whoever sends me their boards I fix it up for them for free :) Aug 21 21:52:24 ok I fixed 2.15 as well but on master Aug 21 21:52:37 so you can backport 2.15 changes from master into denzil Aug 21 21:52:48 and it will work Aug 21 21:53:10 then 2.16 came out and I relegated 2.15 Aug 21 21:53:18 khem: was it the stable branch update that had the fixes? Aug 21 21:53:33 fixes are in master Aug 21 21:53:37 IIRC Aug 21 21:54:34 i only see two commits for 2.15: Aug 21 21:54:35 * a4d55aa eglibc-2.15: Update to latest on 2.15 branch Aug 21 21:54:35 * 9ecb454 eglibc-2.15: Support mips64 Aug 21 21:54:41 in master but not in denzil Aug 21 21:54:49 hmmm Aug 21 21:55:17 it very well could be that I never posted the patches to master and just forwarded ported them to 2.16 Aug 21 21:55:30 since 2.16 is where I really started to use 5020 Aug 22 00:37:23 mbroadst: actually putting vmdk in IMAGE_FSTYPES will activate image-vmdk.bbclass, so it is used **** ENDING LOGGING AT Wed Aug 22 03:00:00 2012