- Boost-users - lists.boost.org

Cannot build debug-only with bjam?
by Jason Nye 13 Oct '08

13 Oct '08

Hi All, We are a Visual C++ shop (using vs2005 currently) and I would like to build boost with _SECURE_SCL=0 for release and _SECURE_SCL=1 for debug. I see there are only two options for the bjam --build-type command line option: minimal (which is release) and complete (which is debug+release). I would like to run bjam twice: once for release (with _SECURE_SCL=0) and once for debug (with _SECURE_SCL=1). Is there any way to do this? Note: I am fine with building both dynamics and statics for each configuration. I tried -build-type=debug but this doesn't work. Thanks, Jason.

2 1

try, catch with boost.asio acceptor
by Etienne Philip Pretorius 13 Oct '08

13 Oct '08

How would someone get this right? retry: try { boost::asio::local::stream_protocol::acceptor acceptor(m_service,endpoint); } catch (boost::system::system_error e) { if(e.code()==boost::system::errc::address_in_use) { std::remove("/tmp/someprogram.socket"); goto retry; } throw; } Etienne

1 0

new trunk build problem: tr1/.svn
by Robert Mecklenburg 13 Oct '08

13 Oct '08

To try and test the latest serialization changes, I've done a trunk update and now I'm getting a new build error: time make install ./tools/jam/src/bin.linuxx86/bjam --user-config=user-config.jam --prefix=/home/mecklen/work/boost-install --exec-prefix=/home/mecklen/work/boost-install --libdir=/home/mecklen/work/boost-install/lib --includedir=/home/mecklen/work/boost-install/include --without-python --without-mpi install warning: Graph library does not contain optional GraphML reader. note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the note: directories containing the Expat headers and libraries, respectively. Building Boost.Regex with the optional Unicode/ICU support disabled. Note: Please refer to the Boost.Regex documentation for more information Note: this is a strictly optional feature. error: Unable to find file or target named error: 'boost/tr1/tr1/.svn' error: referred from project at error: '.' The file it is complaining about exists and has mode bits 755. My configure line looks like: ./configure --prefix=/home/mecklen/work/boost-install --without-libraries=python --without-libraries=mpi --without-icu I'm not much of a bjam guy. This configure and build worked about 10 days ago. Any suggestions would be greatly appreciated. Thanks, -- Robert

5 7

Boost-1.36 with gcc stlport links against both libstlport_gcc.so and libstdc++.so.5
by Shetty, Diwakar 13 Oct '08

13 Oct '08

Thanks to Juergen Hunold's help, I was able to build Boost 1.36 on Linux-x86-32bit with gcc and stlport However, the boost lib seems to links against both "libstlport_gcc.so" and "libstdc++.so.5". See line 1 and line 3 below Should it not be linking only against "libstlport_gcc.so"?? ldd libboost_unit_test_framework-gcc32-mt-p-1_36.so Line 1: libstlport_gcc.so => /somepath/STLport-4.6.2/lib/libstlport_gcc.so (0xb74d9000) Line 2: librt.so.1 => /lib/tls/librt.so.1 (0xb74c5000) Line 3: libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xb7412000) Line 4: libm.so.6 => /lib/tls/libm.so.6 (0xb73f0000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb73e6000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb73d6000) libc.so.6 => /lib/tls/libc.so.6 (0xb729e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) Thanks, Diwakar (Extn. 64048) ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ==============================================================================

1 0

serialization 1.36.0 extended_type_info exit issue(s)
by Tim St. Clair 13 Oct '08

13 Oct '08

