April 2008 - Boost-users - lists.preview.boost.org

Linking boost libraries under visual c++ 2008
by Germán Diago 07 Apr '08

07 Apr '08

Hello. I compiled boost successfully for windows xp with visual c++ 9 toolchain. But when I try to link the regex example, visual studio looks for 'libboost-regex...' but the file produced for that file is 'boost-regex...' without the lib prefix. I don't know if this is a boost problem or a visual studio configuration problem. Anyway, do you know how can I solve this problem and link libraries with visual studio? I googled a lot but found no answer. Thanks in advance.

5 7

[boost][multiarray]Creating multi arrays on shared memory
by sankar lingam 07 Apr '08

07 Apr '08

I was working with boost multiarray and I found that multi arrays cannot be created in shared memory using boost interprocess..Will this be done in the future releases of boost?? Regards, sankar

2 3

Patch for boost-1_35 to remove compile warnings
by Lothar Werzinger 07 Apr '08

07 Apr '08

Attached is a patch for boost-1_35 to remove compile warnings in date_time/time.hpp Lothar

2 1

Re: [Boost-users] [smart_ptr] Sole ownership of shared_ptr?
by Richard L. Aurbach 07 Apr '08

07 Apr '08

On Apr 7, 2008, at 11:00 AM, Joseph Thomson wrote: > Actually, I think I have a better way which uses auto_ptr (or the > boost ptr > containers) as you suggested. It still isn't thread safe, but this > isn't of > immediate concern, and there are other methods for this anyway. > > Before, I was storing a map of shared_ptrs in the ObjectManager and a > weak_ptr reference in any ObjectHandles to check if the object is > still > valid. Instead: > > - A map of auto_ptrs (or a ptr_map of Objects) would be stored in the > ObjectManager. > - On its creation, Object would create and store a > shared_ptr<ObjectHandle>, > passing a raw pointer to it in the process (don't worry, this is still > safe). > - Any user wanting to get access to the Object would request an > ObjectHandle > from ObjectManager, which would in turn request a copy of Object's > shared_ptr<ObjectHandle>. > - On its destruction (by ObjectManager), Object would inform its > ObjectHandle of its destruction, and ObjectHandle would set an > internal flag > to indicate that it is expired. > - ObjectHandle would handle any requests from the user by first > checking the > expiry flag, and then forwarding the call to Object using its stored > raw > pointer. The expiry flag is set by the Object itself, so there is > no chance > of the pointer being invalid when called. > > Any advice/thoughts are appreciated. > > Cheers, > > Joe Joe, Suppose that: (a) ObjectManager uses shared_ptrs, not auto_ptrs, and (b) the base class of all Objects derives from boost::tr1::enable_shared_from_this. Then suppose the logic of ObjectHandle was something like: shared_ptr<Object> ptr = Object->shared_from_this(); if (ptr) { ptr->perform-requested-action(); } // shared ptr is reset when it goes out of scope Wouldn't this: >> preserve the single point of deletion (since the shared_ptr above is local). >> be thread-safe (because 'ptr' prevents the object from being deleted until the operation is complete. Or am I overlooking something really obvious in my (perhaps overly-)quick response? Cheers, Rick

1 0

Re: [Boost-users] [smart_ptr] Sole ownership of shared_ptr?
by Richard L. Aurbach 07 Apr '08

07 Apr '08

On Apr 6, 2008, at 5:48 PM, Joseph Thomson wrote: > Hi everyone, > > Over the past few days I have been trying to integrate Boost smart > pointers > into my system, which is basically a manager (ObjectManager) class > which > creates, destroys, and keeps track of instances of another class > (Object). > > The manager keeps a std::map of instances of type shared_ptr. The > manager > has a createObject() method which returns a shared_ptr instance to > the user, > thus the user becomes an owner of the object, alongside the > manager. My > problem arises because I want objects to _always_ be destroyed when > the > manager method destroyObject() is called. I realise that part of > the reason > to use smart pointers is to prevent data from being deleted while a > reference to it still exists, but I figure they are still worth > using just > for the safety aspect. I am also in the position of attempting to integrate shared_ptr into my application framework, so I am definitely a neophyte in this area. (So please take my comments with a grain of salt.) However, I have a couple of thoughts. (1) Your idea of storing both a weak_ptr and a true pointer to the object strikes me as dangerous. Any time you use the true pointer instead of locking the weak_ptr, you run the risk that the true pointer is not valid. This would, of course, invalidate one of the major points in using the shared_ptr/weak_ptr mechanism in the first place. I don't think that the overhead of converting the weak_ptr via lock() is sufficiently high to forego the advantages of the mechanism. But of course, only performance testing can verify that. [My own bias is to build a safe mechanism first, then only weaken it if performance measurements verify that this step is necessary.] (2) If you have, in fact, built a mechanism where you *know* that it is safe to use the true pointer instead of converting the weak_ptr, then I wonder if starting with a shared_ptr strategy is the best way to go in the first place. Since you only want one lock on the file (rather than shared ownership), wouldn't it be better to use auto_ptr? That pattern seems better suited to your overall approach -- if (and only if) you can be sure that a user will never use a deleted true pointer. Cheers, Rick Aurbach, Ph.D. President and Chief Engineer Aurbach & Associates, Inc. 8233 Tulane Avenue, Suite B St. Louis, MO 63132 www: http://www.aurbach.com/ eMail: support(a)aurbach.com [business] rick(a)aurbach.com [personal] Fax: 314/678-0869 Phone: 800/774-7239 314/726-1321 "If it ain't broke and you haven't fixed it recently, it probably needs to be rewritten." - Richard Aurbach (1948- ) "Beware of bugs in the above code; I have only proved it correct, not tried it." - Donald Knuth, computer scientist (1938- ) "If in the last few years you haven't discarded a major opinion or acquired a new one, check your pulse. You may be dead." - Gelett Burgess (1866-1951) "A life spent making mistakes is not only more honorable, but more useful than a life spent doing nothing." - George Bernard Shaw (1856-1950) "It doesn't matter how beautiful your theory is, it doesn't matter how smart you are. If it doesn't agree with experiment, it's wrong." - Richard Feynman (1918-1988) "The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." - Nathaniel Borenstein (1957-)

2 2

boost::bind triggers seg fault if compiled with gcc optimizations
by Sebastian Weber 07 Apr '08

07 Apr '08

Hello, I'm using boost::bind to bind some member function of class two arguments, making it a nullary function call. If I compile things with any optimizations, then the resulting code causes seg-faults. Without optimizations, everything is fine. Any ideas? Some possible workaround? BTW, boost::lambda::bind results in the same behavior. My versions: gcc 4.1.3 on ubuntu gutsy, boost 1.35.0 Greetings, Sebastian Weber

2 4

Solution: use string trim algorithms with Borland C++ 2006
by Markus Svilans 07 Apr '08

07 Apr '08

Hello, Apparently the string trimming algorithms do not work "out of the box" with Borland C++ 2006. There is a rather easy solution, which I have written about here: http://www.wrongbananas.net/cpp/boost_trim_borland.html Regards, Markus.

2 2

Building boost with VC8 & bjam
by Michael Bradley Jr 07 Apr '08

07 Apr '08

Hi, i have Microsoft VC 8.0 and the actual Microsoft Vista SDK install on my box. When i try to build boost with bjam with the following parameters: "bin\bjam.exe" -d 0 stage --stagedir=. --toolset=msvc link=static runtime-link=shared architecture=x86 release debug address-model=32 i do get vc9 used instead of the vc8. How can i "tell" bjam to generate the library using vc8 instead of vc9? Any help is welcome Regards Mike

3 2

fusion tuple to pod object
by Sebastian Weber 07 Apr '08

07 Apr '08

Hi there! The fusion library seems to be the choice for handling tuple-like data in C++. However, for some reasons I would like to be able to transform a fusion vector into a pod object. Something like: fusion::vector<int, double, float> myVec; SOME_MAGIC_ADAPTER_MACRO(myVec) The macro or whatever should then turn the vector into struct myVec_pod { int v1; double v2; float v3; }; or similar. Is this possible? Greetings, Sebastian Weber

3 3

[1.35.0] Boost.Serialization fails to build on Cygwin
by Václav Haisman 06 Apr '08

06 Apr '08

Hi, the non-wchar_t variant of Boost.Serialization fails to link on Cygwin because codecvt_null<wchar_t> tries to use std::codecvt<wchar_t> as base but std::codecvt<wchar_t> doesn't seem to be present in Cygwin's libstdc++. The output of the failing build is attached. -- wilx warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (don't panic: this is a strictly optional feature). ...patience... ...patience... ...found 4222 targets... ...updating 14 targets... gcc.link.dll bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/libboost_serialization-gcc34-mt-1_35.dll.a "g++" "-Wl,--out-implib,bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/libboost_serialization-gcc34-mt-1_35.dll.a" -o "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/cygboost_serialization-gcc34-mt-1_35.dll" -Wl,-h -Wl,cygboost_serialization-gcc34-mt-1_35.dll -shared -Wl,--start-group "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/extended_type_info.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/extended_type_info_no_rtti.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/extended_type_info_typeid.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/polymorphic_iarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/polymorphic_oarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/stl_port.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/text_iarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/text_oarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/void_cast.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_grammar.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_iarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_oarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_archive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_iarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_iserializer.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_oarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_oserializer.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_pointer_iserializer.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_pointer_oserializer.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_serializer_map.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_text_iprimitive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_text_oprimitive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_xml_archive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/binary_iarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/binary_oarchive.o" "bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o" -Wl,-Bstatic -Wl,-Bdynamic -Wl,--end-group -Wl,--strip-all -mthreads bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVN5boost7archive12codecvt_nullIwEE[vtable for boost::archive::codecvt_null<wchar_t>]+0x14): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_unshift(_mbstate_t&, char*, char*, char*&) const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVN5boost7archive12codecvt_nullIwEE[vtable for boost::archive::codecvt_null<wchar_t>]+0x20): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_always_noconv() const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVN5boost7archive12codecvt_nullIwEE[vtable for boost::archive::codecvt_null<wchar_t>]+0x24): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_length(_mbstate_t&, char const*, char const*, unsigned int) const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVSt7codecvtIwc10_mbstate_tE[vtable for std::codecvt<wchar_t, char, _mbstate_t>]+0x10): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_out(_mbstate_t&, wchar_t const*, wchar_t const*, wchar_t const*&, char*, char*, char*&) const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVSt7codecvtIwc10_mbstate_tE[vtable for std::codecvt<wchar_t, char, _mbstate_t>]+0x14): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_unshift(_mbstate_t&, char*, char*, char*&) const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVSt7codecvtIwc10_mbstate_tE[vtable for std::codecvt<wchar_t, char, _mbstate_t>]+0x18): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_in(_mbstate_t&, char const*, char const*, char const*&, wchar_t*, wchar_t*, wchar_t*&) const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVSt7codecvtIwc10_mbstate_tE[vtable for std::codecvt<wchar_t, char, _mbstate_t>]+0x1c): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_encoding() const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVSt7codecvtIwc10_mbstate_tE[vtable for std::codecvt<wchar_t, char, _mbstate_t>]+0x20): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_always_noconv() const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVSt7codecvtIwc10_mbstate_tE[vtable for std::codecvt<wchar_t, char, _mbstate_t>]+0x24): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_length(_mbstate_t&, char const*, char const*, unsigned int) const' bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVSt7codecvtIwc10_mbstate_tE[vtable for std::codecvt<wchar_t, char, _mbstate_t>]+0x28): undefined reference to `std::codecvt<wchar_t, char, _mbstate_t>::do_max_length() const' Creating library file: bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/libboost_serialization-gcc34-mt-1_35.dll.a collect2: ld returned 1 exit status ...failed gcc.link.dll bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/libboost_serialization-gcc34-mt-1_35.dll.a bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/cygboost_serialization-gcc34-mt-1_35.dll... ...removing bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/libboost_serialization-gcc34-mt-1_35.dll.a gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_text_wiprimitive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\basic_text_wiprimitive.o" "libs\serialization\src\basic_text_wiprimitive.cpp" libs\serialization\src\basic_text_wiprimitive.cpp:14:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_text_wiprimitive.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_text_woprimitive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\basic_text_woprimitive.o" "libs\serialization\src\basic_text_woprimitive.cpp" libs\serialization\src\basic_text_woprimitive.cpp:14:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/basic_text_woprimitive.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/binary_wiarchive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\binary_wiarchive.o" "libs\serialization\src\binary_wiarchive.cpp" libs\serialization\src\binary_wiarchive.cpp:14:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/binary_wiarchive.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/binary_woarchive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\binary_woarchive.o" "libs\serialization\src\binary_woarchive.cpp" libs\serialization\src\binary_woarchive.cpp:14:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/binary_woarchive.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/text_wiarchive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\text_wiarchive.o" "libs\serialization\src\text_wiarchive.cpp" libs\serialization\src\text_wiarchive.cpp:14:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/text_wiarchive.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/text_woarchive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\text_woarchive.o" "libs\serialization\src\text_woarchive.cpp" libs\serialization\src\text_woarchive.cpp:13:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/text_woarchive.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/utf8_codecvt_facet.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\utf8_codecvt_facet.o" "libs\serialization\src\utf8_codecvt_facet.cpp" libs\serialization\src\utf8_codecvt_facet.cpp:8:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/utf8_codecvt_facet.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_wgrammar.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\xml_wgrammar.o" "libs\serialization\src\xml_wgrammar.cpp" libs\serialization\src\xml_wgrammar.cpp:14:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_wgrammar.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_wiarchive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\xml_wiarchive.o" "libs\serialization\src\xml_wiarchive.cpp" libs\serialization\src\xml_wiarchive.cpp:13:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_wiarchive.o... gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_woarchive.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2\libs\serialization\build\gcc-3.4.4\release\threading-multi\xml_woarchive.o" "libs\serialization\src\xml_woarchive.cpp" libs\serialization\src\xml_woarchive.cpp:13:2: #error "wide char i/o not supported on this platform" ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi/xml_woarchive.o... ...skipped <pbin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi>libboost_wserialization-gcc34-mt-1_35.dll.a for lack of <pbin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi>basic_text_wiprimitive.o... ...skipped <pbin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi>cygboost_wserialization-gcc34-mt-1_35.dll for lack of <pbin.v2/libs/serialization/build/gcc-3.4.4/release/threading-multi>basic_text_wiprimitive.o... ...failed updating 12 targets... ...skipped 2 targets...

4 7