By default the book(s) normal only have only the basics about running make test or make check. if you would like to create a better way of tracking errors in tests for packages here's a suggestion when running the make check/tests commands.

Using this and similar commands for make tests and other check command directs errors into a logfile as well as output to the terminal. The -j* command is there only to help speed things up considerably.

Plus if you stumble on some serious errors you can submit the logs back to the upstream to help them out.

Alternatively, if you want all the stdout and stderr readouts to go to a log file rather than both the terminal and the log pass this command instead:

This will direct ALL output from the check to the log file. This is useful when some checks put out too much output that can crash the terminal, such as the vim package.

Thanks for the tip!

BTW, I was thinking of making a thread about something useful I found and after reading your how to, it made me think maybe we should create a general thread of tips. I think it'd be nice to have it all in one place. What does everyone think?

I think these how-tos are very useful and put it in a dedicated place would be a good idea!
Particularly i will try the "backup system using tar" next time i will install lfs.

We do need to find more and more useful hints, tips, and suggestions.

The LFS wiki is in need of some serious updates, but the project has been behind in funding for a while now. I'm wondering if they are forgoing the wiki and other things just to try and stem costs enough.