martin welsh wrote: > I am fumbling through and have now got to chapter 7 but not without some > bother with the instructions. > Early on you are told that you start by building the tools chain and > should start from $LFS/tools. > Next - mkdir build file > next - cd build file ok so far. > Then unpack source (to be built file) in build file. Still ok. > Next - possibly a preamble but more to the point ../configure 'the file > being built' possibly with qualifiers. > > This is not ok because ../configure needs to be ./configure.
Where does it say ../configure? If it does say that anywhere that's a typo. As the instructions at the beginning say, all commands should be executed within the extracted source directory. > > Again the way that patches work for me is that you put the patch in the > folder to be patched and then go for the patch instruction. > Ch 5.9.1Expect - excuse the pun. I think "most" people have an area where they keep the source tarballs and do the building (it is pretty arbitrary where your build directory is). So in my "sources" directory I have all the tarballs and the relevant patches. When I need to patch (I am always in the source directory) I type the command "patch -Np1 -i (sources_dir)/patch_file_name I think it is really bad practice to have the patch file *inside* the source tree. It probably won't do any harm, but you are - effectively - contaminating the source tree with an external file. > > I am in $LFS/tools/expect(unpacked) and I have copied the patch into > expect(unpacked). > Next patch -Np1 -i ../expect............... > > This is not ok because again ../expect..... should be ./expect....... > > The same hiccup but a different flavour. > > As I have gone through the book I have tried to think of an elegant > solution which will ensure that future readers do not make the mistakes > that I have. > > The only solution I have thought of is to precede each chapter, the bit > where the user starts typing, with a simple statement saying what > folders should be where. > > > Perhaps $LFS/tools then mkdir -v build-folder > Unpack in $LFS/tools/build-folder > > It is a very good teacher that can place the words so that everybody > receives the same message. > It is a genius who does it for dyslexics. > > martin welsh I think that this is probably something that has to be learnt the hard way. Moving through directory structures, what the "." and ".." do, the basics of building things from source are all what this book needs you to know *before* you learn how to make a Linux System. Having said that, by making mistakes and using the mailing lists like these, you will "get" this stuff pretty quickly. And once you have, it will set you up for a long and happy relationship with Linux and Open Source Software in general. If "every" step was so clearly laid out that it was basically idiot proof, I don't think many people would learn very much at all. I *know* I wouldn't have. Have fun... Alan -- The way out is open! http://www.theopensourcerer.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
