Re: [Boost-users] Building Boost 1.59.0 on Solaris 11 with Solaris Studio 12.4

Subject: Re: [Boost-users] Building Boost 1.59.0 on Solaris 11 with Solaris Studio 12.4
From: Leo Carreon (lcarreon_at_[hidden])
Date: 2015-08-20 21:00:33

Hi John,

I applied your seven changes and three other changes namely:
1. A work-around for std::basic_ostream::sentry's explicit operator bool() 
in Boost.Log.
2. Removed usage of -xldscope=hidden in Boost.Lexical_Cast.
3. Removed usage of -xldscope=hidden in Boost.Variant.

After all the above changes, these are the remaining prevalent problems that 
I have observed:
1.
"libs/thread/src/pthread/thread.cpp", line 144: Error: Overloading ambiguity 
between "boost::call_once<void(*)()>(boost::once_flag&, void(*)())" and 
"boost::call_once<void(&)()>(boost::once_flag&, void(&)())".
2.
"./boost/thread/once.hpp", line 38: Error: Overloading ambiguity between 
"boost::call_once<void(*)()>(boost::once_flag&, void(*)())" and 
"boost::call_once<void(*)()&>(boost::once_flag&, void(*)()&)".
3.
"./boost/thread/pthread/once_atomic.hpp", line 168: Error: Overloading 
ambiguity between "boost::detail::invoke<void, void(*)(rlimit*), 
rlimit*>(void(*)(rlimit*)&, rlimit*)" and "boost::detail::invoke<void, 
void(*)(rlimit*), rlimit*&>(void(*)(rlimit*)&, rlimit*&)".
4.
"./boost/proto/detail/preprocessed/make_expr_.hpp", line 73: Error: type is 
not a member of 
boost::proto::transform<boost::proto::switch_<boost::phoenix::phoenix_generator, 
boost::proto::tag_of<boost::proto::_>()>, 
void>::result<boost::phoenix::phoenix_generator(boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, 
boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, 
boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>, 
boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, 
boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 2>)>.
5.
"libs/python/src/converter/builtin_converters.cpp", line 474: Error: 
Overloading ambiguity between "std::complex<double>::complex(double, 
double)" and "std::complex<double>::complex(complex double[2])".

Problems 1 and 2 appear to be similar but they have slightly different 
signatures.
Problems 2 and 3 appear to be related.

Regards,
Leo