Automatic chroot build infrastructure?

[Mike Frysinger]

On Mon, Dec 12, 2005 at 01:51:23PM -0500, John Kelly wrote:
> For instance, buildroot's third pass of gcc is missing syslimits.h,

this is an upstream gcc bug, not specific to buildroot

> which the makefile tries to correct,

s/tries to correct/corrects/

> and the specs file still says it's a cross compiler, and they try to
> fix that with a sed.

the final specs file comes from the compiler used to build the native
compiler and 99% of the time, the only difference between the two spec
files is the setting of the cross_compile field

> So after
> three passes, buildroot does not cleanly produce a native compiler.

it produces a native compiler as close as is possible considering the
upstream status of cross-compiling in gcc itself

> Buildroot was not designed with the hlfs or diy concept in mind, where
> you want to reach a self hosting state with uclibc.

sure it was ... ive used buildroot plenty of times to generate a self
hosting environment which i then used to bootstrap Gentoo
-mike