Folks, I'm running some serialization unit-tests which pass with flying colors under 1.35.0 and earlier, however they seg-fault on exit when run through 1.36.0. The error appears to deal with destruction of extended_type_info_typeid objects, and *only* manifests itself when I load an archive through a shared_ptr<T>. The load will appear to function properly, then on exit of the application, <<Death>>. This occurs even if I remove BOOST_CLASS_EXPORT && BOOST_CLASS_TYPE_INFO as the shared_ptr is to the derived element, and I'm not testing through a base. My lastest guess is that I may be missing some #define BOOST_SOME_MAGIC_NEW_OPTION //////////////////////////// pseduo code: //////////////////////////// BOOST_AUTO_TEST_CASE( MyTestClass_Serialization ) { boost::shared_ptr<MyTestClass> outtie ( new MyTestClass() ); boost::shared_ptr<MyTestClass> innie; std::ofstream os( "MyTestClass_Serialization.xml", std::ios_base::out ); my_pack< MyTestClass >( os, outtie ); os.close(); std::ifstream is( "MyTestClass_Serialization.xml", std::ios_base::in ); my_unpack< MyTestClass >( is, innie ); is.close(); BOOST_CHECK_NO_THROW(); } //////////////////////////// ddd output: //////////////////////////// *** No errors detected [New Thread 0xb73e26c0 (LWP 4715)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb73e26c0 (LWP 4715)] 0xb76bb56b in std::_Rb_tree_rebalance_for_erase () from /usr/lib/libstdc++.so.6 (gdb) bt #0 0xb76bb56b in std::_Rb_tree_rebalance_for_erase () from /usr/lib/libstdc++.so.6 #1 0xb7a38221 in std::_Rb_tree<boost::serialization::detail::extended_type_info_typeid_0 const*, boost::serialization::detail::extended_type_info_typeid_0 const*, std::_Identity<boost::serialization::detail::extended_type_info_typeid_0 const*>, boost::serialization::detail::type_compare, std::allocator<boost::serialization::detail::extended_type_info_typeid_0 const*> >::erase (this=0xb7a93c94, __position={_M_node = 0x810a3f8}) at /usr/include/c++/4.2/bits/stl_tree.h:1261 #2 0xb7a38270 in std::multiset<boost::serialization::detail::extended_type_info_typeid_0 const*, boost::serialization::detail::type_compare, std::allocator<boost::serialization::detail::extended_type_info_typeid_0 const*> >::erase (this=0xb7a93c94, __position={_M_node = 0x810a3f8}) at /usr/include/c++/4.2/bits/stl_multiset.h:346 #3 0xb7a37482 in boost::serialization::detail::extended_type_info_typeid_0::type_unregister (this=0x810749c) at /opt/tomodev/env/boost/libs/serialization/src/extended_type_info_typeid.cpp:93 #4 0x080b001a in ~extended_type_info_typeid (this=0x810749c) at /opt/tomodev/env/boost/boost/serialization/extended_type_info_typeid.hpp:80 #5 0x0809ebe2 in __tcf_49 () at /opt/tomodev/env/boost/boost/serialization/singleton.hpp:104 #6 0xb74f7084 in exit () from /lib/tls/i686/cmov/libc.so.6 #7 0xb74df458 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #8 0x0809e691 in _start () Cheers, Timothy St. Clair [timothysc(a)gmail.com]

9 37

Linker error with boost_1_36_0
by kumar bhargav 13 Oct '08

13 Oct '08

Hi, I built the thread library after downloading "boost_1_36_0.zip". After building the thread library from bjam, when I build the program in VS2008, I get following linker error:- Error 1 fatal error LNK1104: cannot open file 'libboost_thread-vc90-mt-gd-1_36.lib' What I see in the generated library folder is that boost_thread-vc90-mt-gd-1_36.lib is generated, but the linker is looking for 'libboost_thread-vc90-mt-gd-1_36.lib'. I have already done the required changes in the project properties mentioned at http://www.boost.org/doc/libs/1_36_0/more/getting_started/windows.html . Similar thing happening with Regex library also. The generated lib is boost_regex-vc90-gd-1_36.lib, but the linker is looking for libboost_regex-vc90-gd-1_36.lib. Is there any other settings change required or something else? Thanks, Bhargav.

5 9

[Function] Encapsulated inside a class, won't initialize.
by Ravey Alexandre 13 Oct '08

13 Oct '08

Hi there, I'm using boost::function defined private inside a class and then assign a function comming from another boost::function. But it don't work. A little code may help understand my pretty bad explanation. ####### class C { public: void Bind(boost::function<void()> f); private: boost::function<void()> func; }; void C::Bind(boost::function<void()> f) { func = f; //Compile, but raise an access violation. } ####### The problem seems obvious to me, func si not initialized correctly and swap() fail. But I can't figure out how to make this work. Thanks for your help.

2 1

Visual C++ 2003 and Boost 1.35
by Tomek Jerzykowski 13 Oct '08

