It is now official, the cause of the mysterious gcc 3.3.5 exception

handling failure is definately sjlj. Only enable it for the apparently
broken gcc 3.3.3 toolchain, which _does_ need it for exception handling
to work properly.

diff --git a/toolchain/gcc/Config.in b/toolchain/gcc/Config.in
index ce0a5ab50c4f4cc2220f5072d4570177f0ad2944..b19a36deca53978d96fd8d484f75e79eb5d46d9b 100644 (file)
--- a/toolchain/gcc/Config.in
+++ b/toolchain/gcc/Config.in
@@ -59,7 +59,8 @@ config BR2_GCC_VERSION
 
 config BR2_GCC_USE_SJLJ_EXCEPTIONS
        string
-       default "--enable-sjlj-exceptions"
+       default "--enable-sjlj-exceptions" if BR2_GCC_VERSION_3_3_3
+       default ""
        help
            Currently the unwind stuff seems to work for staticly linked apps
            but not dynamic.  So use setjmp/longjmp exceptions by default.