when using -O2 instead of -Os, get rid of the two optimizations that are causing...

[openwrt.git] / toolchain / Config.in

diff --git a/toolchain/Config.in b/toolchain/Config.in
index 0f67fc0..cf08ae9 100644 (file)
--- a/toolchain/Config.in
+++ b/toolchain/Config.in
@@ -13,7 +13,7 @@ menuconfig TOOLCHAINOPTS
 menuconfig EXTRA_TARGET_ARCH
        bool
        prompt "Enable an extra toolchain target architecture" if TOOLCHAINOPTS
-       default y       if TARGET_ps3
+       default y       if powerpc64
        default n
        help
          Some builds may require a 'biarch' toolchain. This option
@@ -23,7 +23,7 @@ menuconfig EXTRA_TARGET_ARCH
 
        config EXTRA_TARGET_ARCH_NAME
                string
-               default "powerpc64"     if TARGET_ps3
+               default "powerpc64"     if powerpc64
                prompt "Extra architecture name" if EXTRA_TARGET_ARCH
                help
                  Specify the cpu name (eg powerpc64 or x86_64) of the
@@ -31,7 +31,7 @@ menuconfig EXTRA_TARGET_ARCH
 
        config EXTRA_TARGET_ARCH_OPTS
                string
-               default "-m64"          if TARGET_ps3
+               default "-m64"          if powerpc64
                prompt "Extra architecture compiler options" if EXTRA_TARGET_ARCH
                help
                  If you're specifying an addition target architecture,
@@ -42,24 +42,32 @@ menuconfig EXTRA_TARGET_ARCH
                  both powerpc and powerpc64 binaries, you'll need to
                  specify -m64 here.
 
+comment "Binary tools"
+       depends TOOLCHAINOPTS
+
 source "toolchain/binutils/Config.in"
+
+comment "Compiler"
+       depends TOOLCHAINOPTS
+
 source "toolchain/gcc/Config.in"
 
+comment "C Library"
+       depends TOOLCHAINOPTS
+
 choice
-       prompt "LIBC implementation" if TOOLCHAINOPTS
+       prompt "C Library implementation" if TOOLCHAINOPTS
        default USE_UCLIBC
        help
-         Select the LIBC implementation.
+         Select the C library implementation.
 
        config USE_EGLIBC
                bool "Use eglibc"
                depends !avr32
-               select NO_STRIP
        
        config USE_GLIBC
                bool "Use glibc"
                depends !avr32
-               select NO_STRIP
        
        config USE_UCLIBC
                bool "Use uClibc"
@@ -70,6 +78,9 @@ source "toolchain/eglibc/Config.in"
 source "toolchain/glibc/Config.in"
 source "toolchain/uClibc/Config.in"
 
+comment "Debuggers"
+       depends TOOLCHAINOPTS
+
 config GDB
        bool
        prompt "Build gdb" if TOOLCHAINOPTS
@@ -77,39 +88,13 @@ config GDB
        help
                Enable if you want to build the gdb
 
-config LARGEFILE
-       bool
-       prompt "Enable large file (files > 2 GB) support?" if TOOLCHAINOPTS
-       default y
-       help
-               Enable large file (files > 2 GB) support
-
-config SHADOW_PASSWORDS
+config INSIGHT
        bool
-       prompt "Enable shadow password support?" if TOOLCHAINOPTS
-       default y
-       help
-               Enable shadow password support.
-
-config SOFT_FLOAT
-       bool
-       prompt "Use software floating point by default" if TOOLCHAINOPTS
-       default y
-       depends on (arm || armeb || powerpc) && !HAS_FPU
-       help
-         If your target CPU does not have a Floating Point Unit (FPU) or a
-         kernel FPU emulator, but you still wish to support floating point
-         functions, then everything will need to be compiled with soft floating
-         point support (-msoft-float).
-
-         Most people will answer N.
-
-config TARGET_OPTIMIZATION
-       string
-       prompt "Target Optimizations" if TOOLCHAINOPTS
-       default DEFAULT_TARGET_OPTIMIZATION
+       prompt "Build insight-gdb" if TOOLCHAINOPTS
+       select GDB
+       default n
        help
-         Optimizations to use when building for the target host.
+               Enable if you want to build insight-gdb
 
 config USE_UCLIBC
        bool