On 3/7/07, Dave Klingler <[EMAIL PROTECTED]> wrote: > --- Dan Nicholson <[EMAIL PROTECTED]> wrote: > > On 3/6/07, Dave Klingler <[EMAIL PROTECTED]> wrote: > > > > I'm not sure why you think you can skip to Ch. 6.7. <snip> > 6.7 is the installation of the kernel headers, if I'm > not misunderstanding your objection. I then proceeded > to 6.8, the installation of the man pages, and then on > to 6.9, the installation of glibc.
Oops. You're right. I didn't look and thought you were implying you jumped straight to glibc. <snip> > cd ../obj_s; /usr/bin/g++ -I../c++ -I../include -I. > -DHAVE_CONFIG_H -I. -I../include -D_GNU_SOURCE > -DNDEBUG -I/tools/include -fPIC -c ../c++/cursesf.cc > In file included from ../c++/internal.h:50, > from ../c++/cursesf.cc:34: > /tools/include/string.h:33:20: stddef.h: No such file > or directory One problem here is that you're using g++ from /usr/bin and not the one in /tools/bin that we know how it's configured. You're going to have to do some magic to make sure that you prefer the binaries in /tools/bin until you get past gcc and binutils. In LFS we can get away with putting /tools/bin at the end of PATH because the chroot is basically empty. When it starts to get populated, the new binaries are preferred. You should consider building into a separate directory that you can chroot into and then copy over your existing system later. It will be tough to keep the clean bootstrapped temp system in /tools separate from the "dirty" existing system in /. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
