Remove CT_BROKEN.
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Oct 09 19:17:49 2008 +0000 (2008-10-09)
changeset 9140b164a321177
parent 913 194c03ec22c3
child 915 452aa1d7f9b1
Remove CT_BROKEN.
Only one component is actually BROKEN (libelf), make it depend on EXPERIMENTAL, but state BROKEN in the prompt.
ltrace (which depends on libelf) is now marked as EXPERIMENTAL, with the reference to the BROKEN libelf in the help entry.

/trunk/docs/overview.txt | 6 0 6 0 ------
/trunk/config/debug/ltrace.in | 7 4 3 0 ++++---
/trunk/config/global/ct-behave.in | 8 0 8 0 --------
/trunk/config/tools/libelf.in | 5 3 2 0 +++--
4 files changed, 7 insertions(+), 19 deletions(-)
config/debug/ltrace.in
config/global/ct-behave.in
config/tools/libelf.in
docs/overview.txt
     1.1 --- a/config/debug/ltrace.in	Thu Oct 09 19:13:37 2008 +0000
     1.2 +++ b/config/debug/ltrace.in	Thu Oct 09 19:17:49 2008 +0000
     1.3 @@ -2,14 +2,15 @@
     1.4  
     1.5  menuconfig LTRACE
     1.6      bool
     1.7 -    prompt "ltrace"
     1.8 +    prompt "ltrace (EXPERIMENTAL)"
     1.9      default n
    1.10 -    depends on BROKEN
    1.11 +    depends on EXPERIMENTAL
    1.12 +    depends on ! BARE_METAL
    1.13      select LIBELF
    1.14      help
    1.15        ltrace is currently BROKEN! It depends on libelf, and I don't
    1.16        know how to configure/compile that so that ltrace can successfully
    1.17 -      use it. I you manage to build ltrace (and libelf!), please be so
    1.18 +      use it. If you manage to build ltrace (and libelf!), please be so
    1.19        kind as to tell me! Thank you!
    1.20  
    1.21  if LTRACE
     2.1 --- a/config/global/ct-behave.in	Thu Oct 09 19:13:37 2008 +0000
     2.2 +++ b/config/global/ct-behave.in	Thu Oct 09 19:17:49 2008 +0000
     2.3 @@ -27,14 +27,6 @@
     2.4          - non-existant, in which case you could also try hacking it in and send me
     2.5            the result
     2.6  
     2.7 -config BROKEN
     2.8 -    bool
     2.9 -    prompt "Try broken stuff"
    2.10 -    default n
    2.11 -    depends on EXPERIMENTAL
    2.12 -    help
    2.13 -      Select this if you want to _debug_ broken stuff.
    2.14 -
    2.15  config DEBUG_CT
    2.16      bool
    2.17      prompt "Debug crosstool-NG"
     3.1 --- a/config/tools/libelf.in	Thu Oct 09 19:13:37 2008 +0000
     3.2 +++ b/config/tools/libelf.in	Thu Oct 09 19:17:49 2008 +0000
     3.3 @@ -2,9 +2,10 @@
     3.4  
     3.5  menuconfig LIBELF
     3.6      bool
     3.7 -    prompt "libelf"
     3.8 +    prompt "libelf (BROKEN)"
     3.9      default n
    3.10 -    depends on BROKEN
    3.11 +    depends on EXPERIMENTAL
    3.12 +    depends on ! BARE_METAL
    3.13      help
    3.14        libelf lets you read, modify or create ELF files in an
    3.15        architecture-independent way.
     4.1 --- a/docs/overview.txt	Thu Oct 09 19:13:37 2008 +0000
     4.2 +++ b/docs/overview.txt	Thu Oct 09 19:17:49 2008 +0000
     4.3 @@ -272,12 +272,6 @@
     4.4    feature present only in a recent version, or a new tool, you can find them
     4.5    hidden behind CT_EXPERIMENTAL.
     4.6  
     4.7 -CT_BROKEN:
     4.8 -  Show broken versions or tools. Some usefull tools are currently broken: they
     4.9 -  won't compile, run, or worse, cause defects when running. But if you are
    4.10 -  brave enough, you can try and debug them. They are hidden behind CT_BROKEN,
    4.11 -  which itself is hidden behind CT_EXPERIMENTAL.
    4.12 -
    4.13  Re-building an existing toolchain |
    4.14  ----------------------------------+
    4.15