Randy McMurchy wrote: > Unfortunately, my build script has them all on one line so I never > encountered this issue. (moral - make your build scripts match what > is in the book for testing book instructions!)
Agreed. I use a technique I call "Document Centric Automation". It's helped me tremendously in keeping build commands free of silly typos and thinkos. It involves extracting the build commands directly from the XML sources then feeding them to a build script. Manuel has recently implemented a "dump commands" facility for use by all the *LFS projects so now this sort of automation should be achievable. I cannot speak highly enough of using DCA style techniques as an extra tool in the QA toolbox. Regards Greg -- http://www.diy-linux.org/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
