Gentoo Archives: gentoo-embedded

From: Ned Ludd <solar@g.o>
To: gentoo-embedded@l.g.o
Subject: Re: [gentoo-embedded] x86 SBC Gentoo Embedded HowTo version 0.03 (unfinished)
Date: Sat, 30 Apr 2005 21:51:16
Message-Id: 1114897300.5452.1367.camel@localhost
In Reply to: Re: [gentoo-embedded] x86 SBC Gentoo Embedded HowTo version 0.03 (unfinished) by Heath H Holcomb
1 [snip]
2
3 > > make-symlinks is a feature intended for people that are cross compiling
4 > > only. If you can run the native binarys which you can cuz it's x86 based
5 > > then you should consider doing something like so.
6 > >
7 > > chroot /opt/i586-pc-linux-uclibc /bin/bash --login
8 > >
9 > > ROOT=/dev/shm/rootfs
10 > > mount -obind /proc/ ${ROOT}/proc/
11 > > chroot ${ROOT} /bin/busybox --install -s
12 > > umount ${ROOT}/proc
13 >
14 > Should I not use busybox? I don't understand why I should not use the use
15 > flag "make-symlinks" for busybox. If I emerge busybox without the that use
16 > flag it don't create the smylinks for all the commands, it only install the
17 > binary busybox.
18
19 This is what I mean.
20 Notice how you only got the symlinks in your development environment vs
21 all the ones the busybox supports your embedded rootfs run-time
22 environment ? chrooting into your rootfs at some point and running the
23 above command helps because ensure you have a symlink for every given
24 applet the busybox was built to support.
25
26 > > > # build busybox and uclibc, put into the Embedded RootFS (/Embedded
27 > > > RootFS) # don't understand exactally how this works, someone please add
28 > > > comments mkdir /Embedded RootFS
29 > > > ROOT=/Embedded RootFS emerge busybox uclibc
30 > > >
31 > > > # emerge other software you need for you embedded target
32 > > > ROOT=/Embedded RootFS emerge xxxxxxxxx
33 > >
34 > > Being that you already enabled FEATURES=buildpkg there is no point in
35 > > building xxxxxxx again. Simply use "emerge -K" at this point.
36 >
37 > Do you mean that I should emerge mplayer (for example) in my development
38 > rootfs (with buildpkq use flag), and just emerge -k mplayer into my embedded
39 > rootfs?
40
41 Yes you want to really only install your built packages into the rootfs
42 vs building your packages in it to ensure no extra cruft is left behind.
43 Thats why I noted the -K vs -k flags.
44
45
46 > > > # install a kernel into Embedded RootFS
47 > > > ROOT=/Embedded RootFS emerge vanilla-sources
48 > > > cd /Embedded RootFS/usr/src
49 > > > ln -s linux-
50 > >
51 > > No this is wrong.
52 > >
53 > > Your kernel building for native-* should be in
54 > > /opt/i586-pc-linux-uclibc/usr/src/linux
55 > > vs
56 > > /opt/i586-pc-linux-uclibc/"Embedded RootFS"
57 >
58 > Ok, I understand. Emerge, configure, and make the kernel in the development
59 > rootfs and this copy it to my embedded rootfs boot directory.
60
61 correct.
62
63 --
64 Ned Ludd <solar@g.o>
65
66 --
67 gentoo-embedded@g.o mailing list