We also have a wonderful LFS community that is willing to offer
assistance through the mailing lists and IRC (see the Section 1.4,
“Resources” section of this book). However, we get
several support questions every day and many of them can be easily
answered by going to the FAQ and by searching the mailing lists
first. So, for us to offer the best assistance possible, you need to
do some research on your own first. That allows us to focus on the
more unusual support needs. If your searches do not produce a
solution, please include all relevant information (mentioned below)
in your request for help.

1.5.1. Things to Mention

Apart from a brief explanation of the problem being experienced,
the essential things to include in any request for help are:

Note

Deviating from this book does not mean that we will not help you.
After all, LFS is about personal preference. Being upfront about
any changes to the established procedure helps us evaluate and
determine possible causes of your problem.

1.5.2. Configure Script Problems

If something goes wrong while running the configure script, review the
config.log file. This file may
contain errors encountered during configure which were not printed
to the screen. Include the relevant lines if you need to ask for
help.

1.5.3. Compilation Problems

Both the screen output and the contents of various files are useful
in determining the cause of compilation problems. The screen output
from the configure
script and the make
run can be helpful. It is not necessary to include the entire
output, but do include enough of the relevant information. Below is
an example of the type of information to include from the screen
output from make:

This is not enough information to properly diagnose the problem
because it only notes that something went wrong, not what went wrong. The entire section, as
in the example above, is what should be saved because it includes
the command that was executed and the associated error message(s).