I don't have the exact failure message around anymore, but i will try again in some time. The error was, that somehow an operator<< was not found. Funny about that was, that it was the basic_ostream<wchar_t, ...>::operator<<(basic_ostream<wchar_t,...>, const std::string&) as far as i remember. I had a look at the preprocessor output, but didn't see anything suspicious there. (replace wchar_t with unsigned short in the case of /Zc:wchar_t- (off), which *was* the case). I also asked other colleges from my company (some c++ freaks ;o)), but they couldn't find anything either. Very weird. The very same thing happened when using the complete normal windows build with vc7.1 when using <native-wchar_t>off. Maybe someone can try this, to see if it has something to do with my machine (??). So i think this should be reproduceable even without stdcxx, and the normal windows STL implementation. My bjam flags where: bjam_flags="<runtime-link>dynamic" bjam_flags="${bjam_flags} <threading>multi" bjam_flags="${bjam_flags} <native-wchar_t>off" Cheers, Markus -----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jeff Garland Sent: Monday, September 25, 2006 3:18 PM To: boost@lists.boost.org Subject: Re: [boost] Windows and apache stdcxx Duft Markus wrote:

No, you misunderstood. I _did_ build with consistent wchar_t option (off in that case). But boost won't build the date time library without native wchar_t.

Well, that's fairly hard for me to imagine based on what is in the lib. The tests are a different story...many platforms have issues with correct support for wchar and hence fail a variety of date-time tests designed to exercise wchar support. Perhaps you need to post the failure details....or did I just miss them? The other thing I'll mention is that the platforms that use the Rogue Wave library, in general, haven't been the best for Boost support in general. So I wouldn't be surprised at all if there are plenty of boost compatibility issues with apache stdcxx. As an example, in date-time I had to add some code for facets that returned id's to make things work with the RW library: //time_facet.hpp #if defined (__SUNPRO_CC) && defined (_RWSTD_VER) std::locale::id& __get_id (void) const { return id; } #endif I don't know if this is still needed, but if it is you won't be getting it because the config macros won't select it. If you search the boost source on RWSTD you'll find other workarounds. Jeff _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost