I have been toying around with the dan kegels crosstool shell scripts.
why? because lfs would never build for me. actually lots things
didnt work out. i have tried lnx-bbc, rock-linux, and gentoo-catalyst.

Ideas I have tried on my own:
The Uroborus of trying make or download somebodies chroot.
Ah then use the chroot build the new system
inside the chroot. Uroborus at its worst. This is a long
way to go about just making an embedded system.

Ok.
How do I build glibc that is not dependent on the system im building on,
and then move this to a nas·cent root file system. Even more just move
binaries, not the man files, not the header files.

I looked at kegels cross tool about 6 months ago and dismissed it.
Mostly because I didnt know what it could do (or might be able to).
I began to notice that the first steps of the lfs system are
almost exactly the same steps in kegels cross tool:

* build the binutils
* build a static version of gcc
* build glibc
* build the gcc again

lfs does the same, however with out the monking around with the path
variable's and needing to create a distict user called lfs.

so how do i know that what i have built with kegels crosstool
actually works.
I could build a chroot with them.
what will i need bash env ls so forth.
or the big test build all the root files
get make a hybrid of gentoo or some other
and use my newly created root file system.