[EMAIL PROTECTED] wrote: > I experimented with --with-sysroot earlier. It eliminates the need for a > few patches for some reason, but then gcc stupidly insists that headers > and libraries must be in usr if it is passed --with-sysroot. I don't > really like the idea of putting glibc into usr without testing it first, > simply to satisfy gcc. CLFS-2 does this and I am curious why. CLFS-2 is > still under development, tho, so maybe it won't stay in there? > CLFS-1.0 is what it is now, cross-compile /tools then use /tools to build the final system. CLFS-2.0 is a sysroot style build, It's useful when your target system is slower the crap. CLFS-3.0 is intended to be a uclibc / busybox style embedded setup. (Not started yet but always in the back of my head).
So, sysroot will stay in clfs-2.0. Even when clfs-2.0 is stable, clfs-1.0 will still be maintained. That's how I understand it anyway. Correct me if I'm wrong. _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
