Daniel James 1271821c44 Include <utility> for some versions of gcc's library. ...

Sometimes gcc's <cstddef> doesn't define the C++ macros, so check for it
and include <utility> in that case. Also remove a workaround from
container_fwd.hpp

Fixes #2924.

[SVN r52246]

2009-04-08 10:56:22 +00:00

..

dinkumware.hpp

Added BOOST_NO_STD_UNORDERED config macro.

2008-12-22 09:45:31 +00:00

libcomo.hpp

Added BOOST_NO_STD_UNORDERED config macro.

2008-12-22 09:45:31 +00:00

libstdcpp3.hpp

Include <utility> for some versions of gcc's library.

2009-04-08 10:56:22 +00:00

modena.hpp

Added BOOST_NO_STD_UNORDERED config macro.

2008-12-22 09:45:31 +00:00

msl.hpp

Added BOOST_NO_STD_UNORDERED config macro.

2008-12-22 09:45:31 +00:00

roguewave.hpp

Added BOOST_NO_STD_UNORDERED config macro.

2008-12-22 09:45:31 +00:00

sgi.hpp

Added BOOST_NO_STD_UNORDERED config macro.

2008-12-22 09:45:31 +00:00

stlport.hpp

Have config/select_stdlib_config.hpp and config/stdlib/stlport.hpp use <cstddef> instead of <utility> to determine which standard library is in use. For std lib implementations that rely on Boost components like TypeTraits, Bind, Function, or SmartPtr, this helps to avoid circular header dependency issues, since <cstddef> is much less likely to pull in Boost libraries than <utility>.

2009-04-01 14:42:11 +00:00

vacpp.hpp

Added BOOST_NO_STD_UNORDERED config macro.

2008-12-22 09:45:31 +00:00