On 3/6/07, Dave Klingler <[EMAIL PROTECTED]> wrote: > > Continuing, I expected to be able to skip ahead to > Chapter 6.7, the installation of Linux standard > headers. When I started compiling glibc-2.3.6, > though, the build crapped out during the linking stage > and I discovered that configure had somehow missed > types.h, stdlib.h, stat.h, etc. Going back to the > Kurobox I discovered that the same thing happened if I > attempted a build of glibc-2.3.6 using --prefix=/usr > on that box tool. Everything goes fine if I use > --prefix=/tools. The relevant files are all sitting > in /usr/lib/sys, right where they're supposed to be,
I'm not sure why you think you can skip to Ch. 6.7. One of the essential pieces of building glibc is getting the kernel headers in place. And our gcc is not going to look in /usr/lib/sys. The default is to look in /usr/include/sys, where the headers are supposed to be. But, it'd help to see specific errors. Also, it's kind of hard to understand what you're doing if you're jumping around. Are you following the LFS build style? I.e., building into a separate directory and then chrooting to it for the final system? If you're just trying to install over the top of an existing system, then I can't say that satisfaction will be guaranteed. Also, Jim's suggestion that you use Cross-LFS is a good one. No one here has tried to build on PPC in a long time (that I know of). Although, getting the native build going on PPC probably isn't too much effort, and it seems like you've already found most of the needed workarounds. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
