After reading http://dev.gentoo.org/~iggy/uclibc/gentoo-uclibc-HOWTO and doing some experiments, I believe that to achieve the above I a need a uclibc-based root fs on my gentoo development host that I can chroot too and emerge from into my deployment root. I'll call this chrootable root fs the "uclibc-based host root". Once I can chroot to this uclibc based gentoo root, I can then "ROOT=/deployment/root emerge baselayout-lite uclibc busybox" and have a small bootable root fs at /deployment/root. Do I have it right so far?
I found http://dev.gentoo.org/~solar/uclibc/uclibc.txt which I believe gives a sequence of steps for building a uclibc-based host root. I need some more details for some of the steps from this document.
From http://dev.gentoo.org/~solar/uclibc/uclibc.txt:
1) First thing you need to do is compile a prebase system using uclibc-buildroot
grab it from http://uclibc.org/downloads/snapshots/
Simple.
2) download a few files into the buildroot scripts:Where do the .mk files go? Anywhere? I guess they need to be included in some other Makefile, but where? I didn't download them, is there more info in them? I assume the patch file is just applied to the buildroot sources.
make/
http://dev.gentoo.org/~vapier/uclibc/portage.mk
http://dev.gentoo.org/~vapier/uclibc/python.mk
sources/
http://dev.gentoo.org/~vapier/uclibc/python-cross-compile.patch
3) Edit the buildroot Makefile and add python/portage to TARGETSPlease be more specific. The only place I found a TARGETS variable in the makefiles is in the util subdirectory, and that didn't seem right. But maybe it is.
4) Build & deploy the buildroot image
Hopefully this will be obvious once the previous steps are more clear.
-- Jack
-- [email protected] mailing list
