**** BEGIN LOGGING AT Mon Dec 02 02:59:58 2013 Dec 02 09:28:12 morning all Dec 02 09:39:53 god dag Dec 02 09:44:26 morning pwgen, all Dec 02 09:50:13 bluelightning: i tried to build an kexecboot image, but this failed because makedev needs passed and group files. Dec 02 09:50:50 pwgen: hmm, perhaps ant_work could help there...? Dec 02 09:51:11 i tried to add them manually ( do_rootfs_perpend, but this failed . any idea how to force it to add the /etc/passwd and /etc groups Dec 02 09:51:38 btw. whats about fosdem 2014. Dec 02 09:51:59 hi Dec 02 09:52:03 I've applied for a stand, we should know in a week or two whether we're accepted Dec 02 09:52:41 sounds good. Dec 02 09:52:45 I did not see the error however there was an issue on qemux86 on world builds Dec 02 09:53:13 iirc some recent makedev change Dec 02 09:53:29 strangely was failing on qemux86 only Dec 02 09:54:55 ant_work: i took a look at makedev, and the kexecboot image stuffed failed because of absent passed file ( makedev tries to resolve the "root" entry ) Dec 02 09:55:27 maybe changeing the the text entries to numeric ones in the default devices files would help Dec 02 10:06:44 is makedev still needed in this day and age? Dec 02 10:17:55 kexecboot runs without udev, so this image needs default devices. ( i guess ) Dec 02 10:23:52 pwgen: the initramfs-kexecboot-images don't need any device Dec 02 10:23:59 udev doesn't create device entries, the kernel does Dec 02 10:24:23 CONFIG_DEVTMPFS=y Dec 02 10:24:23 CONFIG_DEVTMPFS_MOUNT=y Dec 02 10:24:53 and if devtmpfs is missing, kexecboot will recreate the devices (default) Dec 02 10:24:54 hmm . seems i need a trick to ged rid of mekedev to buld an kexecboot image .. Dec 02 10:25:14 so we reaqlly suffer from image pollution again... Dec 02 10:26:17 imagine we set IMAGE_DEVICE_TABLES = "" in our machine config Dec 02 10:26:46 so that /dev is empty Dec 02 12:15:43 * koen finds himself in the linux-dummy hole and decides to dig deeper Dec 02 12:16:02 turtles, all the way down Dec 02 12:16:45 * bluelightning does not even know what linux-dummy is for Dec 02 12:16:50 maybe that makes me a dummy Dec 02 12:20:24 bluelightning: it's for machines that don't want to build a kernel Dec 02 12:21:10 it a recipe full of empty tasks Dec 02 12:22:19 I see Dec 02 12:22:45 the recipe could probably do with a better description Dec 02 12:40:25 where does the mapping from TUNE = cortexa8hf-neon to actual compiler flags happen? Dec 02 12:40:45 there is a maze of include files, all different Dec 02 13:45:01 Crofton|work: there are indeed several files involved... if you are just interested in the final results, you can do bitbake -e | grep '^TUNE_FEATURES=' Dec 02 13:46:11 once, you get the 'features' list, you can look at their implied compilations flags in openembedded-core/meta/conf/machine/include/arm/ Dec 02 13:46:47 Crofton|work: it took me ~4 work days to follow all the includes and make sense of it Dec 02 13:48:53 then we wonder if worrying about -mtune matters :) Dec 02 13:49:29 I'm fooling around wijh an a15 and an a9 and would like to make them build the same things Dec 02 13:49:51 Crofton|work: see the thread on angstrom-devel about that Dec 02 13:50:13 in short: don't use cortex* tunes, but use armv* tunes Dec 02 13:50:43 * Crofton|work notes angstrom is using the cortex ones for beagle :) Dec 02 13:50:48 it isn't Dec 02 13:51:13 sources/meta-angstrom/conf/distro/include/arm-defaults.inc Dec 02 13:51:51 Crofton|work: https://github.com/Angstrom-distribution/meta-angstrom/blob/master/conf/distro/include/arm-defaults.inc Dec 02 13:52:11 Crofton|work: updated in all the relevant release branches as well Dec 02 13:52:30 the commit: https://github.com/Angstrom-distribution/meta-angstrom/commit/99039d846566f63247ca237c040922b97d033c60 Dec 02 13:53:42 madness :) Dec 02 13:54:07 so use armv7athf-neon :) Dec 02 13:54:12 what is the t? Dec 02 13:55:42 thumb Dec 02 13:55:49 the h is hardfloat Dec 02 14:02:18 yeah, I knew the h Dec 02 14:26:50 Hi all, how to copy all the files from "files" directory to staging dir? Do we use globs like SRC_URI = "file://*" ? Dec 02 14:32:08 Hi, If a package is provided by 2 meta-* , how do I choose the one I need? Dec 02 14:34:42 santhosh01: depends, what are the specifics here? Dec 02 14:37:43 bluelightning: ok. Let me give some details. I have a package located in 2 git servers. One is latest and the other is quite out dated. I want the latest code to be built. But bydefault, bitbake is building the old one. But PR number is taking from new bb file. I am not sure how to make my new recipe as the default one Dec 02 14:38:20 hmm, the banner bits do not tell me I am usin ghard float Dec 02 14:38:22 santhosh01: set PREFERRED_VERSION_recipename = "x.y" Dec 02 14:38:33 santhosh01: in local.conf or your custom distro config Dec 02 14:40:22 bluelightning: I tried this but no luck. when run "bitbake -s | grep mypackage" it gives NOTE: preferred version 1.0.0-1 of mypackage not available Dec 02 14:40:57 santhosh01: it must match whatever the PV of the recipe is Dec 02 14:44:04 hmm, linux dummy is getting me Dec 02 14:44:15 * Crofton|work hunts koen's patch Dec 02 14:51:02 bluelightning: i found out the problem was in bbappend Dec 02 14:51:27 bluelightning: thank you :) Dec 02 14:51:41 santhosh01: np Dec 02 16:49:36 ls Dec 02 18:17:54 qt i smachine dependent? Dec 02 18:21:42 Crofton|work: what makes you say that? Dec 02 18:21:58 I chanfged machine and it rebuilt Dec 02 18:22:06 and I seem to recal some list converstaiotn Dec 02 18:22:14 never mind Dec 02 18:25:05 we need a check for mis spelled overrides Dec 02 18:25:45 Crofton|work: that would be nice, but it's a bit more complicated than it sounds Dec 02 18:25:50 :) Dec 02 18:25:53 yep Dec 02 18:26:13 I believe it's on my "pie in the sky" todo list Dec 02 18:26:21 heh Dec 02 18:26:37 how woul dyou actullay tell what was a type, and what was deliberate Dec 02 18:27:02 right, that's one issue Dec 02 18:27:48 I am asking for the "do what I meant, not what I typed feature" Dec 02 22:19:08 hi. i am having some problems with changing from oe-classic to oe-core to build a angstrom gpe image. i could succesful build the console-image but somehow without the rootfs. runqemu complains allways about it. now i tryed to build the x11-image but this fails together with all other images i tryed. can anybody give me some tips how i can build a good working gpe angstrom image? Dec 02 23:48:41 can anyone tell me what the critical bits are for matchbox-keyboard to work? The applet is present in the dock, but 'clicking' on it does nothing. This is on a core-image-sato build for an arm9. HAVE_TOUCHSCREEN=1 and HAVE_KEYBOARD=0 in /etc/formfactor/machconfig ... nothing is really sticking out as an obvious issue. Dec 02 23:54:33 if I go to the utilities page, I can load it directly, but of course then it can not be dismissed **** ENDING LOGGING AT Tue Dec 03 02:59:58 2013