On Wed, Jul 27, 2011 at 06:55:29PM -0400, Bill Cunningham wrote: > Well yet again I'm having problems with glibc-2.13. Now it is saying > that gcc has not supplied a header called cpuid.h. glibc gets a little > tiring I guess the stable version has some bugs like the earlier stack > problem. The configure script doesn't even finsh now. > > Bill > I haven't built that version, but in a slightly older version of the book (12/2010) that header came from gcc pass 1 and was in /mnt/lfs/tools/lib/gcc/XXX/v.v.v/include where XXX was x86_64-lfs-linux-gnu for me (will be different if you are building 32-bit, maybe some sort of i?86) and v.v.v was the gcc version.
Most likely, either your gcc installed to the wrong place, or you didn't install it all, or there was a difference in the value of $LFS between the gcc build and the glibc build, or, I suppose, the /tools symlink might be broken. If you are building as a normal user 'lfs' (i.e. not able to create files in the host system's '/') then you can run 'find' against /tools to look for cpuid.h. If it isn't present, look at the whole (host) system to see if you managed to install it somewhere else. If you have been able to write to somewhere other than /mnt/lfs then you probably have bigger problems. Alternatively, if this is still on the old system you mentioned earlier (redhat 9?), then because your host system is too old, it's possible that cpuid.h (and perhaps other things) did not get installed by gcc - if that is the case, you are out on your own in trying to continue. I'm not saying it can't be done, only that it will need full logging so you can look at everything, good diagnostic skills, and some luck with googling for workarounds. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
