uuuhuuuu!!!, my new shiny LFS (by hand no automatic tool) system is ready!!!, thank you very much fo such a great book, I follow they instructions one by one and I don't have any problem, the book don't have even a typo bug. ...now to read and follow BFLS book...my new system have only a basic bash console but I think that is better than Fedora 7...uhuuu jajaja :-)
Mauricio, from Chili Mauricio Henriquez wrote: > Hi to all: > > thank for your quick help, I re-read your book instruction and off > course you don't put anything on there that is not necesary :-) I was > using the Gcc compiled version of the chapter 5 of the book, I delete > the folder, re-extract and build again without problems. > > As I think, only a begginer problem...sorry :-( I had panic :-) , from > now on I going to re-re-read your book instruction more carefully.. I > try to finish the job now. > > thanks again.. > > Mauricio > > Dan Nicholson wrote: > >> Welcome. >> >> On 6/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >> >>> #Gcc Make error (page 97 of the PDF LFS 6.2 book) >>> In file included from ../../gcc-4.0.3/gcc/crtstuff.c:64: >>> ../../gcc-4.0.3/gcc/tsystem.h:90:19: error: stdio.h: No such file or >>> directory >>> ../../gcc-4.0.3/gcc/tsystem.h:93:23: error: sys/types.h: No such file or >>> directory >>> >>> >> I know this has come up before, but I can't recall what the issue is >> exactly. So, at that point, it should be finding those headers from >> the Ch. 5 glibc in /tools/include. But it's not for some reason. >> >> So, do those headers exist? You should definitely have >> /tools/include/stdio.h. If so, let's find out where gcc is trying to >> look. Here's a quick one-liner to make gcc be verbose about what it's >> doing. >> >> # echo | gcc -v -x c - >> >> That should spit out some info including where the system header >> search path is. Mine (using the final gcc) says: >> >> #include <...> search starts here: >> /usr/local/include >> /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include >> /usr/include >> End of search list. >> >> Yours should include /tools/include and /tools/lib/gcc-... What does >> it say for you? >> >> -- >> Dan >> >> > > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
