Boost logo

Boost-Build :

Subject: [Boost-build] Compiler warnings building Boost 1.37.0 for Macintosh OS X
From: Doug Hill (douglas.hill_at_[hidden])
Date: 2008-11-03 22:13:31


Hello there,

I just got the latest Boost release 1.37.0. I'm attempting to build
the libraries on a Machine with OS X 10.5.5 and XCode 3.1.1. I made
the following change:
- Commented out line 46 of /boost/math/tools/config.hpp
//# define BOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS

I then used the following command for the build:

sudo bjam --toolset=darwin --build-type=complete architecture=combined

I get a large number of warnings that I can't immediately tell if they
are significant or not:

=
=
=
========================================================================
./boost/spirit/home/support/iterators/multi_pass.hpp:151: warning:
‘boost
::spirit
::multi_pass
<
std
::pair
<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*>,
boost
::spirit
::multi_pass_policies
::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque> >::shared’ will
be initialized after
./boost/spirit/home/support/iterators/multi_pass.hpp:82: warning:
base
‘boost
::spirit
::multi_pass_policies
::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost
::spirit
::multi_pass_policies
::split_std_deque
>
::unique
<
std
::pair
<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*> >’
./boost/spirit/home/support/iterators/multi_pass.hpp:81: warning:
when initialized here
./boost/spirit/home/support/iterators/multi_pass.hpp: In copy
constructor ‘boost::spirit::multi_pass<T, Policies>::multi_pass(const
boost::spirit::multi_pass<T, Policies>&) [with T =
std
::pair
<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*>, Policies =
boost
::spirit
::multi_pass_policies
::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque>]’:
./boost/wave/cpplexer/cpp_lex_iterator.hpp:170: instantiated from
‘static boost::spirit::classic::tree_parse_info<LexIteratorT, typename
boost::wave::grammars::cpp_grammar_gen<LexIteratorT,
TokenContainerT>::node_factory_type, boost::spirit::classic::nil_t>
boost::wave::grammars::cpp_grammar_gen<LexIteratorT,
TokenContainerT>::parse_cpp_grammar(const LexIteratorT&, const
LexIteratorT&, const typename
LexIteratorT::token_type::position_type&, bool&, typename
LexIteratorT::token_type&, TokenContainerT&) [with LexIteratorT =
lexer_type, TokenContainerT = token_sequence_type]’
libs/wave/src/instantiate_cpp_grammar.cpp:45: instantiated from here

<many other snipped>

libs/python/src/converter/from_python.cpp: In function
‘boost::python::converter::rvalue_from_python_stage1_data
boost::python::converter::rvalue_from_python_stage1(PyObject*, const
boost::python::converter::registration&)’:
libs/python/src/converter/from_python.cpp:42: warning: ‘data
$construct’ may be used uninitialized in this function
libs/python/src/converter/from_python.cpp: In function ‘void*
boost::python::converter::rvalue_result_from_python(PyObject*,
boost::python::converter::rvalue_from_python_stage1_data&)’:
libs/python/src/converter/from_python.cpp:42: warning: ‘data
$construct’ may be used uninitialized in this function

<many others snipped>
=
=
=
========================================================================

Can anyone tell me if these warnings are something that I should be
concerned about?

I noticed that these warnings showed in the following thread:

http://archive.netbsd.se/?ml=boost-dev&a=2008-07&t=8069148

The thread mentions that a change may have been checked into the
Boost. Has this fix actually been integrated with the project and used
in this release?

If anyone has information about building the latest version of Boost
on Macintosh OS X, feel free to add to this thread.

Thanks.

Doug Hill
Oracle Corp.



Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk