Building multi-lib aware toolchains is not supported, and won'yt be before a loooong time. Remove the associated config entry.
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sat May 24 22:10:51 2008 +0000 (2008-05-24)
changeset 530010a5f732a6f
parent 528 38e382b3829e
child 531 77df8ff1f383
Building multi-lib aware toolchains is not supported, and won'yt be before a loooong time. Remove the associated config entry.

/trunk/config/toolchain.in | 18 0 18 0 ------------------
1 file changed, 18 deletions(-)
config/toolchain.in
     1.1 --- a/config/toolchain.in	Thu May 22 22:38:37 2008 +0000
     1.2 +++ b/config/toolchain.in	Sat May 24 22:10:51 2008 +0000
     1.3 @@ -51,24 +51,6 @@
     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 -#    prompt "Enable 'multilib' support (EXPERIMENTAL)"
    1.10 -#    default n
    1.11 -#    depends on EXPERIMENTAL
    1.12 -#    help
    1.13 -#      Enable the so-called 'multilib' support.
    1.14 -#      
    1.15 -#      With the same toolchain, and on some architectures, you will be able to
    1.16 -#      build big and little endian binaries, soft- and hard-float, etc...
    1.17 -#      
    1.18 -#      See the gcc configure manual at http://gcc.gnu.org/install/configure.html
    1.19 -#      to see what multilib your target supports.
    1.20 -#      
    1.21 -#      It's preferable for now to build two (or more) toolchains, one for each
    1.22 -#      configuration you need to support (eg. one for thumb and one for ARM,
    1.23 -#      etc...). You can use the vendor string to diferentiate those toolchains.
    1.24 -
    1.25  config TARGET_VENDOR
    1.26      string
    1.27      prompt "Vendor string"