1.1 --- a/config/toolchain.in	Tue Aug 07 19:40:38 2007 +0000
     1.2 +++ b/config/toolchain.in	Tue Aug 14 19:32:22 2007 +0000
     1.3 @@ -51,22 +51,23 @@
     1.4      default "linuxthreads"  if THREADS_LINUXTHREADS
     1.5      default "none"          if THREADS_NONE
     1.6  
     1.7 -config TARGET_MULTILIB
     1.8 -    bool
     1.9 +#config TARGET_MULTILIB
    1.10 +#    bool
    1.11  #    prompt "Enable 'multilib' support (EXPERIMENTAL)"
    1.12 -    default n
    1.13 -    help
    1.14 -      Enable the so-called 'multilib' support.
    1.15 -      
    1.16 -      With the same toolchain, and on some architectures, you will be able to
    1.17 -      build big and little endian binaries, soft- and hard-float, etc...
    1.18 -      
    1.19 -      See the gcc configure manual at http://gcc.gnu.org/install/configure.html
    1.20 -      to see what multilib your target supports.
    1.21 -      
    1.22 -      It's preferable for now to build two (or more) toolchains, one for each
    1.23 -      configuration you need to support (eg. one for thumb and one for ARM,
    1.24 -      etc...). You can use the vendor string to diferentiate those toolchains.
    1.25 +#    default n
    1.26 +#    depends on EXPERIMENTAL
    1.27 +#    help
    1.28 +#      Enable the so-called 'multilib' support.
    1.29 +#      
    1.30 +#      With the same toolchain, and on some architectures, you will be able to
    1.31 +#      build big and little endian binaries, soft- and hard-float, etc...
    1.32 +#      
    1.33 +#      See the gcc configure manual at http://gcc.gnu.org/install/configure.html
    1.34 +#      to see what multilib your target supports.
    1.35 +#      
    1.36 +#      It's preferable for now to build two (or more) toolchains, one for each
    1.37 +#      configuration you need to support (eg. one for thumb and one for ARM,
    1.38 +#      etc...). You can use the vendor string to diferentiate those toolchains.
    1.39  
    1.40  config TARGET_VENDOR
    1.41      string