Boost logo

Boost :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-06-30 01:04:50


Jeff Garland wrote:

> date_time - test_greg_wstream - gcc-3.4.0-linux
> Compiler output:
>
> In file included from /boost/head-regression/boost/boost/config.hpp:44,
> from
> /boost/head-regression/boost/boost/date_time/locale_config.hpp:19,
> from
> /boost/head-regression/boost/boost/date_time/compiler_config.hpp:14,
> from
> /boost/head-regression/boost/boost/date_time/gregorian/gregorian.hpp:19,
> from
> ../libs/date_time/test/gregorian/testgreg_wstream.cpp:10:
> /boost/head-regression/boost/boost/config/stdlib/libstdcpp3.hpp:33:7:
> warning: #warning "Boost threading support turned on, you may need to link
> against -lpthread unless you define BOOST_DISABLE_THREADS when building."

Oops! Looking at the code in question:

#ifdef __GLIBCXX__ // gcc 3.4 and greater:
# ifdef _GLIBCXX_HAVE_GTHR_DEFAULT
      //
      // If the std lib has thread support turned on, then turn it on in Boost
      // as well. We do this because some gcc-3.4 std lib headers define
_REENT
      // while others do not...
      //
# define BOOST_HAS_THREADS
# warning "Boost threading support turned on, you may need to link against
-
# else
# define BOOST_DISABLE_THREADS
# endif
#endif

it seems the warning is *always* emitted, which is really bad, especially to
folks like me who compile things with -Werror :-(

May I suggest that at least this warning is not emitted when expicit
BOOST_DISABLE_THREADS or BOOST_HAS_THREADS were specified by the user, so
that I can have a way to kill the warning?

- Volodya


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk