id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
9160,libs/log/src/named_scope_format_parser.cpp fails to build under Solaris Studio 12.3,Brian Vandenberg <phantall+boost@…>,Andrey Semashev,"{{{
""/libs/log/src/named_scope_format_parser.cpp"", line 225: Error: Could not find a match for boost::log::v2_mt_posix::expressions::aux::parse_named_scope_format<boost::log::v2_mt_posix::expressions::aux::CharT>(const char*, const char*).
""/libs/log/src/named_scope_format_parser.cpp"", line 233: Error: Could not find a match for boost::log::v2_mt_posix::expressions::aux::parse_named_scope_format<boost::log::v2_mt_posix::expressions::aux::CharT>(const wchar_t*, const wchar_t*).
}}}

Unfortunately, this may be a [https://forums.oracle.com/thread/2571048?start=0&tstart=0 known issue] in Sun Studio that will be fixed in the next release.

I've been unable to find a writeup for the problem they discuss on that thread, but from the bits and pieces I've found it looks as though the compiler isn't completely following the standard on how to resolve some ambiguous symbol lookups.

It looks like the Oracle team is recommending people move away from using stlport 4 and instead use the Apache ""stdcxx"" library (see [https://forums.oracle.com/message/9936913?tstart=0 this thread]).

Since it's likely this isn't caused by boost itself, I'm more submitting this so this can be documented somewhere.",Bugs,closed,To Be Determined,log,Boost 1.54.0,Problem,fixed,,Brian Vandenberg <phantall+boost@…>