**** BEGIN LOGGING AT Sat Jun 04 02:59:56 2011 Jun 04 12:11:37 03Paul Eggleton  07master * r764e4e4fc4 10openembedded.git/contrib/opie/opie_find_patches.sh: Jun 04 12:11:37 contrib/opie: add trivial script to find all Opie patches Jun 04 12:11:37 Signed-off-by: Paul Eggleton Jun 04 12:11:40 03Paul Eggleton  07master * r4fc30b45de 10openembedded.git/recipes/opie-vmemo/opie-vmemo_1.2.5.bb: Jun 04 12:11:40 opie-vmemo: remove bogus DEPENDS Jun 04 12:11:40 libopie2 is already a dependency from opie.bbclass and RDEPENDS will be Jun 04 12:11:40 handled by shlibdeps. Jun 04 12:11:40 Signed-off-by: Paul Eggleton Jun 04 12:11:40 03Paul Eggleton  07master * rc3ae171031 10openembedded.git/recipes/opie-recorder/opie-recorder_1.2.5.bb: Jun 04 12:11:41 opie-recorder: remove bogus DEPENDS Jun 04 12:11:41 libopie2 is already a dependency from opie.bbclass and RDEPENDS will be Jun 04 12:11:42 handled by shlibdeps. Jun 04 12:11:42 Signed-off-by: Paul Eggleton Jun 04 12:11:43 03Paul Eggleton  07master * r40794b7886 10openembedded.git/recipes/libqpe/ (libqpe-opie.inc libqpe-opie_1.2.5.bb libqpe-opie_cvs.bb): Jun 04 12:11:43 libqpe-opie: move DEPENDS value to .inc file Jun 04 12:11:44 Small tidy-up now 1.2.4 has been removed. Jun 04 12:11:44 Signed-off-by: Paul Eggleton Jun 04 12:11:45 03Paul Eggleton  07master * rf813ec8fdb 10openembedded.git/recipes/opie-packagemanager/ (opie-packagemanager.inc opie-packagemanager_1.2.5.bb): Jun 04 12:11:46 opie-packagemanager: move DEPENDS value to .inc file Jun 04 12:12:00 03Paul Eggleton  07master * r513603289e 10openembedded.git/recipes/opie-sh/ (opie-sh_1.2.5.bb opie-sh_cvs.bb): Jun 04 12:12:00 opie-sh: add missing opie-sh-path.patch Jun 04 12:12:00 opie-sh-path.patch was in the 1.2.4 recipe but was missing from the _cvs Jun 04 12:12:00 recipe, thus it was never in the 1.2.5 recipe that was created from it. Jun 04 12:12:00 Signed-off-by: Paul Eggleton Jun 04 12:12:01 03Paul Eggleton  07master * re4060679f3 10openembedded.git/recipes/ (212 files in 188 dirs): Jun 04 12:12:01 Opie: remove 1.2.4 recipes and obsolete patches Jun 04 12:12:02 Signed-off-by: Paul Eggleton Jun 04 13:09:08 03Paul Eggleton  07master * r5e8e131ffa 10openembedded.git/recipes/libopie/ (libopie2.inc libopie2_1.2.5.bb): Jun 04 13:09:08 libopie2: tidy up for 1.2.5 Jun 04 13:09:08 * Move opimmemosortvector.h handling to .inc file Jun 04 13:09:08 * Remove DEFAULT_PREFERENCE = "-1" Jun 04 13:09:08 * Remove comment about SQL not supporting sync Jun 04 13:09:08 Signed-off-by: Paul Eggleton Jun 04 13:09:10 03Paul Eggleton  07master * r6fde2fa626 10openembedded.git/recipes/opie-security/ (opie-security.inc opie-security_1.2.5.bb): Jun 04 13:09:10 opie-security: move do_install customisations to .inc file Jun 04 13:09:11 Small tidy-up now older version that required this has been removed. Jun 04 13:09:11 Signed-off-by: Paul Eggleton Jun 04 13:09:11 03Paul Eggleton  07master * r6cff68572f 10openembedded.git/recipes/opie-taskbar/ (4 files in 2 dirs): Jun 04 13:09:12 opie-taskbar: tidy up installation of configuration files Jun 04 13:09:13 * Remove OE copy of 03opiesignal file and use one from Opie source instead Jun 04 13:09:13 * Move do_install parts to .inc file now that 1.2.4 has been removed Jun 04 13:09:14 Signed-off-by: Paul Eggleton Jun 04 13:17:39 03Denis 'GNUtoo' Carikli  07org.openembedded.dev * r158199fba0 10openembedded.git/recipes/base-files/ (base-files/nokia900/fstab base-files_3.0.14.bb): Jun 04 13:17:39 base-files: fix nokia900's fstab and bump PR Jun 04 13:17:39 With the newer meego kernels the oneNAND is now at /dev/mmcblk1p1 Jun 04 13:17:39 Signed-off-by: Denis 'GNUtoo' Carikli Jun 04 13:17:50 03Denis 'GNUtoo' Carikli  07org.openembedded.dev * r40a069d9dc 10openembedded.git/recipes/images/shr-image.inc: Jun 04 13:17:50 shr-image.inc: add support for kexecboot for nokia900 Jun 04 13:17:50 Kexecboot needs a boot.cfg, so we add it. Jun 04 13:17:50 Note that the messed up identation is necessary for not getting the identation Jun 04 13:17:51 in the target boot.cfg file Jun 04 13:17:51 Signed-off-by: Denis 'GNUtoo' Carikli Jun 04 13:17:52 03Denis 'GNUtoo' Carikli  07org.openembedded.dev * r6a65a05de2 10openembedded.git/ (3 files in 3 dirs): Jun 04 13:17:52 linux-nokia900-meego: update with lastest source release from meego Jun 04 13:17:53 Note that the defconfig was updated too. Jun 04 13:17:53 Its size is 1.8M(so it could be flashed as zImage if necessary) Jun 04 13:17:54 The defconfig update fixes many issues such as the headphones amplifier not Jun 04 13:17:54 initializing correctly for instance. Jun 04 13:17:55 Signed-off-by: Denis 'GNUtoo' Carikli Jun 04 13:20:40 hi Jay7 Jun 04 13:21:19 how fast is kexec booting normally if you don't count the time where it boots until the menu? Jun 04 13:21:26 the same than with a normal kernel Jun 04 13:21:32 or way longer like I have Jun 04 13:21:59 GNUtoo: on Z it depends on presence of jffs2 in NAND Jun 04 13:22:17 with clean nand - about 3 sec iirc Jun 04 13:22:26 but we are using very small kernel Jun 04 13:22:35 I wans't very clear Jun 04 13:22:37 about 800Kb with initramfs included Jun 04 13:22:39 basically I've that: Jun 04 13:22:45 it boots until the kexec menu Jun 04 13:22:48 that's very very fast Jun 04 13:23:02 but then I choose to boot on microsd within the menu Jun 04 13:23:06 the screen becomes black Jun 04 13:23:07 ah, you mean after kexec Jun 04 13:23:09 and I wait very long Jun 04 13:23:12 very very long Jun 04 13:23:27 03Paul Eggleton  07master * re6a4e3f302 10openembedded.git/conf/distro/ (5 files): Jun 04 13:23:27 conf/distro: update distro Opie references to 1.2.5 Jun 04 13:23:27 Move all distro files still pointing to Opie 1.2.4 preferred versions Jun 04 13:23:27 inc file to use the 1.2.5 one. Jun 04 13:23:27 Signed-off-by: Paul Eggleton Jun 04 13:23:29 03Paul Eggleton  07master * re511d7ad9e 10openembedded.git/conf/distro/include/ (2 files): Jun 04 13:23:29 conf/distro/include: update preferred-opie-* for 1.2.4 removal Jun 04 13:23:29 * Remove 1.2.4 file Jun 04 13:23:29 * Update git prepended version number to 1.2.5 Jun 04 13:23:30 Signed-off-by: Paul Eggleton Jun 04 13:23:31 way longer than if I flash a zImage to boot without kexec or if I use a chinloaded uboot Jun 04 13:23:33 GNUtoo: can you look on serial what is happenind there? Jun 04 13:23:51 I've no serial yet Jun 04 13:24:04 it may be some kexec problem Jun 04 13:24:15 but since it boots Jun 04 13:24:19 I've the dmesg Jun 04 13:24:32 is it timestamped? Jun 04 13:24:37 of course Jun 04 13:24:44 where is delay? Jun 04 13:24:48 but I've no idea how to decode the timestamps Jun 04 13:25:00 I'll look Jun 04 13:25:04 it's seconds from 1970-01-01 Jun 04 13:25:07 let me reflash the kexecboot kernel Jun 04 13:25:11 date should be able to decode Jun 04 13:25:15 ok nice Jun 04 13:25:24 pastebin dmesg somewhere Jun 04 13:25:40 ok wait a sec I'll flash it before Jun 04 13:25:41 and mark time when you start booting with kexecboot Jun 04 13:25:55 I mean that: Jun 04 13:25:56 [ 0.000000] Jun 04 13:26:03 [ 0.160979] Jun 04 13:26:06 that kernel stuff Jun 04 13:26:08 seconds from start then Jun 04 13:26:16 yes probable Jun 04 13:39:55 hi jay7 Jun 04 13:39:57 and gnutoo Jun 04 13:40:08 hello, woglinde Jun 04 13:40:17 hm I will build now a opie image I think Jun 04 13:40:17 hi Jun 04 13:40:19 with uclibc Jun 04 13:40:23 and systemd Jun 04 13:40:56 for armv4? :) Jun 04 13:41:38 qemu Jun 04 13:41:40 arm Jun 04 13:42:37 grrr 0xFFFF Jun 04 13:43:34 I'll reboot Jun 04 13:43:40 I cannot flash a thing Jun 04 13:43:57 use flasher Jun 04 13:43:59 *g* Jun 04 13:49:41 it was the kernel or hardware not 0xFFFF Jun 04 13:50:09 flasher is non-free btw and it would have failed the same way Jun 04 13:50:09 hehe Jun 04 13:52:57 woglinde, are the timing printk in seconds? Jun 04 13:53:05 or in jifties Jun 04 13:53:09 or something else? Jun 04 13:53:30 Jay7, http://pastie.org/2018272 Jun 04 13:54:08 roughly: Jun 04 13:54:10 [ 1.649291] mmcblk1: p1 Jun 04 13:54:10 [ 7.534912] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null) Jun 04 13:54:19 there is a big jump here Jun 04 13:55:07 I've rootwait Jun 04 13:55:59 GNUtoo: try to reformat Jun 04 13:56:06 or try with another card Jun 04 13:56:15 ok Jun 04 13:56:21 with anothe card it's similar Jun 04 13:56:23 GNUtoo: is 7 seconds looks like full time? Jun 04 13:56:36 it's more than 7 sec Jun 04 13:56:39 from pressing enter to rootmount? Jun 04 13:56:49 for the full boot Jun 04 13:56:59 maybe more than one minute Jun 04 13:57:10 I'll get a watch and calculate Jun 04 13:57:16 can you see when init is started? Jun 04 13:57:36 mostly Jun 04 13:57:45 it's hard to see since I've no backlight Jun 04 13:57:52 but the screen is on at that point Jun 04 13:58:02 is it started later than 7 sec? Jun 04 13:58:15 let me count Jun 04 13:58:23 I can bootchart if you want Jun 04 13:58:34 well.. it would be useful Jun 04 14:00:03 about 1 min in the total dark Jun 04 14:00:04 then Jun 04 14:00:16 I see stuff on the black screen Jun 04 14:00:22 then 30 s later it's totally booted Jun 04 14:02:12 so 1 min in the dark for kernel booting Jun 04 14:02:16 I just want to find where is delay.. possible places are: 1) between kexec -l and kexec -e (loading kernel), 2) between kexec -e and actual kernel start 3) somewhere in kernel 4) somewhere in userland Jun 04 14:02:20 and then 30 sec for the rest Jun 04 14:03:08 1)unlikely, I tried it before and it seemed fine, also count that the dark screen happend right after pressing enter Jun 04 14:03:33 4)unlikely too since I saw the screen messages Jun 04 14:04:28 GNUtoo: have you /var/log/messages? Jun 04 14:04:53 I've logread Jun 04 14:05:47 hm.. messages have no 'Starting init'.. Jun 04 14:07:27 http://pastie.org/2018320 Jun 04 14:10:12 seems not 3) as well.. there is only 8 secs of kernel boot Jun 04 14:10:34 8 secs for kernel + 2 secs up to klogd Jun 04 14:10:44 8 secs for kernel? Jun 04 14:11:16 looks like Jun 04 14:11:42 ah, almost 9 Jun 04 14:12:00 klogd is started in 10 secs Jun 04 14:12:41 Jan 1 01:00:10 nokia900 user.info kernel: [ 1.502502] Freeing init memory: 244K Jun 04 14:12:42 hm.. Jun 04 14:12:45 hm what machine and system? Jun 04 14:12:49 n900? Jun 04 14:12:50 nokia900 Jun 04 14:12:52 woglinde: GNUtoo's n900 Jun 04 14:12:55 yes n900 Jun 04 14:12:59 why the kernel tooks so long? Jun 04 14:13:00 seems I'm wrong a bit Jun 04 14:13:02 distro SHR Jun 04 14:13:05 image shr-image Jun 04 14:13:14 and kexec boot build with oe Jun 04 14:13:21 and included in locally built kernel Jun 04 14:13:21 init is started in 1.5 sec Jun 04 14:13:31 systemd Jun 04 14:14:08 well, I should go now Jun 04 14:14:26 GNUtoo: things should be easier with serial console Jun 04 14:14:28 ok, see you later Jun 04 14:14:51 I think the serial console is something like 2.6V Jun 04 14:15:00 I'm afraid to apply 3.3v Jun 04 14:16:17 I'll try to mesure without kexec Jun 04 14:26:27 else the boot takes 25 sec Jun 04 14:26:58 so there is one minute lost somewhere Jun 04 14:27:52 lol Jun 04 14:27:55 1 minute Jun 04 14:40:46 indeed that's huge Jun 04 14:44:34 hi ao2 Jun 04 14:45:17 hi Jun 04 14:51:53 he mr crofton Jun 04 15:17:14 which bitbake is required to build oe-core? bitbake < 1.12 seems to be unsupported due to the missing fetcher2, bitbake 1.12 fails due to the broken fetcher2 and '-g' with bitbake master fails with 'AttributeError: 'NoneType' object has no attribute 'bbfile_config_priorities'' :( Jun 04 15:20:43 Hi Jun 04 15:21:08 How to clean a build to begin again? Jun 04 15:21:56 ChanServ, aloisiojr, aloril, amarsman, anarsoul, AnssiN_ Jun 04 15:21:58 How to clean a build to begin again? Jun 04 15:22:22 hi, what's that: Jun 04 15:22:25 unresolvable R_ARM_THM_CALL relocation against symbol `memcpy@@GLIBC_2.4' Jun 04 15:22:47 Nobody can listen you Jun 04 15:22:54 Me too Jun 04 15:23:06 You need to highlight all Jun 04 15:23:46 ensc you need to define something Jun 04 15:23:54 ensc look at the meta-oe layer Jun 04 15:24:16 How to clean a build to begin again? Jun 04 15:24:36 woglinde: this happens with -g only, plain 'bitbake foo' does not trigger this error Jun 04 15:25:00 SyNko remove your oetmp-dir Jun 04 15:26:51 Ok, thanks, im bulding armstrong any suggestions? Jun 04 15:27:32 *amstrong Jun 04 15:28:09 no Jun 04 15:30:25 For now i got "Parsing recipes" and after some error Jun 04 15:30:56 It gives "Error: function 'staging_helper' failed" Jun 04 15:32:16 SyNko when you want to start from the begin remove the oetmp-dir which you specified in local.conf Jun 04 15:41:23 woglinde : it says "logfile of failure stored in: /dev/null" how to change this? Jun 04 15:42:14 when you remove the oetmp-dir? Jun 04 15:42:24 Yeap Jun 04 15:42:34 Already removeed Jun 04 15:42:44 And done another build Jun 04 15:42:56 Get the same error Jun 04 15:44:21 "Task staging_helper: failed" Jun 04 15:44:35 hm try to update bitbake Jun 04 15:44:59 K Jun 04 15:51:58 anyone for unresolvable R_ARM_THM_CALL relocation against symbol `memcpy@@GLIBC_2.4' ? Jun 04 15:52:16 woglinde : the new version of bit bake give me an error on setup.py install command Jun 04 15:54:38 woglinde, should I ask khem ? Jun 04 15:54:57 JaMa|Zzz, would know I guess but he's not in front of his computer Jun 04 15:55:44 gntuoo yes Jun 04 15:55:51 ok Jun 04 15:55:52 hi khem Jun 04 16:09:43 woglinde: i've got a news: "cannot map 'amd64' to linux kernel architecture Jun 04 16:16:43 GNUtoo: still not in front of my computer, but what's the problem? Jun 04 16:16:50 R_ARM_THM_CALL while building what? Jun 04 16:17:18 JaMa|Wrk, a dep of mplayer Jun 04 16:17:27 libav- Jun 04 16:17:34 *libav-2 Jun 04 16:18:40 that's known and reported to khem too Jun 04 16:18:43 mmt Jun 04 16:19:03 GNUtoo: http://wiki.shr-project.org/trac/wiki/Building%20SHR#ffmpegandlibav Jun 04 16:20:18 ok Jun 04 16:27:04 yeah thumb stuff Jun 04 17:00:16 woglinde: i've got a news: "cannot map 'amd64' to linux kernel architecture Jun 04 17:03:35 SyNko hm what are you building? Jun 04 17:03:39 x86 on x86? Jun 04 17:04:12 On amd64 a system of 64 bit Jun 04 17:04:49 X86 on 64bit Jun 04 21:29:39 pb_: ping Jun 04 21:35:33 bluelightning ping Jun 04 23:05:21 Hi everybody, may anybody explain PREFERRED_RPOVIDERS and DISTRO_FEATURES please Jun 04 23:06:03 I checked manual but there is not enough explanation in manual, I did not understand them Jun 04 23:06:22 I will appreciate if somebody explain to me Jun 04 23:16:44 I got PREFERRED_PROVIDERS now, but I still need to explanation of DISTRO_FEATURES :) Jun 05 00:13:57 can anybody tell me relation and differences in MACHINE_FEATURES and DISTRO_FEATURES please? Jun 05 00:57:41 kays_: from the manual: "Machine options are meant to reflect capabilities of the machine, distro options list things distribution maintainers might want to add or remove from their distros images." Jun 05 00:59:45 then what does kernel26 mean in MACHINE_FEATURE Jun 05 01:00:06 it means the machine uses a 2.6 kernel Jun 05 01:00:09 as opposed to 2.4 Jun 05 01:00:13 it's a relic of an older era Jun 05 01:00:34 but every machine would be expected to have that in MACHINE_FEATURES I would think Jun 05 01:01:19 hmm so will bitbake check the preferred kernel version with MACHINE_FEATURES contents? Jun 05 01:02:05 nope Jun 05 01:02:19 all that does AFAIK is ensure the appropriate tools are in place for a 2.6 kernel Jun 05 01:02:29 tools and configuration Jun 05 01:03:06 if you want to select a kernel in your machine you should do PREFERRED_PROVIDER_virtual/kernel = "linux-blahblah" Jun 05 01:03:53 then if there is a specific version you need, PREFERRED_VERSION_linux-blahblah = "2.6.34" for example Jun 05 01:03:53 I set MACHINE and DISTRO FEATURES Jun 05 01:04:08 then why I need to set MACHINE_FEATURES Jun 05 01:04:18 is it handled by controller? Jun 05 01:04:35 MACHINE_FEATURES is not something that you should be setting outside a machine conf file Jun 05 01:04:36 from manual: the resulting task-base would support pcmcia but not usbhost. Jun 05 01:05:04 MACHINE just tells it which machine conf file to select Jun 05 01:06:11 I think manual says, if you select anythin which machine does not support, it wont be installed to images Jun 05 01:06:33 in manual there is not usbhost in MACHINE_FEATURES but in DISTRO_FEATURES Jun 05 01:06:50 so manual says "the resulting task-base would support pcmcia but not usbhost." Jun 05 01:06:55 am I right? Jun 05 01:07:03 items in DISTRO_FEATURES that are not in MACHINE_FEATURES won't be included yes, that's what it's saying Jun 05 01:07:22 ok Jun 05 01:07:53 how DISTRO_FEATURES items are handled? Jun 05 01:08:00 for example it contains nfs Jun 05 01:08:18 so should be a bb file like nfs.bb? Jun 05 01:08:25 no Jun 05 01:08:26 or a task like task-nfs.bb? Jun 05 01:08:59 if you have a look around in e.g. task-base.bb you will see how features are handled Jun 05 01:09:19 ok I am checking Jun 05 01:11:10 hmm so there are limited features and they all handled in task-base.bb at first Jun 05 01:11:16 right? Jun 05 01:11:25 yes I think so Jun 05 01:12:11 if it's packages that you want to add to your image, there is a separate mechanism for that also Jun 05 01:13:39 thanks bluelightning Jun 05 01:13:47 if you have time I want to ask one more question Jun 05 01:13:53 sure thing Jun 05 01:14:53 for example I want to add a new application which depends on libpthread and libc Jun 05 01:15:25 I will write a bb file to configure, compile and install issues Jun 05 01:15:44 I will call directly by -b parameter Jun 05 01:15:54 but I want to add it to my image automatically Jun 05 01:16:12 well, -b is really for debugging only Jun 05 01:16:31 so, firstly the bb should be put somewhere within the OE tree under recipes/ Jun 05 01:16:32 so which configuration file is suitable place for add this application to my image Jun 05 01:16:42 yes Jun 05 01:17:22 which image are you building atm? Jun 05 01:18:13 no, I have my own image Jun 05 01:18:30 it is provided me by board vendor Jun 05 01:19:13 ok cool, in which case you should just be able to add the name of your recipe to the end of IMAGE_INSTALL Jun 05 01:19:31 so IMAGE_INSTALL += "bob" if it's bob_1.2.3.bb Jun 05 01:19:45 within the image file that is Jun 05 01:19:45 hmm Jun 05 01:19:57 ok I got it Jun 05 01:21:34 by the way, do you know any application in openembedded for image view and slide show? Jun 05 01:21:56 I also work on beagleboard for my own test Jun 05 01:22:25 I use angstrom distro Jun 05 01:23:18 hmm, well there's probably a whole heap of such apps Jun 05 01:24:55 you could try git grep -i "DESCRIPTION.*viewer" Jun 05 01:25:04 seems to produce a few interesting results Jun 05 01:25:23 of course that might miss some that have no DESCRIPTION set, but it's a start Jun 05 01:26:50 hm ok thanks :) Jun 05 01:27:31 no worries Jun 05 01:33:02 could anyone explain why does OE try to package individual kernel modules into .ipk files when I do a bitbake virtual/kernel? Jun 05 01:33:54 Why doesn't it package everything into one? Jun 05 01:34:42 I think in the last stage of my build, it did package everything into one .ipk though Jun 05 01:35:21 agnel: it's automatic via kernel.bbclass I think Jun 05 01:36:04 the idea is you probably don't need all modules installed, just some of them Jun 05 01:36:59 if you really do want them all there should be a meta package "kernel-modules" that will drag them all in Jun 05 01:37:17 bluelightning, oh ok. thanks. Could you recommend a starting point to understand how recipes work (like how I can trace a complete execution) other than the user manual? Source code would be overkill as a start but I don't mind doing that either Jun 05 01:39:12 agnel I understood many things when I read openembedded/conf/bitbake.conf file Jun 05 01:39:35 you can see including files and many variables setting there Jun 05 01:39:36 kays_, oh ok, thanks I will check it out Jun 05 01:40:16 agnel: well, for logs of recipe building you can have a look in $TMPDIR/work/*/package-ver/temp for each package Jun 05 01:40:18 sure, I'm having a bit of trouble understanding which packages and source code are pulled in for which recipe Jun 05 01:41:17 like Ideally I'd like to take a pre-built image of some recipe, and build a single component and replace it in the image Jun 05 01:41:29 actually I am writing a document about oe what I understand while I am training Jun 05 01:41:31 without actually building the whole recipe again Jun 05 01:41:58 I try to make it a beginning document before manual reading Jun 05 01:42:09 kays_, oh ok, I would be happy to maybe read it as I'm new to OE and maybe give any feedback from a beginner's perspective Jun 05 01:42:30 agnel: I'm not sure I follow what you're aiming to do Jun 05 01:42:53 timing sucks, I really got to go but I would be happy to continue this conversation when I'm back. Thanks Guys Jun 05 01:43:17 I will share link here when I finished Jun 05 01:43:20 sure thing Jun 05 01:43:44 and I will send mail list for review Jun 05 01:43:47 agnel: you may wish to check out the yocto project docs as well, a lot of that is applicable to OE too Jun 05 01:48:32 have a nice day bluelihtning, thanks again Jun 05 01:54:53 03Paul Eggleton  07master * re21f758fd4 10openembedded.git/recipes/libopie/ (libopie2.inc libopie2_1.2.5.bb libopie2_cvs.bb): Jun 05 01:54:53 libopie2: remove legacy staging Jun 05 01:54:53 Use symlinking to provide libopie2 with the appropriate headers at Jun 05 01:54:53 compile time, and install just the "public" headers at install time. Jun 05 01:54:53 Signed-off-by: Paul Eggleton Jun 05 01:54:53 03Paul Eggleton  07master * r44d9ad1d29 10openembedded.git/recipes/opie-i18n/ (opie-lupdate-native.inc opie-lupdate-native_1.2.5.bb): Jun 05 01:54:53 opie-lupdate-native: remove legacy staging Jun 05 01:54:54 Signed-off-by: Paul Eggleton Jun 05 01:54:55 03Paul Eggleton  07master * r372c70e053 10openembedded.git/recipes/opie-ftplib/ (opie-ftplib.inc opie-ftplib_1.2.5.bb): Jun 05 01:54:55 opie-ftplib: remove legacy staging Jun 05 01:54:56 Library is now installed into standard libdir. Also remove unnecessary Jun 05 01:54:57 PROVIDES. Jun 05 01:54:57 Signed-off-by: Paul Eggleton Jun 05 01:55:00 03Paul Eggleton  07master * r22fb0f2e2f 10openembedded.git/recipes/libmailwrapper/ (libmailwrapper.inc libmailwrapper_1.2.5.bb): Jun 05 01:55:00 libmailwrapper: remove legacy staging Jun 05 01:55:00 Library is now installed into standard libdir. Jun 05 01:55:00 Signed-off-by: Paul Eggleton **** ENDING LOGGING AT Sun Jun 05 02:59:56 2011