13 Oct '08

Hello! I'm having a problem with using Boost 1.35 on Visual C++ 2003 SP1. Take a look at the following very simple program: ------------------------------------ #include "stdafx.h" #include <boost/interprocess/sync/interprocess_upgradable_mutex.hpp> int _tmain(int argc, _TCHAR* argv[]) { int i = 0; unsigned int j = 2; j < i; return 0; } ------------------------------------ It does nothing, just emits a compiler warning. Unfortunately, this warning is followed by lots of meaningless messages related to the included Boost header: ------------------------------------ BoostTest2.cpp c:\BoostTest2\BoostTest2.cpp(11) : warning C4018: '<' : signed/unsigned mismatch c:\Program Files\boost\boost_1_35_0\boost\interprocess\sync\interprocess_upgradable_mut ex.hpp(621) : see reference to class template instantiation 'boost::interprocess::upgradable_lock<M>' being compiled with [ M=boost::interprocess::interprocess_mutex ] c:\Program Files\boost\boost_1_35_0\boost\interprocess\sync\interprocess_upgradable_mut ex.hpp(621) : see reference to class template instantiation 'boost::interprocess::upgradable_lock<M>' being compiled with [ M=boost::interprocess::interprocess_mutex ] ------------------------------------ If I remove #include <boost..., the extra messages go away. It looks to me like compiler bug. The exe produced is probably ok, but the amount of spam in output window makes using Boost very cumbersome. Is there any way to make these messages go away?

6 9

boost::noncopyable doesn't work
by Maurer Philipp 13 Oct '08

13 Oct '08

Hello, I have a very special problem concerning boost::noncopyable under Windows in a shared library. A class deriving from boost::noncopyable becomes copyable. Strange ? Here is the example code. (Using Visual Studio 2005, no sp, Windows XP): 1) create one static lib with only TestClasses.hpp with the following content in it: #include <boost/noncopyable.hpp> class INonCopyNormalClass: boost::noncopyable { public: virtual INonCopyNormalClass* clone() = 0; }; 2) create one DLL (shared lib) with the following content: DLLMain.hpp: #include "../TestLib/TestClasses.hpp" # if defined(UNCOPYABLETESTDLL_EXPORTS) # define DLL_API __declspec(dllexport) # else # define DLL_API # endif class DLL_API AnotherNonNormalCopyClass: public INonCopyNormalClass { }; class YetAnotherNonNormalCopyClass: public AnotherNonNormalCopyClass { public: YetAnotherNonNormalCopyClass(); virtual INonCopyNormalClass* clone(); }; DLLMain.cpp: #include "DLLmain.hpp" YetAnotherNonNormalCopyClass::YetAnotherNonNormalCopyClass() { } INonCopyNormalClass* YetAnotherNonNormalCopyClass::clone() { return new YetAnotherNonNormalCopyClass(*this); } It is quite important that the DLL_API is defined properly !! This seems to be the reason, that the code above compile, links and runs. This should not be possible. The line return new YetAnotherNonNormalCopyClass(*this); should not work. If DLL_API is undefined or removed, you will get the correct error message and compilation fails ANY ideas ? SOMEONE ? Thanks and best, Philipp

1 0

[Boost.Asio] asio objects: initializing after construction
by Roman Shmelev 12 Oct '08

12 Oct '08

Hi! Lets assume I have some kind of map : map<int, boost::asio::ip::tcp::acceptor> my_acceptors; AND map<int, boost::asio::ip::tcp::socket> my_sockets; I want to extend the maps with new objects, so what is the right way to (?): my_acceptors[someport_int].initialize(_my_ioservice,_my_endpoint); my_acceptors[another_int].initialize(_my_ioservice); I use such code, but not sure it is right: { // initialize new acceptor ip::tcp::endpoint _my_endpoint(ip::tcp::v4(),port); ip::tcp::acceptor _acc(_my_ioservice,_my_endpoint); my_acceptors[someport_int] = _acc; // initialize new socket ip::tcp::socket _thesock(_my_ioservice); my_sockets[another_int] = _thesock; // asycc_accept my_acceptors[someport_int].async_accept(my_sockets[new_neighbour_id],boost::bind(do_AsyncAcceptHandler,this,new_neighbour_id)); } Thanks!

3 3