Totally comment-out the multilib option: it's not implemented, and not really implementable with the current crosstool-NG scheme.

This commit is contained in:
Yann E. MORIN" 2007-08-14 19:32:22 +00:00
parent ecd5005989
commit ab0fc7eab4

View File

@ -51,22 +51,23 @@ config THREADS
default "linuxthreads" if THREADS_LINUXTHREADS
default "none" if THREADS_NONE
config TARGET_MULTILIB
bool
#config TARGET_MULTILIB
# bool
# prompt "Enable 'multilib' support (EXPERIMENTAL)"
default n
help
Enable the so-called 'multilib' support.
With the same toolchain, and on some architectures, you will be able to
build big and little endian binaries, soft- and hard-float, etc...
See the gcc configure manual at http://gcc.gnu.org/install/configure.html
to see what multilib your target supports.
It's preferable for now to build two (or more) toolchains, one for each
configuration you need to support (eg. one for thumb and one for ARM,
etc...). You can use the vendor string to diferentiate those toolchains.
# default n
# depends on EXPERIMENTAL
# help
# Enable the so-called 'multilib' support.
#
# With the same toolchain, and on some architectures, you will be able to
# build big and little endian binaries, soft- and hard-float, etc...
#
# See the gcc configure manual at http://gcc.gnu.org/install/configure.html
# to see what multilib your target supports.
#
# It's preferable for now to build two (or more) toolchains, one for each
# configuration you need to support (eg. one for thumb and one for ARM,
# etc...). You can use the vendor string to diferentiate those toolchains.
config TARGET_VENDOR
string