**** BEGIN LOGGING AT Thu Nov 10 02:59:58 2011 Nov 10 03:41:17 _JOEL_, did you ever get an answer to your question about Sheevaplug support? Nov 10 03:41:25 <_JOEL_> no Nov 10 03:41:49 well, I can tell you that we don't have an "official" BSP for it in Yocto, but you should be able to port one from OpenEmbedded Nov 10 03:42:53 have you worked with OE before? Nov 10 03:43:44 <_JOEL_> somewhat, I had some build issues with it that didn't occur with yocto and a few python issues from my previous distro I was using causing bitbake to fail Nov 10 03:44:11 <_JOEL_> I've build a few qemu in yocto as test environments and I like what I've scene so far Nov 10 03:44:33 http://git.openembedded.org/openembedded/tree/conf/machine/sheevaplug.conf Nov 10 03:45:11 I've never ported a machine from OE, but it shouldn't be too difficult Nov 10 03:45:23 <_JOEL_> ooo nice, I wasn't sure if any of the configs would work with your project Nov 10 03:45:38 you will likely find the Yocto BSP developer guide helpful: http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Nov 10 03:45:56 <_JOEL_> and eventually I gave up screaming at a broken python stack in previous distro, running new distro now and trying yocto which was reccomended by a friend Nov 10 03:46:18 <_JOEL_> zenlinux:awesome, ty, info linkslaps always appreciated Nov 10 03:46:52 sure thing. That should get you started with some background info, and feel free to ask questions on the OE and/or Yocto mailing lists Nov 10 03:47:25 This IRC channel gets pretty quiet during US evenings Nov 10 03:48:00 <_JOEL_> yea I figured as much, this is a side project for me as a hobby I want to turn into something else Nov 10 03:48:09 <_JOEL_> so it's not my "work" Nov 10 03:48:54 also, out of curiosity, which Linux distro had the python stack issues? Nov 10 03:48:55 <_JOEL_> thanks for the info, most appreciated, I am setting up eclipse to try out the yocto IDE plugin Nov 10 03:51:23 <_JOEL_> zenlinux: ubuntu 11.04 and 10.04 but only the 64 bit versions Nov 10 03:51:48 <_JOEL_> they didn't like even the git checkouts of bitbake for some reason Nov 10 03:52:02 <_JOEL_> I had a lot of issues with that, the x86 versions didn't have that issue Nov 10 03:52:05 odd. We do test with recent Ubuntu releases. Nov 10 03:52:11 <_JOEL_> it might have been fixed in an update Nov 10 03:52:16 if you're ever able to reproduce the problem, please file it in a bug report Nov 10 03:52:31 <_JOEL_> but I gave up and I needed to update my OS anyway Nov 10 03:52:52 <_JOEL_> ubuntu 11.10 is running awesome, no issues so far Nov 10 03:53:21 cool. I'm going afk for the rest of the evening - good luck with your Sheevaplug adventures. :) Nov 10 03:53:54 <_JOEL_> thanks, I'm looking forward to target building and lots of compiling voodoo Nov 10 03:57:05 <_JOEL_> thanks again for the help **** BEGIN LOGGING AT Thu Nov 10 05:56:30 2011 Nov 10 07:59:00 sgw: ping Nov 10 08:12:50 good morning Nov 10 10:49:31 good morning. Is there a way to list all packages that are going to be installed for specific target? thx Nov 10 10:53:10 jkprg: that's difficult because it's not always possible to determine before building Nov 10 10:53:45 for example, kernel modules - the packages for these are automatically generated based on the modules that get built Nov 10 10:54:12 I see. Nov 10 10:54:13 there are other examples wherever a piece of software has plugins or add-on modules Nov 10 10:54:41 the hob UI shows you a guess Nov 10 10:54:58 thx. I'll try Nov 10 10:54:59 but I don't think it takes the above into account Nov 10 13:46:08 bluelightning, ping Nov 10 14:03:39 hi Crofton|work Nov 10 14:28:17 can you help me to find the code that is responsible for adding -dbg packages? Nov 10 14:28:44 through IMAGE_FEATURE according to poky reference man Nov 10 14:31:08 bluelightning, looks my cmake + qt problems are caused by cmake :) Nov 10 14:31:32 the cmake macro runs qmake in query mode to find paths Nov 10 14:31:43 and the native qmake finds paths to native staging Nov 10 14:31:54 trying a build now with a sed to remove these from makefiles Nov 10 14:32:11 Crofton|work: excellent, sounds good :) Nov 10 14:33:03 jkprg: do you mean including them in the image or creating them in the first place? Nov 10 14:34:00 bluelightning: including them in the image Nov 10 14:36:35 jkprg: it's in classes/image.bbclass - "dbg-pkgs" in IMAGE_FEATURES Nov 10 14:37:41 bluelightning: I see. I've probably found it. they are added to NORMAL_FEATURE_INSTALL_OPTIONAL Nov 10 14:43:39 that's an internal variable though Nov 10 14:46:54 I'm trying to understand how it's implemented :-) Nov 10 14:52:00 ok, fair enough Nov 10 14:56:15 btw I want to extend core-image-minimal by x11 I can put final packages names to IMAGE_INSTALL or I can use complex task that would do it automatically, right? Nov 10 14:58:58 jkprg: yes you can do that Nov 10 15:00:40 bluelightning: and is it recommended way to do it - create a new target and specify IMAGE_INSTALL="core-image-minimal task-core-x11"? Nov 10 15:02:38 maybe it's better to do in in my "private" layer.. Nov 10 15:02:44 jkprg: actually I would suggest creating a new image and inheriting from core-image Nov 10 15:03:00 that gives you more control of things via IMAGE_FEATURES Nov 10 15:03:15 ic thx Nov 10 15:03:56 look at meta/recipes-core/images/core-image-base.bb for an example Nov 10 15:05:35 :-) great Nov 10 16:20:15 * zenlinux likes to start his days marking bugs as fixed :) Nov 10 16:23:34 :) Nov 10 19:22:24 hey guys, new to oe and yocto and I have some problems was wondering if I could get some help. --> SH4 Nov 10 19:22:48 We have three embedded dev environments I'm moving over to yocto, unfortunately, the first to go is going to be SH4 based Nov 10 19:23:40 having an error trying to compile gcc-cross-intermediate Nov 10 19:24:19 build-edison-sh4/tmp/sysroots/i686-linux/usr/bin/sh4-poky-linux/sh4-poky-linux-ld: cannot find crti.o: No such file or directory Nov 10 19:24:30 build-edison-sh4/tmp/sysroots/i686-linux/usr/bin/sh4-poky-linux/sh4-poky-linux-ld: cannot find -lc Nov 10 19:24:39 build-edison-sh4/tmp/sysroots/i686-linux/usr/bin/sh4-poky-linux/sh4-poky-linux-ld: cannot find crtn.o: No such file or directory Nov 10 19:24:57 And I've searched and searched and cannot find any fixes for this Nov 10 19:28:16 mebrown: what version of yocto are you using? Nov 10 19:28:24 edison 1.1 Nov 10 19:29:11 I've tried porting the working gcc recipes from openembedded, but they are hopelessly incompatible for my level of knowledge atm Nov 10 19:29:36 and when I compile yocto for arm, for example, I dont hit this problem at all Nov 10 19:30:32 mebrown: i dont think sh4 is supported by default is it? Nov 10 19:30:39 nope, not in the list Nov 10 19:30:44 but base oe supports it Nov 10 19:30:46 the lack of testing in this regards is the issue i suspect Nov 10 19:30:56 and I cannot find anything where sh4 has been 'disabled' Nov 10 19:31:06 all the sh4 files are still there Nov 10 19:31:14 i've never seen these issues on the cross compiler Nov 10 19:31:47 I've been working this for about a week now without success. Nov 10 19:32:15 oe-core has the same issue as yocto, but base openembedded does not Nov 10 19:32:21 have you sent an email to the mailing list? Nov 10 19:32:28 not yet Nov 10 19:32:39 was going to be my next step Nov 10 19:33:17 would this be a poky or yocto topic? Nov 10 19:33:42 most people don't really use the poky list too much Nov 10 19:33:47 just like the poky IRC channel Nov 10 19:35:04 mebrown: you might try makeing a meta-toolchain too Nov 10 19:35:14 and see if it generates a working cross compiler Nov 10 19:35:18 bitbake meta-toolchain? Nov 10 19:35:20 yea Nov 10 19:35:40 building... Nov 10 19:36:57 commit a80541d6960b663358e10c8bb41a919a033c2224 Nov 10 19:37:07 you might also look at that patch for the toolchain Nov 10 19:37:19 looking... Nov 10 19:37:25 but that fixes just the sdk (toolchain) target not the normal cross compiler Nov 10 19:37:51 is that in yocto git? Nov 10 19:37:54 I'm not seeing it Nov 10 19:38:34 meta-toolchain failed the same way Nov 10 19:38:45 try sha 53f7342 Nov 10 19:39:05 ok, I see it Nov 10 19:40:05 $ find tmp/ -name crt[in].o Nov 10 19:40:05 tmp/work/sh4-poky-linux/eglibc-initial-2.13-r15+svnr14157/sysroot-destdir/usr/lib/crtn.o Nov 10 19:40:05 tmp/work/sh4-poky-linux/eglibc-initial-2.13-r15+svnr14157/sysroot-destdir/usr/lib/crti.o Nov 10 19:40:05 tmp/sysroots/qemush4-tcbootstrap/usr/lib/crtn.o Nov 10 19:40:05 tmp/sysroots/qemush4-tcbootstrap/usr/lib/crti.o Nov 10 19:40:42 so it would seem the sysroot param is what I need to tweak Nov 10 19:41:08 mebrown: yes, I think it's a simple configure parameter issue Nov 10 19:41:17 trying it now Nov 10 19:45:11 still looks like it is failing, I'll jiggle that param and see if I can make something happen Nov 10 19:51:10 how can I put in debugging to tell what variables are set to? Nov 10 19:51:14 in a recipe? Nov 10 19:51:28 you can just run bitbake -e pkg Nov 10 19:51:35 is that what you mean? Nov 10 19:52:11 let me check (completely and totally new to yocto/oe, tons of experience with rpm/mock/fedora buildsys/opensuse buildsys) Nov 10 19:57:18 yes, that gives me what i was hunting for. Nov 10 20:06:04 funny... oe core gcc-crosssdk-intermediate succeeded (when bitbake meta-toolchain), but yocto one fails. Now I should have something to compare against. Nov 10 20:34:27 mebrown: i would send an email with your issues Nov 10 20:35:07 Will do in about 2 hrs Nov 10 20:41:41 dont want to get ahead of myself because it is still going, but I *may* have figured it out. Nov 10 20:41:48 gcc-cross4.inc in base openembedded: Nov 10 20:41:53 EXTRA_OECONF_append_sh4 = " --with-multilib-list= --enable-incomplete-targets " Nov 10 20:42:01 but is empty in yocto Nov 10 20:42:23 added and am doing a clean build. I *think* it got past the build that failed, but not sure yet Nov 10 20:42:45 and with that, I have to go to the meeting where we are discussing this... Nov 10 20:47:17 Do someone knows the Paul Menzel's nick? Nov 10 23:13:40 hi again. How could I get an info what packages were installed during build? Nov 10 23:32:21 RP__: are you around? Nov 10 23:32:39 RP__: IIRC you did the fixup_perms method ... right? Nov 10 23:34:05 RP__: I am getting a failure of operation denied Nov 10 23:35:05 RP__: http://paste.debian.net/144630/ Nov 10 23:35:24 RP__: do you have any clue about it? Nov 11 01:38:14 So I have a question. Nov 11 01:38:22 Is anyone here then? Nov 11 01:45:50 Probably not. But! Nov 11 01:46:09 Every so often people wander through and check their logs. So just ask, and leave yourself logged in, and the next day you might have an answer. Nov 11 01:46:19 Think of us as like cobbler elves, only we do build debugging. Nov 11 01:46:56 it's one of the most convenient aspects of irc. as long as you stay connected, async communication works quite well Nov 11 01:52:04 haha ok thanks. Nov 11 02:06:29 Andy44: good morning (it's morning in my side :-) Nov 11 02:09:08 good morning Nov 11 02:10:39 I'm new to Yocto (and OE as a matter of fact). I write software for a living (c# .net) and I really like what everyone is doing here. Lately I've been spending a lot of time on this, reading manuals, trying* to get builds to work etc... I'd like to boot my atom based laptop from a linux image Yocto made. I've been able to fly through the quick start guide without any problems which is great Nov 11 02:10:40 . However, the moment I change any variable outside of the basic build defiend in the quick start, the build fails. If I add one new item to my local.conf file it never builds for me. I'm not too worried about the specifics right now I'm more interested in knowing if anyone else feels this way. It's like if I change anything from default it dosen't build for whatever reason. Is this expected Nov 11 02:10:40 ? Do I really need to power through problem after problem every time I change something? Or has his not been everyone else's experience? Nov 11 02:13:07 Andy44: welcome to ycoto and poky! :-) Nov 11 02:13:34 haha Nov 11 02:13:48 Andy44: could you please detail the issue you're meeting with? Nov 11 02:14:22 Andy44: what the build log of the failure? Nov 11 02:15:21 well the exact problem I'm trying to resolve is it seems perl-native doesn't want to build. Nov 11 02:15:47 dcui: what branch are you uisng? poky.git's master branch? Nov 11 02:16:29 ...oh gosh. How do I know that? Nov 11 02:16:48 one sec let me find out... Nov 11 02:17:09 Andy44: How do you get the poky source code? by the git repository or the recent relased edison bz2 ball? Nov 11 02:17:53 I got it from the edison bz2 at the website Nov 11 02:19:54 Andy44: well, the recently edison release should be enough stable since we did many tests and we didn't find there were perl-native build failure. :-) Nov 11 02:20:07 Andy44: could you please supply the detailed log file? Nov 11 02:34:10 Andy44: I downloaded poky-edison-6.0.tar.bz2 just now and did " bitbake perl-native" just now. The build finished successfully. So there mighe be some host environment issue in your host we don't know yet? BTW, my host OS x86-64 Ubuntu 11.04. Nov 11 02:40:10 Yeah I'm wondering that too because some other stuff I did didn't make sense a few days ago. I'm using VMWare Workstation running Ubuntu 11.10 Nov 11 02:41:07 How do you recommend I get you the log file dcui? Nov 11 02:42:05 Andy44: usually I use "bitbake perl-native | tee per-native.log" :-) Nov 11 02:43:12 Andy44: if there is a config/compile/install error, I'll check tmp/work/x86_64-linux/perl-native-5.12.3-r5/temp/log.do_XXX. Nov 11 02:43:14 Yeah I mean I have the log file. Do you want be to just past the contents in here? Nov 11 02:43:27 Andy44: not here. Nov 11 02:43:34 I'm looking at it... Nov 11 02:43:42 Andy44: Could you please send mail to yocto mailing list? Nov 11 02:43:45 haha I didn't think so. can I pm you? Nov 11 02:44:27 Andy44: there are much more people in the mailing list who could comment. Nov 11 02:45:16 Andy44: please subscribe them in case you haven't :-) Please see http://www.yoctoproject.org/community/mailing-lists Nov 11 02:45:22 will do. Nov 11 02:46:22 Andy44: we also have a bugzilla http://bugzilla.yoctoproject.org/ you could file a bug so people can get more details to fix the issue. Nov 11 02:48:01 Yeah I would but I'm hesitant to do that because I'm worried it's actually something I'm doing wrong - not a bug. Nov 11 02:48:42 Andy44: Ok, so let us first talk about the details in the mailing lists :-) Nov 11 02:48:58 Andy44: btw, I'll need to be away for a while. Nov 11 02:49:35 Thanks for your help! Nov 11 02:49:54 Andy44: you're welcome! **** ENDING LOGGING AT Fri Nov 11 02:59:57 2011