Am Donnerstag, 18. Mai 2006 22:39 schrieb Dan Nicholson: > On 5/18/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote: > > root:/# strings /sources/gcc-build/gcc/cppdefault.o > > > > /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include > > /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../include/c++/4.0.3 > > /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../include/c++/4.0.3/i686-p > >c-linux-gnu > > /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../include/c++/4.0.3/backwa > >rd /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include > > /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../i686-pc-linux-gnu/includ > >e /usr/local/include > > BINUTILS > > This is definitely the problem. /usr/include should be after > BINUTILS. I don't know why it isn't. Everything else looks normal.
Hey, great that you found out the problem. From now on there is a real chance to get the whole stuff corrected. :-) > I'm stumped. I've looked over the source a few times, and I can't > figure out how this would happen. If it thought you were building a > cross compiler, then /usr/local/include shouldn't be in there, either. > > At this point, I would double check that all the simple stuff is > correct like the essential symlinks. Sorry to ask, but what are the important symlinks? I did some kind of logging for _all_ steps within the LFS building. I just wrote every single command to a text file. Well, almost every single command. When I continued my work the following day I didn't log the following three commands for example: export LFS=/media/sdb3 mount -v /dev/sdb3 $LFS su - lfs Might it be of any use to post this log? > What kind of host are you building on? I'm using Debian GNU/Linux testing. uname -a Linux veneto 2.6.15-1-686 #2 Mon Mar 6 15:27:08 UTC 2006 i686 GNU/Linux Side note: The stable version of Debian GNU/Linux is "to old" for an funny desktop experience. > -- > Dan Leonhard. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
