On Wed, Aug 01, 2007 at 10:20:20PM -0400, Bryan Kadzban wrote: > > Well, so far I haven't seen anything like what you were describing. I'm > building the current CLFS development book (aka what was on the web last > night and tonight), without any kind of automated process. (Yeah, yeah, > I know, automation makes it way easier. I still haven't settled on any > particular method yet, and plus copying and pasting from the browser > window makes me feel like I have some control over the process. :-P ) > > Anyway, I got the /cross-tools and /tools stuff all built, and entered > chroot. I set up the directories and symlinks and stuff, and before > starting the test-suite requirements (tcl/expect/dejagnu/tree), I tried > to build coreutils. It built fine, though I didn't install it. > > But this is running on 2.6.21.3, not 2.6.22*, so it's probably not a > great test either. It is a multilib->multilib build, though (the host > is a CLFS from around 1.0.0rc3 or so). > Brian, thanks for that info. Last I checked, the book was using linux-headers from 2.6.21.something. I moved to the kernel's own headers (like LFS) some months ago - apparently, they might give problems on some architectures. For me, using the kernel's own headers is one less piece of maintenance.
Of course, it's also possible that my problems are a result of bad karma :-) ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
