Re: [gentoo-embedded] Current Status?

[Ned Ludd]

On Mon, 2004-07-26 at 16:32, Alex wrote:
> > I'm rather fond of building packages and then installing those packages
> > into the $ROOT vs
>
> So when you want to emerge a package, you do something like:
>
>  	(ARCH/USE/etc) emerge -B app --nodeps
>  	(ARCH/USE/etc) ROOT="/someroot" emerge --usepkg app
>

> How do you handle libc and PAM dependencies? What about things like
> baselayout? How do you handle dependencies?

Well here is currently what I'm doing. (not really officially support
yet)

I have a native-uclibc-x86 chroot which I emerge stuff all day long in
with FEATURES="buildpkg" 
I then use two scripts I wrote to handle staging these into my desired
ROOT

First one converts the package format from .tbz2 into .ipk and cleans up
some of the left over cruft that's not needed at runtime (like .a/.h
files etc)
Then those ipk files are installed to my target dir and I do a second
round of cleaning to clean out some of the other cruft I don't desire.

The whole thing sorta looks like this.

uCsimple shm # ./genipkg install
>>> Installing baselayout-lite-1.0_pre1.ipk to /dev/shm/binroot
>>> Installing uclibc-0.9.26-r3.ipk to /dev/shm/binroot
>>> Installing busybox-1.0.0_pre20040726.ipk to /dev/shm/binroot
>>> Installing bridge-utils-0.9.6-r1.ipk to /dev/shm/binroot
>>> Installing chillispot-0.94.ipk to /dev/shm/binroot
>>> Installing dropbear-0.42.ipk to /dev/shm/binroot
>>> Installing ebtables-2.0.6.ipk to /dev/shm/binroot
>>> Installing iproute2-2.4.7.20020116.ipk to /dev/shm/binroot
>>> Installing iptables-1.2.9-r4.ipk to /dev/shm/binroot
>>> Installing libpcap-0.8.3-r1.ipk to /dev/shm/binroot
>>> Installing lilo-22.5.9-r1.ipk to /dev/shm/binroot
>>> Installing net-snmp-5.1.1.ipk to /dev/shm/binroot
>>> Installing pcmcia-cs-3.2.5-r1.ipk to /dev/shm/binroot
>>> Installing vtun-2.6.ipk to /dev/shm/binroot
>>> Installing zlib-1.2.1-r2.ipk to /dev/shm/binroot
>>> Installing tcpdump-3.8.3-r1.ipk to /dev/shm/binroot
>>> Installing wireless-tools-26-r1.ipk to /dev/shm/binroot
>>> Installing madwifi-driver-0.1_pre20040726.ipk to /dev/shm/binroot
>>> Installing hostap-driver-0.1.3.ipk to /dev/shm/binroot
>>> Installing hostap-utils-0.1.2.ipk to /dev/shm/binroot
>>> Installing hostapd-0.1.0.ipk to /dev/shm/binroot
>>> Setting up busybox symlinks
>>> Setting up linux kernel /usr/src/linux/arch/i386/boot/bzImage
>>> Setting up cramfs - 4.8M
>>> Setting up squashfs - 4.3M
>>> Done
9.7M    .

-- 
So if I wanted to add apache to this environment I'd do

uCsimple shm # ./genipkg install apache
>>> Repacking apache-2.0.50.tbz2 apache-2.0.50.ipk
>>> Installing apache-2.0.50.ipk to /dev/shm/binroot
>>> Setting up busybox symlinks
>>> Setting up linux kernel /usr/src/linux/arch/i386/boot/bzImage
>>> Setting up cramfs - 5.9M
>>> Setting up squashfs - 5.2M
>>> Done
14M     .

--
Here is the script I'm playing with (use at your own risk). 
It fetches the other as needed.
http://oc12.net/~solar/uclibc/gentoo/x86/packages/genipkg

But this only works in a native-environment.
For cross-* many things still have to be planned among the lot of us
developers and users. And unfortunately I've gotten really crappy
feedback or none from people wanting to cross compile.

PAM? pam is not even an option in my minds eye as it's not supported in
uclibc environments and glibc in an embedded environment is a joke.

> Then to build for an embedded system, you end up generating a script of
> which packages (and in what order) to emerge?
>
> Thanks
>
> -Alex
-- 
Ned Ludd <solar@g.o>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer