summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2009-04-20 21:30:25 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2009-04-20 21:30:25 (GMT)
commit683d2307779cbb9e7b641d1d6041cb2d0ba900a4 (patch)
treeca1cfd3da57b0078f97c101bd1f814e52c62294c
parent1805f4e62d15259fdef1e363896b810db07b0a46 (diff)
Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL.
-------- diffstat follows -------- /trunk/config/global/ct-behave.in | 22 13 9 0 +++++++++++++--------- /trunk/docs/overview.txt | 8 6 2 0 ++++++-- 2 files changed, 19 insertions(+), 11 deletions(-)
-rw-r--r--config/global/ct-behave.in22
-rw-r--r--docs/overview.txt8
2 files changed, 19 insertions, 11 deletions
diff --git a/config/global/ct-behave.in b/config/global/ct-behave.in
index 0e64de2..49f76ac 100644
--- a/config/global/ct-behave.in
+++ b/config/global/ct-behave.in
@@ -8,9 +8,13 @@ config OBSOLETE
default n
help
If you set this to Y, you will be able to select obsolete features.
-
- Such obsolete features are the use of old kernel headers, old
- gcc versions, etc...
+
+ Such obsolete features are the use of old kernel headers, old gcc
+ versions, etc... for which maintaining support in crosstool-NG
+ would be very costly.
+
+ It does not however mean that the specific feature or version has been
+ marked obsolete by the upstream team.
config EXPERIMENTAL
bool
@@ -19,7 +23,7 @@ config EXPERIMENTAL
help
If you set this to Y, then you will be able to try very experimental
features.
-
+
Experimental features can be one of:
- working, in which case you should tell me it is!
- buggy, in which case you could try patching and send me the result
@@ -32,7 +36,7 @@ config DEBUG_CT
prompt "Debug crosstool-NG"
default n
help
- Say 'y' here to get some debugging options
+ Say 'y' here to get some options regarding debugging crosstool-NG.
if DEBUG_CT
@@ -51,10 +55,10 @@ config DEBUG_CT_SAVE_STEPS
help
If you say 'y' here, then you will be able to restart crosstool-NG at
any step.
-
- It is not currently possible to restart at any of the debug facility.
+
+ It is not currently possible to restart at any of the debug facilities.
They are treated as a whole.
-
+
See docs/overview.txt for the list of steps.
config DEBUG_CT_SAVE_STEPS_GZIP
@@ -65,7 +69,7 @@ config DEBUG_CT_SAVE_STEPS_GZIP
help
If you are tight on space, then you can ask to gzip the saved states
tarballs. On the other hand, this takes some longer time...
-
+
To lose as less time as possible, the gzip process is done with a low
compression ratio (-3), which gives roughly 70% gain in size. Going
further doesn't gain much, and takes far more time (believe me, I've
diff --git a/docs/overview.txt b/docs/overview.txt
index d98e048..3fd7b6f 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -277,13 +277,17 @@ CT_OBSOLETE:
Show obsolete versions or tools. Most of the time, you don't want to base
your toolchain on too old a version (of gcc, for example). But at times, it
can come handy to use such an old version for regression tests. Those old
- versions are hidden behind CT_OBSOLETE.
+ versions are hidden behind CT_OBSOLETE. Those versions (or features) are so
+ marked because maintaining support for those in crosstool-NG would be too
+ costly, time-wise, and time is dear.
CT_EXPERIMENTAL:
Show experimental versions or tools. Again, you might not want to base your
toolchain on too recent tools (eg. gcc) for production. But if you need a
feature present only in a recent version, or a new tool, you can find them
- hidden behind CT_EXPERIMENTAL.
+ hidden behind CT_EXPERIMENTAL. Those versions (or features) did not (yet)
+ receive thorough testing in crosstool-NG, and/or are not mature enough to
+ be blindly trusted.
Re-building an existing toolchain |
----------------------------------+