Introduce a new EXPERIMENTAL feature: BARE_METAL.
This should ultimately llow to build bare-metal compilers, for targets that have no kernel and no C library.
Move the C library build script to their own sub-directory; introduce an empty build script for bare-metal.
Move the compiler build script to its own sub-directory.
Move the kernel build script to its own sub-directory; introduce an empty build script for bare-metal.
Update the ARM target tuples to enable bare-metal targets.
Add two ARM bare-metal samples.
Add latest Linux kernel versions.

/trunk/scripts/build/kernel/none.sh | 77 6 71 0 +----
/trunk/scripts/build/cc/gcc.sh | 58 41 17 0 ++-
/trunk/scripts/build/libc/none.sh | 513 9 504 0 +-----------------------------
/trunk/scripts/crosstool.sh | 17 9 8 0 +
/trunk/scripts/functions | 6 4 2 0 +
/trunk/scripts/showSamples.sh | 6 3 3 0
/trunk/samples/arm-unknown-elf/crosstool.config | 225 225 0 0 +++++++++++++
/trunk/samples/arm-unknown-eabi/crosstool.config | 223 223 0 0 +++++++++++++
/trunk/config/kernel/linux_headers_install.in | 64 27 37 0 ++--
/trunk/config/kernel.in | 9 8 1 0 +
/trunk/config/toolchain.in | 1 1 0 0 +
/trunk/config/cc/gcc.in | 3 3 0 0 +
/trunk/config/debug/dmalloc.in | 1 1 0 0 +
/trunk/config/debug/gdb.in | 4 3 1 0 +
/trunk/config/debug/strace.in | 1 1 0 0 +
/trunk/config/debug/duma.in | 1 1 0 0 +
/trunk/config/cc.in | 8 8 0 0 +
/trunk/config/target.in | 13 13 0 0 +
/trunk/config/binutils.in | 1 1 0 0 +
/trunk/config/gmp_mpfr.in | 1 1 0 0 +
/trunk/config/libc.in | 17 11 6 0 +
/trunk/arch/arm/functions | 3 1 2 0 -
22 files changed, 600 insertions(+), 652 deletions(-)

# Options specific to crosstool-NG overall behavior

comment "crosstool-NG behavior"

config OBSOLETE

    bool

    prompt "Use obsolete features"

    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...

config EXPERIMENTAL

    bool

    prompt "Try features marked as EXPERIMENTAL"

    default n

    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

        - unfinished, in which case you could try hacking it and send me the result

        - non-existant, in which case you could also try hacking it in and send me

          the result

config BROKEN

    bool

    prompt "Try broken stuff"

    default n

    depends on EXPERIMENTAL

    help

      Select this if you want to _debug_ broken stuff.

config DEBUG_CT

    bool

    prompt "Debug crosstool-NG"

    default n

    help

      Say 'y' here to get some debugging options

if DEBUG_CT

config DEBUG_PAUSE_STEPS

    bool

    prompt "Pause between every steps"

    default n

    help

      Say 'y' if you intend to attend the build, and want to investigate

      the result of each steps before running the next one.

config DEBUG_CT_SAVE_STEPS

    bool

    prompt "Save intermediate steps"

    default n

    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.

      They are treated as a whole.

      See docs/overview.txt for the list of steps.

config DEBUG_CT_SAVE_STEPS_GZIP

    bool

    prompt "gzip saved states"

    default y

    depends on DEBUG_CT_SAVE_STEPS

    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

      got figures here! :-) ).

endif