organicmaps/boost
13
Fork 0
mirror of https://github.com/boostorg/boost.git synced 2025-04-08 14:44:02 +00:00
Code Issues 1 Projects Releases Wiki Activity Actions

Unordered: Mark up new container forwarding failures. Refs #6323.

Browse source 
A lot of new failures because container forwading is now disabled for a
lot of cases where it doesn't have to be.

[SVN r76444]
This commit is contained in:
Daniel James 2012-01-13 08:55:28 +00:00
parent f6df19d304
commit e0daf5afe8
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
status/explicit-failures-markup.xml
View file

@ -1401,6 +1401,29 @@
</note>
</mark-expected-failures>
<mark-expected-failures>
<test name="correctly_disable"/>
<toolset name="gcc-4.2*"/>
<toolset name="gcc-4.3*"/>
<toolset name="gcc-4.4*"/>
<toolset name="gcc-4.5*"/>
<toolset name="gcc-4.6*"/>
<toolset name="gcc-4.7*"/>
<toolset name="gcc-mingw-*"/>
<toolset name="darwin-4.2"/>
<toolset name="clang-darwin-trunk"/>
<toolset name="clang-darwin-normal"/>
<toolset name="clang-darwin-linux-2.9"/>
<toolset name="intel-linux-*"/>
<note author="Daniel James">
GCC's libstdc++ has a versioned namespace feature which breaks
container forwarding. I don't know how to detect it so I'm just
always disabling it, which means that a lot of setups which
means that it's disabled for a lot of setups where it could
work - which is what these failures represent.
</note>
</mark-expected-failures>
<mark-expected-failures>
<test name="container_fwd"/>
<test name="container_fwd_debug"/>