On Tue, Nov 03, 2015 at 04:21:29PM -0500, Michael Havens wrote: > On Tue, Nov 3, 2015 at 3:54 PM, Pat Barnes <[email protected]> wrote: > > :-)~MIKE~(-:Well After I compiled glibc again I got an error. I'm getting > frustrated! Think I'll take a break and start over at a later date.
Nobody said building a system from source was easy. For a few people, it probably is (because of their experience and knowledge), but the rest of us get problems. Sometimes caused by our own misunderstandings or our broken changes, other times caused by things which nobody else has yet encountered. What you need to do is look at the evidence you have (logs, command history, your scripts, the contents of config.log files), find the error message, and then work out what went wrong. LFS is about learning, and one thing you need to do is make a sensible diagnosis of what went wrong. 'Sensible' does not always mean 'correct', but if you can find the evidence and then use that to deduce what might have gone wrong you should be well on the way to mastering it. At this stage, building with -j1 (so that the logs are in order) is slower but will make it less hard to find compile errors because they will be near the end (compare to -jN -O where the actual error might be hundreds of lines back). To recapitulate a few things from along the way: 1. Now that you have scripts for the individual packages which appear to work (barring redundant '&&' in any of them), it might be a good idea to make a fresh start, with nothing in /tools. But first, review all your scripts for anything that you now recognise as an error, and check that you have not missed any commands. And make sure that the host things you had to change (e.g. the /bin/sh symlink ) are correct from the start of the build. 2. Remember to remove the source directories, and any -build directories, after each package is completed. 3. If it still breaks, remember that running the exact same steps again is unlikely to help. And you will usually get quicker solutions if you can manage to find the *real* error messages, even if you do not understand them. In some cases, google can help - but the important matches might be 2 or 3 pages down. In other cases, google will find totally irrelevant matches. In particular, for problems in LFS be wary of solutions from stackoverflow - the people there try to help, but few of them understand how LFS is built and I happened to find a suggestion which was sensible in other contexts, but totally irrelevant for the LFS build methd. Conversely, the linuxfromscratch part of linuxquestions often has useful responses. And remember to learn from your mistakes - the only thing worse than being bitten by an error is repeating the same error after you learn about it. Yes, we *all* do that from time to time, and it hurts. Again, when you are ready to retry, Good Luck. ĸen -- Il Porcupino Nil Sodomy Est! (if you will excuse my latatian) aka "The hedgehog song" -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
