From 9063b1d1fdb8bba21473f748200e45915311b56a Mon Sep 17 00:00:00 2001
From: Daniel James <daniel@calamity.org.uk>
Date: Sat, 31 May 2014 18:22:42 +0100
Subject: [PATCH] Don't run 'correctly_disable' tests by default.

---
 test/container_fwd/Jamfile | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/test/container_fwd/Jamfile b/test/container_fwd/Jamfile
index ab55bc2..1c0906e 100644
--- a/test/container_fwd/Jamfile
+++ b/test/container_fwd/Jamfile
@@ -21,9 +21,19 @@ run container_fwd_test.cpp : :
     : <define>_STLP_DEBUG <define>_GLIBCXX_DEBUG
     : container_fwd_debug ;
 
+# The 'correctly_disable' tests fail if forward declaring standard types
+# could work, but is currently not being done. Unfortunately, this if often
+# the case - but we can't detect it, so the tests fail and there's not much
+# we can do. There are also problems because some compilers don't support
+# the debug version of their libraries. So I felt it was best to stop these
+# tests from running in a normal test run..
+
 compile-fail correctly_disable_fail.cpp
     : <warnings-as-errors>off
     : correctly_disable ;
 compile-fail correctly_disable_fail.cpp
     : <warnings-as-errors>off <define>_STLP_DEBUG <define>_GLIBCXX_DEBUG
     : correctly_disable_debug ;
+
+explicit correctly_disable ;
+explicit correctly_disable_debug ;