2009/12/1 Ed W <li...@wildgooses.com> > > So look at the TinyGentoo instructions: > http://en.gentoo-wiki.com/wiki/TinyGentoo and this gives you the basic > principles >
Yeah, I'm more fond of things like this. I don't need uclibc, or embedded things ... I just use a dedicated host as my "build" chroot. I based my thoughts on http://www.gentoo.org/proj/en/base/embedded/handbook/ The problem now is that I want some targets to run with "previous version" libc, where previous comes for "anterior to my host libc/gcc". So I think you have to compile with correct "previous version" gcc. So I deduced I have to build a special env with old gcc + old libc to build my old libc based target. Is that the case ? Or can I just emerge --root=/mytarget --configdir=/mytargetconfig glibc-oldversion with my current host, and target will run correctly based on glibc-oldversion ? > > I use a kind of similar process to build my builds. I use a chroot as the > build system (basically just a roughly right stage4 build), then I chroot > into that and build packages for everything that I need, then I install all > the packages into some build directory and that becomes the new > installation. This means that the destination doesn't need portage or gcc, > etc (it's a very small and bare installation). You can also build packages > to distribute with qpkg, etc. > I'm quite near that instead that I want to directly emerge in my target build instead of building packages then unpacking them to my target. Why is the chroot useful ? Why don't you just emerge onto your target with you host ? > I personally build mine the other way and install only the stuff I need > That's I want to do to. I would prefer not unmerging things. I prefer asking myself "what should I add to nothing to have a bare minimal working system" instead of "what sould I remove from a full build-capable stage4 without breaking things". > > What I *expect* catalyst to do is to build a stage1-4 build environment, > then use that stage4 build environment to build another stage1-4 > distribution where each stage builds incrementally? > Catalyst build stages from 1 to 4 starting with a chrooted stage3 which serves as a build platform. But as soon as you talk about "stage" in Gentoo, you comes with portage, gcc and many build stuff I don't want in my target. Catalyst use a "when stage4 is built, unmerge and remove a big list of things like gcc" logic, which I don't want. At least, that's what I figured out. Anyway, thanks for the tips that was quite useful. -- Pierre. "Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson
