On 04 29 2005 09:27 am, Ned Ludd wrote:
> > emerge -e system
> > # fixes a emerge ebuild bug, this should go away soon
> > emerge python
> > # continue with the rest of the emerge system
> > emerge -e system
This was just a for a work around for a bug I encountered.
> (-e system twice) You should never need todo this.
>
> > # modify make.conf and set you USE flags for the target embedded build
> > # these use flags build a smaller system with no documentation, man or
> > info pages installed
> > # the make-symlinks option of for busybox to automatically create the
> > symlinks to it
> >
> >
> > nano -w /etc/make.conf
> > USE="make-symlinks nodoc noinfo noman"
>
> nodoc/noman/noinfo are not alid USE flags. They are FEATURES= and they
> are enabled per default in the uclibc profiles.
> See: emerge info
I'll fix this.
> make-symlinks is a feature intended for people that are cross compiling
> only. If you can run the native binarys which you can cuz it's x86 based
> then you should consider doing something like so.
>
> chroot /opt/i586-pc-linux-uclibc /bin/bash --login
>
> ROOT=/dev/shm/rootfs
> mount -obind /proc/ ${ROOT}/proc/
> chroot ${ROOT} /bin/busybox --install -s
> umount ${ROOT}/proc
Should I not use busybox? I don't understand why I should not use the use
flag "make-symlinks" for busybox. If I emerge busybox without the that use
flag it don't create the smylinks for all the commands, it only install the
binary busybox.
> > # build busybox and uclibc, put into the Embedded RootFS (/Embedded
> > RootFS) # don't understand exactally how this works, someone please add
> > comments mkdir /Embedded RootFS
> > ROOT=/Embedded RootFS emerge busybox uclibc
> >
> > # emerge other software you need for you embedded target
> > ROOT=/Embedded RootFS emerge xxxxxxxxx
>
> Being that you already enabled FEATURES=buildpkg there is no point in
> building xxxxxxx again. Simply use "emerge -K" at this point.
Do you mean that I should emerge mplayer (for example) in my development
rootfs (with buildpkq use flag), and just emerge -k mplayer into my embedded
rootfs?
> > # install a kernel into Embedded RootFS
> > ROOT=/Embedded RootFS emerge vanilla-sources
> > cd /Embedded RootFS/usr/src
> > ln -s linux-
>
> No this is wrong.
>
> Your kernel building for native-* should be in
> /opt/i586-pc-linux-uclibc/usr/src/linux
> vs
> /opt/i586-pc-linux-uclibc/"Embedded RootFS"
Ok, I understand. Emerge, configure, and make the kernel in the development
rootfs and this copy it to my embedded rootfs boot directory.
> --
> Ned Ludd <[EMAIL PROTECTED]>
Thanks,
--
Heath Holcomb
[EMAIL PROTECTED]
www.bulah.com
--
[email protected] mailing list
