Its not good when make check just hangs and one cannot continue

to check and then (if one does not remember all FS tasks) one
starts to play around with configure flags and wasts a lot of
time.
For testing sllisttest one can always write
   make sllisttest
(at least I hope that is what EXTRA_PROGRAMS does)


[[Imported from SVN: r5715]]

dune/common/test/Makefile.am

@@ -2,7 +2,7 @@
 # $Id$
 
 TESTPROGS = parsetest test-stack arraylisttest smartpointertest \
-	sllisttest iteratorfacadetest iteratorfacadetest2 tuplestest fvectortest fmatrixtest \
+	iteratorfacadetest iteratorfacadetest2 tuplestest fvectortest fmatrixtest \
 	poolallocatortest settest gcdlcmtest streamtest \
 	bigunsignedinttest mpihelpertest singletontest mpicollcomm \
 	utilitytest lrutest \
@@ -28,7 +28,7 @@ compile_XFAIL:
 	  fi; \
 	done
 
-EXTRA_PROGRAMS = $(COMPILE_XFAIL_TESTS)
+EXTRA_PROGRAMS = $(COMPILE_XFAIL_TESTS) sllisttest
 
 TESTS = $(TESTPROGS) $(COMPILE_XFAIL)
 

dune/common/test/sllisttest.cc

@@ -4,6 +4,8 @@
 #include "config.h"
 #endif
 
+#warning sllist is known to fail with some optimization flags (FS493)
+
 #include <dune/common/sllist.hh>
 #include <dune/common/test/iteratortest.hh>
 #include <dune/common/poolallocator.hh>