summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2011-04-07 17:21:15 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2011-04-07 17:21:15 (GMT)
commit43850b301c4e8b22d7303d60c101d359c6b44932 (patch)
tree948fe95e2b278c369c3236050ef0489b999ad053
parenta5785964b7b4813ebd538b8f21ed97d7025230d8 (diff)
docs: add a status for know issues
As time passes, a known issues can be no longer applicable (because the component has been fixed, or a workaround ahs been added in the crosstool-NG scripts/config...). Some may also be unconfirmed, with no way to easily trigger the error, or applies to old versions of components... Add a status for every known issues. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
-rw-r--r--docs/B - Known issues.txt32
1 files changed, 32 insertions, 0 deletions
diff --git a/docs/B - Known issues.txt b/docs/B - Known issues.txt
index 0bbe7a5..8ba4711 100644
--- a/docs/B - Known issues.txt
+++ b/docs/B - Known issues.txt
@@ -27,6 +27,17 @@ The following dummy section explains it all.
happens, what has been investigated so far, and possible orientations
as how to try to solve this (eg. URLs, code snippets...).
+ Status:
+ Tells about the status of the issue:
+ UNCONFIRMED : missing information, or unable, to reproduce, but there
+ is consensus that there is an issue somewhere...
+ CURRENT : the issue is applicable.
+ DEPRECATED : the issue used to apply in some cases, but has not been
+ confirmed or reported again lately.
+ CLOSED : the issue is no longer valid, and a fix has been added
+ either as a patch to this component, and/or as a
+ workaround in the scripts and/or the configuration.
+
Fix:
What you have to do to fix it, if at all possible.
The fact that there is a fix, and yet this is a known issue means that
@@ -53,6 +64,9 @@ Explanations:
A possible fix could probably set the environment variable CCACHE_CC to the
actual compiler used.
+Status:
+ CURRENT
+
Fix:
None known.
@@ -68,6 +82,9 @@ Explanations:
case-sensitive. You have to use so-called "managed" mounts. See:
http://cygwin.com/faq.html section 4, question 32.
+Status:
+ DEPRECATED
+
Fix:
Use "managed" mounts for the directories where you build *and* install your
toolchains.
@@ -83,6 +100,9 @@ Explanations:
With uClibc, it is possible to build a cross-ldd. Unfortunately, it is
not (currently) possible to build this cross-ldd under Cygwin.
+Status:
+ DEPRECATED
+
Fix:
None so far.
@@ -100,6 +120,9 @@ Explanations:
core gcc is not located in the same place it is located when building
with shared companion libraries.
+Status:
+ DEPRECATED
+
Fix:
None so far.
@@ -120,6 +143,9 @@ Explanations:
will not be built. There is nothing to be worry about (unless you do
want to build the Fortran frontend, of course).
+Status:
+ CURRENT
+
Fix:
None so far. It's a spurious error, so there will probably never be
a fix for this issue.
@@ -137,6 +163,9 @@ Explanations:
need sjlj. On some architectures, gcc is unable to determine whether
sjlj are needed or not.
+Status:
+ CURRENT
+
Fix:
None so far.
@@ -154,6 +183,9 @@ Explanations:
of glibc (and possibly eglibc as well) on some architectures
(seen on powerpc, s390, s390x and x86_64).
+Status:
+ CURRENT
+
Fix:
None so far. It would require some glibc hacking.