**** BEGIN LOGGING AT Wed Aug 31 02:59:57 2011 Aug 31 08:37:37 in the meta package poky-image-base where is the meta package IMAGE_FEATURES += "apps-console-core" which it refers to? Aug 31 08:38:29 Snafflehog: apps-console-core is not really a meta-package per se, it's an image feature Aug 31 08:38:48 Snafflehog: these are defined in meta/classes/core-image.bbclass Aug 31 08:39:05 ok thank you, I'll go do some more digging! Aug 31 08:39:30 most of them do point to "tasks" (which are themselves meta-packages) Aug 31 09:04:03 Guest86108: It works with your xorg.conf ! Aug 31 09:04:46 Guest86108: the best resolution is not correctly corrected, but if i add the right resol in xorg.conf, dvi output is ok Aug 31 09:04:55 but i have no mouse/keyboard detected Aug 31 09:20:18 I think I'm missing a trick here, I'm adding dropbear to the IMAGE_FEATURES array in poky-image-minimal but it is not picking up the new recipe at build time, am I doing something seriously wrong? I have read and re-read the poky manual umpteen times now... Aug 31 10:07:38 Snafflehog: I think you may need to "bitbake -c clean task-core" when changing that variable Aug 31 10:12:34 hmm, no, that's not it... Aug 31 10:13:12 Snafflehog: right... you can't just add a package name to IMAGE_FEATURES Aug 31 10:13:20 it's not a list of packages, it's a list of features Aug 31 10:14:28 ok, so I don't really understand how to add packages and then pre-roll them into an image - I've looked at the adding a package section, but this relates to adding a custom package Aug 31 10:15:08 I can't find anywhere which explains how to include specific recipies into your build Aug 31 10:15:29 what you need to do is add "dropbear" to POKY_EXTRA_INSTALL Aug 31 10:15:34 that is a list of packages to add Aug 31 10:16:08 so add this to your local.conf: Aug 31 10:16:17 POKY_EXTRA_INSTALL += "dropbear" Aug 31 10:16:49 some of this will improve for the upcoming 1.1 release btw Aug 31 10:18:15 RP__: ping Aug 31 10:18:27 ah hah, thank you it is now re-parsing the recipes Aug 31 10:18:28 dongxiao: pong Aug 31 10:19:09 RP__: we still have a multilib block issue, the different kernel bit... Aug 31 10:19:27 dongxiao: I know, that is on my buglist for today Aug 31 10:19:42 however, it still didn't pick up the dropbear package, I think the poky-image-minimal had an update - just coincidence Aug 31 10:19:45 dongxiao: but first I need to fit the autobuilder intltool failure Aug 31 10:20:06 RP__: yes, that is the first priority Aug 31 10:30:48 Snafflehog: what does "bitbake -e | grep POKY_EXTRA_INSTALL" show? (use pastebin if it's >2 lines) Aug 31 10:31:42 "The BBPATH variable is not set" - do I have to source the enviornment again? Aug 31 10:34:39 Snafflehog: either you're in a different directory or a different shell Aug 31 10:34:56 ok, I sourced the environemt again and now I have: Aug 31 10:34:59 # POKY_EXTRA_INSTALL= dropbear Aug 31 10:34:59 POKY_EXTRA_INSTALL="dropbear" Aug 31 10:35:24 but the build still doesn't pick up dropbear Aug 31 10:36:12 right, so what about "bitbake -e | grep POKY_BASE_INSTALL" Aug 31 10:36:40 that returns nothing Aug 31 10:39:03 argh sorry Aug 31 10:40:19 I meant "bitbake -e poky-image-minimal | grep POKY_BASE_INSTALL" Aug 31 10:41:39 http://pastebin.com/AqJDNA5A Aug 31 10:45:43 Snafflehog: so it has got dropbear in it... so how did you determine that dropbear was not included in your image? Aug 31 10:47:04 when I extract the root image onto my board there is no dropbear binary available Aug 31 10:47:54 I will try again with the new image from the last build Aug 31 10:48:08 as I didn't see it compiling dropbear so I assumed that ti wasn't included Aug 31 10:48:35 Snafflehog: it's possible it may have been compiled earlier Aug 31 10:58:02 bluelightning: even with the new image dropbear is still not available Aug 31 10:58:28 well, I don't really know what to suggest, it should be there Aug 31 10:58:50 I have all the busybox binaries avaiable Aug 31 10:58:56 when you last ran "bitbake poky-image-minimal" did it do a "do_rootfs" step? Aug 31 10:59:30 yes Aug 31 10:59:41 ok, good Aug 31 10:59:54 i'll try it with another package and see if that works Aug 31 11:02:35 if you "cd tmp/work/*/poky-image-minimal*/rootfs" and then "find . -name dropbear" does it find anything? Aug 31 11:03:37 no, nothing found Aug 31 11:07:22 how about "bitbake -c clean poky-image-minimal" then "bitbake poky-image-minimal" and try the same thing Aug 31 11:10:18 still no dropbear Aug 31 11:12:12 well, this is so crazy I'm actually running my own build of bernard from scratch to see what is going on Aug 31 11:12:43 fantastic, so i take it work over at Intel then ;) Aug 31 11:12:53 you* work Aug 31 11:12:59 yes Aug 31 12:19:53 bluelightning: I am also doing a build from scratch and I recieve this error: http://pastebin.com/H218UtwP when it tries to build Python 2.6.6 - however when I then re-run the build it compiles fine Aug 31 12:20:26 This happened on this build and the first build so it is possibly a reproducable bug Aug 31 12:20:41 Snafflehog: which host distribution are you using? Aug 31 12:20:48 Archlinx 64 Aug 31 12:41:59 bluelightning: exactally the same issue with the fresh build - no dropbear binary available Aug 31 13:02:58 Snafflehog: so, I'm an idiot Aug 31 13:03:21 I've led you astray a bit... poky-image-minimal overrides IMAGE_INSTALL, so POKY_EXTRA_INSTALL never gets in there Aug 31 13:03:47 minimal is pretty minimal, it cuts out a lot of stuff including anything brought in via IMAGE_FEATURES Aug 31 13:04:24 so, if you want to add dropbear, just edit poky-image-minimal and modify the IMAGE_INSTALL line Aug 31 13:04:28 sorry for the confusion :/ Aug 31 13:06:22 ah hah, it is now compiling dropbear :) Aug 31 13:06:43 no problem with the confusion, I want to learn as much as I can about the process as possible Aug 31 13:06:59 and mistakes/problem finding is usually the best way to do it Aug 31 13:08:58 I do have another question though... does the minimal image also build kernel modules/drivers - as the ethernet on the BeagleBoard isn't being picked up - even though the usbgadget module is specified in the machine conf Aug 31 13:12:46 by not being picked up you mean there's no ethernet interface at all (usb0)? Aug 31 13:12:53 no interface what so ever Aug 31 13:13:23 ok... that's puzzling... the answer to your question is yes, you should get the appropriate modules etc. Aug 31 13:13:46 FYI, beagleboard support will improve a lot in the upcoming release Aug 31 13:13:51 usbcore picks up the smsc95xx chip which is the usb interface to the ethernet Aug 31 13:15:34 thats good news Aug 31 13:27:10 RP__: ping Aug 31 13:29:10 RP__: one question, if we build a 64 bit image, and want to install some lib32 version of library. library files will be over-written since the baselib in above cases both are "lib". Aug 31 13:30:22 dongxiao: The user would need to define baselib to be something different in that case Aug 31 13:32:00 RP__: why we don't use baselib=lib64 for 64bit system? like qemux86-64? Aug 31 13:53:35 dongxiao: don't we do that whenever multilib is enabled? Aug 31 13:58:54 RP__: yes. Is it workable? or do we have other consideration on the baselib setting? Currently I saw ppc64's baselib is set to lib64, while others are "lib" Aug 31 14:00:09 In the new poky-git where are the machine configs? Aug 31 14:03:53 no worries found them in meta-yocto Aug 31 14:44:45 morning folks Aug 31 14:50:29 bluelightning: update, I have pulled the latest git and now the beagleboard-xm is loading the correct modules and the usb0 interface is loaded Aug 31 14:51:05 5.0.1 must have some issues with loading the correct firmware/drivers but the support seems a lot more sound in the latest git Aug 31 14:51:35 Snafflehog: good stuff Aug 31 14:53:56 hi dvhart Aug 31 15:00:20 I'm now trying to compile dhcp and the build fails with the the following: Aug 31 15:00:42 http://pastebin.com/4ap8HvRL Aug 31 15:01:08 It builds and compiles but then complains it cannot find the package... Aug 31 15:03:12 Ok, I just specified dhcp when I should have been more specific, dhcp-client works - dhcp compiles all the programs under dhcp but it needs specific package names Aug 31 15:03:20 to install them Aug 31 15:55:43 I couldnot get GUI (sato) after regorous trials.. plz give me a command to start sato from commandline like '$gdm start' for gnome Aug 31 16:02:06 Arial700, there is an X init script Aug 31 16:02:11 I forget it's exact name Aug 31 16:02:13 but: Aug 31 16:02:17 /etc/init.d/x.... start Aug 31 16:11:07 dvhart, it worked !!! :) Thanks a lot.. but I dont know why... It is showing all rectangular boxes asif the font is not present Aug 31 16:11:25 Arial700, interesting Aug 31 16:11:40 if nobody has a response to that here, considering sending a report to the yocto list Aug 31 16:11:54 not even all images is showing except the green bar on the top with 'Desktop' text Aug 31 16:12:16 dvhart, yocto list ?? Aug 31 16:12:55 yocto@yoctoproject.org Aug 31 16:14:23 dvhart, thanx a lot friend !! I guess I 've missed the language pack or something .. I 'll recompile it and try Aug 31 16:14:42 sure, good luck Aug 31 16:44:55 Arial700: FWIW, those boxes usually show up if something in the postinstalls is breaking somehow Aug 31 17:00:16 RP__, ohk.. I'll look into it Aug 31 17:04:19 RP__, Thanku Aug 31 17:38:51 is anyone going to be at Plumbers next week? Aug 31 17:41:39 msm, I will be Aug 31 17:42:14 some of us from Freescale will be around also Aug 31 17:42:15 as will I Aug 31 17:42:57 is there anything yocto related planned? Aug 31 17:47:48 msm, the config fragment management bof is yocto related Aug 31 17:47:58 msm, but is of general interest Aug 31 17:48:05 (co presenting with jstultz of linaro) Aug 31 17:54:28 cool, i'll be sure to check it out Aug 31 18:20:56 how do I do an override if something is *not* set Aug 31 18:44:08 after enabling language pack I got the GUI Correctly.. Aug 31 18:44:14 ThankU All Aug 31 18:44:15 :) Aug 31 19:05:28 pidge|Zzzzzzzzz: ping when you awake Aug 31 19:05:37 RP__: pong Aug 31 19:06:01 pidge: I've pushed a fix for intltool so you could try that for a spin on ab05 Aug 31 19:07:14 RP__: awesome, spinning now. Aug 31 19:15:24 hmm ive had this intltool perl problem for a while Aug 31 19:55:29 msm: which problem? Aug 31 19:59:01 intltool shebang issues Aug 31 20:00:04 RP__: i think your patch fixes for intltool Aug 31 20:00:11 msm: being too long? Aug 31 20:00:17 msm: right, it does Aug 31 20:00:23 yes Aug 31 20:00:27 but there are other packages as well Aug 31 20:00:54 and im trying to remember how they were related to intltools if at all Aug 31 20:01:44 msm: Weren't these the ones looking for perl in PATH? Aug 31 20:01:54 msm: We should have fixed that in a previous patch Aug 31 20:02:12 my patch I have keeps rebasing so its hard to tell Aug 31 20:02:24 i just added inherit perlnative to a lot of packages Aug 31 20:03:03 which somehow had the same effect as 'export PERL=/usr/bin/env perl' Aug 31 20:03:17 well not somehow, but it did =) Aug 31 21:33:32 what deploys the compiled device tree? Aug 31 21:34:55 nvm **** ENDING LOGGING AT Thu Sep 01 02:59:57 2011