docs: use the error message in the known issues titles

This helps users find the appropriate known issue entry.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
This commit is contained in:
Yann E. MORIN" 2011-04-07 19:17:12 +02:00
parent c52ca838fb
commit a5785964b7

View File

@ -19,7 +19,8 @@ The following dummy section explains it all.
--------------------------------
Symptoms:
A one-liner of what you would observe.
A one- or two-liner of what you would observe.
Usually, the error message you would see in the build logs.
Explanations:
An as much as possible in-depth explanations of the context, why it
@ -107,8 +108,7 @@ Workaround:
--------------------------------
Symptoms:
While building the final gcc, I get an error message that ends with:
libtool.m4: error: problem compiling FC test program
libtool.m4: error: problem compiling FC test program
Explanations:
The gcc build procedure tries to run a Fortran test to see if it has a
@ -129,7 +129,7 @@ Workaround:
--------------------------------
Symptoms:
gcc barfs because it is "unable to detect the exception model".
unable to detect the exception model
Explanations:
On some architectures, proper stack unwinding (C++) requires that
@ -147,9 +147,7 @@ Workaround:
--------------------------------
Symptoms:
Installing the C library headers and start files fails because of
missing unwind support, with a message like:
configure: error: forced unwind support is required
configure: error: forced unwind support is required
Explanations:
The issue seems to be related to building NPTL on old versions