Yasser Zamani wrote: > Hi there, > > At first thank you very much for this useful site and book! > > Currently I'm doing jobs step-by-step with no getting any errors; however, > sometimes the steps are very specific e.g. GCC pass 2 steps. GCC needs that > patch, fixincludes should be suppressed, -fomit-frame-pointer should be > removed and etc. should I really remember and keep in mind these?! how book > writer discovered these? because we just do steps and if we try to e.g. use > another version then we are not sure about patches and switches, right? > > One more thing; sometimes I know why to run the script but I don't know how > script works exactly. the main example is sed. I know it edits streams to > replace or remove something but it's command in book is complicated for me at > this time to understand. Is it essential to understand how it exactly works?
The steps in book have been developed over time, In some cases, people very familiar with the internals have determined what the steps should be. Many are quite customized specifically for LFS. You shouldn't need to remember any steps. That's why we wrote them down for you. If you are interested in more detail, then we have been successful. You need to research switches like -fomit-frame-pointer to see what it does, but explaining the internals of gcc is quite a bit beyond LFS's goals. Learning sed, and regular expressions in general, can be challenging. It is a stream editor and will modify a text file by adding, deleting, or changing text in the file. Grabbing a sed reference and figuring out exactly what one of our seds are doing is an excellent learning exercise. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
