summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/B - Known issues.txt12
1 files changed, 5 insertions, 7 deletions
diff --git a/docs/B - Known issues.txt b/docs/B - Known issues.txt
index 5b8824b..0bbe7a5 100644
--- a/docs/B - Known issues.txt
+++ b/docs/B - Known issues.txt
@@ -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