Roman I Khimov wrote: > > > I think there is a misunderstanding here. :) What I see currently in CLFS > and CBLFS is that we cross-compile some basic temporary system just to > boot/chroot into it and then compile natively everything on target. Second > part doesn't differ that much from LFS/BLFS. What I want to see is full > cross-compilation, every package builds on some build machine for target > machine and the result is not something temporary but final system. > That would be very cool. I managed to cross-compile openssh (openssl) and through all the dependencies for gtk+-2 when I got stuck. I suppose the next time I do that I'll document it. Hopefully, it will get big enough for a book. I don't think a wiki, like cblfs, would be appropriate for it. Since there are so many critical parts to a build like this. A lot of the times you need to compile a package twice to build binaries that are run during the build.
I think we could integrate this kind of information into cblfs, if we wanted to, but it would probably just clutter up the pages more then they'd need to be. CLFS-2.0 and CLFS-3.0 could both benefit a lot from something like this. _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
