docs/B - Known issues.txt
changeset 2386 ff33dccf005c
parent 2384 5f260bb27b35
child 2387 41743d7a3f37
     1.1 --- a/docs/B - Known issues.txt	Thu Apr 07 19:02:56 2011 +0200
     1.2 +++ b/docs/B - Known issues.txt	Thu Apr 07 19:17:12 2011 +0200
     1.3 @@ -19,7 +19,8 @@
     1.4  
     1.5      --------------------------------
     1.6      Symptoms:
     1.7 -      A one-liner of what you would observe.
     1.8 +      A one- or two-liner of what you would observe.
     1.9 +      Usually, the error message you would see in the build logs.
    1.10  
    1.11      Explanations:
    1.12        An as much as possible in-depth explanations of the context, why it
    1.13 @@ -107,8 +108,7 @@
    1.14  
    1.15  --------------------------------
    1.16  Symptoms:
    1.17 -  While building the final gcc, I get an error message that ends with:
    1.18 -    libtool.m4: error: problem compiling FC test program
    1.19 +  libtool.m4: error: problem compiling FC test program
    1.20  
    1.21  Explanations:
    1.22    The gcc build procedure tries to run a Fortran test to see if it has a
    1.23 @@ -129,7 +129,7 @@
    1.24  
    1.25  --------------------------------
    1.26  Symptoms:
    1.27 -  gcc barfs because it is "unable to detect the exception model".
    1.28 +  unable to detect the exception model
    1.29  
    1.30  Explanations:
    1.31    On some architectures, proper stack unwinding (C++) requires that
    1.32 @@ -147,9 +147,7 @@
    1.33  
    1.34  --------------------------------
    1.35  Symptoms:
    1.36 -  Installing the C library headers and start files fails because of
    1.37 -  missing unwind support, with a message like:
    1.38 -    configure: error: forced unwind support is required
    1.39 +  configure: error: forced unwind support is required
    1.40  
    1.41  Explanations:
    1.42    The issue seems to be related to building NPTL on old versions