Okay, I finally completed CLFS and was able to boot the new system. However, there were a number of things that had a lovely red FAIL next to them when the system booted instead of the good old green OK. Among these was this message:
cp: cannot stat 'lib/udev/devices/*' : No such file or directory I cc'ed this to clfs-dev in case it is of some relevance there since the changes to move udev to lib64 on multilib systems were fairly recent. I built an x86_64 multilib system using the SVN version of the book. I don't recall exactly when I started, but it was within the last week or so, so the current SVN should be basically what I built with. Either way, all of the udev stuff I did pointed to /lib64, not /lib. I don't know enough to know exactly what is looking for udev in lib (the kernel I would guess), but SOMETHING is and I wouldn't think that we'd want that. Any suggestions on what I may have messed up would be appreciated. If I did everything correctly, then it appears that we have a problem with putting udev in /lib64. My first suggestion would be to created a link from /lib64/udev to /lib. I assume that that would fix the problem, but I'm not sure that that's really what we want to be telling people to do in CLFS. On some level that defeats the purpose of putting it in /lib64 in the first place. - Jonathan Davis _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
