On Sat, 2012-05-05 at 19:50 +0430, 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?
Correct. The switches are usually fairly unchanged over time, but patches are a mix. Some of them are fixes for bugs not yet available in upstream releases, but others would better be described as "configuration". For example, the GCC patches are mostly of the latter type - they're there to change the GCC install during the process of building the new toolchain, and aren't used in the final GCC build. > 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? Not essential, but the book does usually try to explain them for those who want the details. Is there a particular example you're having trouble with? Also, if you're interested in understanding sed expressions, I'd suggest searching for "sed one liners", and you'll see some of the more creative examples people have come up with. It's a much more powerful tool than most people realise... Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
