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

1 files changed, 16 insertions, 15 deletions

diff --git a/config/toolchain.in b/config/toolchain.in
index 1e3f9491..6eb3539d 100644
--- a/config/toolchain.in
+++ b/config/toolchain.in
@@ -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