On Wed, Nov 14, 2012 at 06:49:34AM -0800, Paige Thompson wrote: > > heres that there script i been usin: > https://github.com/paigeadele/erraticOS/blob/master/usr/src/bootstrap_userland.sh >
The *first* time you build LFS, run all the commands through by hand - pasting from the browser is perfectly ok. But before you restart, check the host-prerequisites section and fix up any missing packages. Yes, doing it unscripted takes longer. While packages are building, take the time to read the page about what you are doing, and make sure you don't omit any steps. When you have built LFS successfully, scripts are good. By that stage you should have a deeper understanding of what *can* go wrong, and also of what logging (if any) you wish to achieve. Equally, you should then be in a position to diagnose where the error is likely to be. I don't claim to understand your script (the use of compile.list looks cool, I just don't see where it ever gets updated), but I note two things : 1. You are using apt-get before you begin. Is /bin/sh a symlink to dash ? If so, that is not adequate. 2. You seem to be using git checkouts instead of tarballs - fair enough, if you have the bandwidth and if the versions agree. This does mean that your scripts become excessively long. Earlier, you had the 'No such file' error - that is because something has linked to a host library that no longer exists in chroot : it's in the FAQ. You mentioned using the host 'ld', I think. When you do things differently, you *will* get unusual errors. If you can't fix them after googling, it will often be some hours before you get any response : we aren't all keeping the same hours ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
