Update the knwon issues with the broekn build of seemingly-native toolchains.
/trunk/docs/known-issues.txt | 59 59 0 0 ++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 59 insertions(+)
1 This files lists the known issues encountered while developping crosstool-NG,
2 but that could not be addressed before the release.
4 The file has one section for each known issue, each section containing four
5 sub-sections: Symptoms, Explanations, Fix, and Workaround.
7 Each section is separated from the others with a lines of at least 4 dashes.
9 The following dummy section explains it all.
11 --------------------------------
13 A one-liner of what you would observe.
16 An as much as possible in-depth explanations of the context, why it
17 happens, what has been investigated so far, and possible orientations
18 as how to try to solve this (eg. URLs, code snippets...).
21 What you have to do to fix it, if at all possible.
22 The fact that there is a fix, and yet this is a known issue means that
23 time to incorporate the fix in crosstool-NG was missing, or planned for
27 What you can do to fix it *temporarily*, if at all possible.
28 A workaround is not a real fix, as it can break other parts of
29 crosstool-NG, but at least makes you going in your particular case.
31 So now, on for the real issues...
33 --------------------------------
35 Seemingly native toolchains do not build.
38 Seemingly native toolchains are toolchains that target the same architecture
39 as the one it is built on, and on which it will run, but the machine tuple
40 may be different (eg i686 vs. i386, or x86_64-unknown-linux-gnu vs.
43 This seems to happen when building glibc-2.7 based toolchains only, for
46 Only the system part of the tuple (here, linux-gnu) needs to be the same to
49 If you really cross-compile (eg x86 -> x86_64, or the other way around),
50 the toolchain builds successfully.
56 If this happens for you, stick with glibc-2.6.1 for now.
59 --------------------------------