**** BEGIN LOGGING AT Tue Aug 04 02:59:57 2009
Aug 04 16:50:32 <haenschen> hi, i have problems building angstrom with bitbake from oe. after "bitbake console-image" finishes without errors my tar-image contains broken links: ./sbin/init -> .
Aug 04 16:50:55 <haenschen> what's that? 
Aug 04 16:55:13 <haenschen> anyone out there who can help, or do you need more info?
Aug 04 16:59:05 <haenschen> join #beagle on irc.freenode.net
Aug 04 18:58:35 <dcordes> haenschen, for an obvious reason this link is broken if the rootfilesystem is viewed on your build machine.
Aug 04 18:59:46 <dcordes> haenschen, I don't see where this is a problem
Aug 04 18:59:53 <dcordes> haenschen, do you have problems booting?
Aug 04 19:05:06 <haenschen> dcordes: yes, it can't find init as the link is: "./sbin/init -> ."
Aug 04 19:06:08 <dcordes> hm normally it should be /sbin/init -> /init
Aug 04 19:06:31 <dcordes> you can specify init in CMDLINE "init=/sbin/init"
Aug 04 19:06:58 <haenschen> dcordes: on irc channel #beagle they said it might be a fakeroot problem caused by my filesystem gfs2, i would try to build it again on ext3
Aug 04 19:07:14 <dcordes> in the normal console-image I don't get this symlink at all. it must be specific to the beagle machine.
Aug 04 19:07:51 <dcordes> I often use console-image as initramfs for devices without proper storage. then I must create this link manually because in the initrd init is expected in /init
Aug 04 19:08:54 <dcordes> no idea abut gfs2 filesystem. I always built the .tar.gz with OE and then either create an initrd (cpio.gz) from it or copy it to an sd card with ext3 filesystem
Aug 04 19:09:10 <dcordes> s/copy/extract/
Aug 04 19:10:01 <haenschen> dcordes: nearly every file is a link to "." or in case of busybox programs it points to "b", specifiying init on CMDLINE doesn't help if the links are broken and no "real" files are there wher i could point the link to manually
Aug 04 19:12:30 <dcordes> to "b" ? maybe you have messed up some variables in the OE setup script? are you saying you have no /sbin/init in the rootfs ?
Aug 04 19:13:49 <haenschen> dcordes: sbin/init is only a link to "."
Aug 04 19:14:30 <dcordes> how big is your filesystem? it consists only of symlinks :) ?
Aug 04 19:16:49 <haenschen> my compressed console-image.rootfs.tar.bz2 is about 8,4 MB
Aug 04 19:17:05 <dcordes> that sounds about right. so you must have some binaries?
Aug 04 19:19:34 <dcordes> haenschen, can you pastebin your enviornment variable setup script (source-me.sh) ?
Aug 04 19:22:33 <haenschen> just ahd the same thought, this is my console image content and my source script: http://pastebin.ca/1518253
Aug 04 19:24:16 <dcordes> haenschen, you should as well show this in #beagle
Aug 04 19:26:57 <haenschen> Ok thanks, but first i will try rebuild with ext3
Aug 04 19:28:03 <dcordes> haenschen, what do you mean, with ext3 ? can you be more specific? you define IMAGEFS ext3 in local.conf ?
Aug 04 19:28:06 <dcordes> can you show your local.conf?
Aug 04 19:28:55 <haenschen> dcordes: sorry, on #beagle they asked me to put the build environment on an ext3 and start the build there again
Aug 04 19:30:12 <dcordes> ah I see
Aug 04 19:30:26 <dcordes> ok you should try that
Aug 04 19:35:04 <haenschen> dcordes: thanks so far!
Aug 04 19:35:34 <dcordes> haenschen, no problem let me know if ext3 host filesystem fixed it
**** ENDING LOGGING AT Wed Aug 05 02:59:56 2009