1.1 --- a/docs/B - Known issues.txt	Thu Apr 07 19:17:12 2011 +0200
     1.2 +++ b/docs/B - Known issues.txt	Thu Apr 07 19:21:15 2011 +0200
     1.3 @@ -27,6 +27,17 @@
     1.4        happens, what has been investigated so far, and possible orientations
     1.5        as how to try to solve this (eg. URLs, code snippets...).
     1.6  
     1.7 +    Status:
     1.8 +      Tells about the status of the issue:
     1.9 +        UNCONFIRMED : missing information, or unable, to reproduce, but there
    1.10 +                      is consensus that there is an issue somewhere...
    1.11 +        CURRENT     : the issue is applicable.
    1.12 +        DEPRECATED  : the issue used to apply in some cases, but has not been
    1.13 +                      confirmed or reported again lately.
    1.14 +        CLOSED      : the issue is no longer valid, and a fix has been added
    1.15 +                      either as a patch to this component, and/or as a
    1.16 +                      workaround in the scripts and/or the configuration.
    1.17 +
    1.18      Fix:
    1.19        What you have to do to fix it, if at all possible.
    1.20        The fact that there is a fix, and yet this is a known issue means that
    1.21 @@ -53,6 +64,9 @@
    1.22    A possible fix could probably set the environment variable CCACHE_CC to the
    1.23    actual compiler used.
    1.24  
    1.25 +Status:
    1.26 +  CURRENT
    1.27 +
    1.28  Fix:
    1.29    None known.
    1.30  
    1.31 @@ -68,6 +82,9 @@
    1.32    case-sensitive. You have to use so-called "managed" mounts. See:
    1.33    http://cygwin.com/faq.html section 4, question 32.
    1.34  
    1.35 +Status:
    1.36 +  DEPRECATED
    1.37 +
    1.38  Fix:
    1.39    Use "managed" mounts for the directories where you build *and* install your
    1.40    toolchains.
    1.41 @@ -83,6 +100,9 @@
    1.42    With uClibc, it is possible to build a cross-ldd. Unfortunately, it is
    1.43    not (currently) possible to build this cross-ldd under Cygwin.
    1.44  
    1.45 +Status:
    1.46 +  DEPRECATED
    1.47 +
    1.48  Fix:
    1.49    None so far.
    1.50  
    1.51 @@ -100,6 +120,9 @@
    1.52    core gcc is not located in the same place it is located when building
    1.53    with shared companion libraries.
    1.54  
    1.55 +Status:
    1.56 +  DEPRECATED
    1.57 +
    1.58  Fix:
    1.59    None so far.
    1.60  
    1.61 @@ -120,6 +143,9 @@
    1.62    will not be built. There is nothing to be worry about (unless you do
    1.63    want to build the Fortran frontend, of course).
    1.64  
    1.65 +Status:
    1.66 +  CURRENT
    1.67 +
    1.68  Fix:
    1.69    None so far. It's a spurious error, so there will probably never be
    1.70    a fix for this issue.
    1.71 @@ -137,6 +163,9 @@
    1.72    need sjlj. On some architectures, gcc is unable to determine whether
    1.73    sjlj are needed or not.
    1.74  
    1.75 +Status:
    1.76 +  CURRENT
    1.77 +
    1.78  Fix:
    1.79    None so far.
    1.80  
    1.81 @@ -154,6 +183,9 @@
    1.82    of glibc (and possibly eglibc as well) on some architectures
    1.83    (seen on powerpc, s390, s390x and x86_64).
    1.84  
    1.85 +Status:
    1.86 +  CURRENT
    1.87 +
    1.88  Fix:
    1.89    None so far. It would require some glibc hacking.
    1.90