From 172f4c76b3476f95e9ae1478da97d245acf7b0b0 Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Sun, 1 May 2005 00:34:11 +0000 Subject: 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. --- toolchain/gcc/Config.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'toolchain/gcc') diff --git a/toolchain/gcc/Config.in b/toolchain/gcc/Config.in index ce0a5ab50..b19a36dec 100644 --- 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. -- cgit v1.2.3