- Boost-users - lists.boost.org

Re: [Boost-users] [multi_array] compiling and changing an example
by Steven Watanabe 29 Jan '10

29 Jan '10

AMDG sean farrow wrote: > I'm trying to use boost::multi_array, I've included boost/multi_array.hpp > in the file and have the following code: > > private: > > typedef boost::multi_array<double, 3> array_type; > > typedef array_type::index index; > > array_type test(boost::extents[3][4][2]); > > Commenting out the third line compiles fine, but leaving this in gives a > c2061 error. It seems there is an issue with boost::extents, which header > is this in? I don't have a using boost; earlier, should I have? I'm using > visual c+ 2008. > It compiles fine for me with the trunk: #include <boost/multi_array.hpp> int main() { typedef boost::multi_array<double, 3> array_type; typedef array_type::index index; array_type test(boost::extents[3][4][2]); } What version of boost are you using? What is your code exactly (with #includes)? What is the exact error message? In Christ, Steven Watanabe

1 0

The Boost difference b/w 32 and 64 bits
by JongKwan Kim 29 Jan '10

29 Jan '10

Hello, I am running my own C and C++ code using the Boost Library. First, I run the my code with Boost Library 1.36.0 on the 32 bits linux (Ubuntu) computer, so it is working well. However, I need to move the same code on the 64 bits linux (RedHat) computer. So, I am trying to run the code with Boost Library 1.41.0 on the 64 bits linux machine. At that time, the compiling is well, but when I run it, there is segmentation fault. I do not know if the problem is because of the difference between 32 bits and 64 bits or between 1.36.0 and 1.41.0 versions. Could you guys please let me know what is problem? When I type "make install" on the prompt window, I got messages like below.... ............................. /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libz.a(crc32.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_atan.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_cos.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_sin.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_exp.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_fmod.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_log.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_log10.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_pow.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_sqrt.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_round.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(m_isnan.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(m_finite.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_ceilf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_cosf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_floorf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_sinf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_expf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_fmodf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_logf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_log10f.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_powf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(w_sqrtf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_roundf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(m_isnanf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(m_finitef.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(k_standard.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_lib_version.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_matherr.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(e_exp.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(e_fmod.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(e_log.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(e_log10.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(e_pow.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `/usr/lib/libm.a(s_rint.o)' is incompatible with i386:x86-64 output ...............etc............. Thanks,

2 2

[Boost Circular Buffer] Warning C4099 when compiling with boost/circular_buffer.hpp
by Lloyd Zslnka 28 Jan '10

28 Jan '10

Boost Version: 1.35.0 Compiler: Visual Studio 2008 Version 9.0.30729.1 SP OS: Windows XP SP3 Hello, I'm compiling boost/circular_buffer.hpp with my project and am getting the following warning message: ...\boost\boost_1_35_0\boost\circular_buffer\base.hpp(180) : warning C4099: 'boost::cb_details::iterator' : type name first seen using 'class' now seen using 'struct' ...\boost\boost_1_35_0\boost\circular_buffer\details.hpp(187) : see declaration of 'boost::cb_details::iterator' ...\boost\boost_1_35_0\boost\circular_buffer\base.hpp(2477) : see reference to class template instantiation 'boost::circular_buffer<T,Alloc>' being compiled In looking at details.hpp, I see that iterator is declared as a class on line 187, but in base.hpp it is declared as a struct on line 180. Is this a mistake or am I missing something? Thanks, Lloyd --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

2 2

Boost, bjam, and symbolic links
by svdbg＠free.fr 28 Jan '10

28 Jan '10

Hello, I generated some Boost librairies with bjam, and I get many symbolic links. For date_time : libboost_date_time-gcc41-mt-1_39.a libboost_date_time-gcc41-mt-1_39.so -> libboost_date_time-gcc41-mt-1_39.so.1.39.0 libboost_date_time-gcc41-mt-1_39.so.1.39.0 libboost_date_time-gcc41-mt.a -> libboost_date_time-gcc41-mt-1_39.a libboost_date_time-gcc41-mt.so -> libboost_date_time-gcc41-mt-1_39.so.1.39.0 Why don't I just get the .a and .so ? Why these 3 symbolic links ? And why do the original files have a so complicated name for the .so, with the release version mentionned twice ? Isn't it possible to just have : libboost_date_time-gcc41-mt-1_39.a libboost_date_time-gcc41-mt-1_39.so Thanks for help. I don't know what to do of these symbolic links. Note : I am a newbie in Linux.

2 1

[Boost.Thread]
by Andrew Chinkoff 28 Jan '10

28 Jan '10

Hi. There is a test program I would to be explained to me: *** BEGIN OF TEST PROGRAM *** #include <stdio.h> #include <boost/thread.hpp> #define USE_SPINLOCKS //#define USE_MUTEXES boost::thread th1; boost::thread th2; boost::mutex mutex; int global_int = 0; bool IsNotEven(int code) { boost::mutex::scoped_lock locker(mutex); bool ret = (code & 1); return ret; } void thread_func() { for(int i = 0; i < 1000000; ++i) { #ifdef USE_MUTEXES if(IsNotEven(global_int)) // (1) #elif defined USE_SPINLOCKS if(__sync_fetch_and_and(&global_int, 1)) // (2) #else ERROR__WRONG_COMPILED; #endif global_int+=9; else global_int+=1; } } int main() { th1 = boost::thread(&thread_func); th2 = boost::thread(&thread_func); th1.join(); th2.join(); printf("global_int = %d\n", global_int); return 0; } *** END OF TEST PROGRAM *** Results of test program: 1) Test program compiled with USE_SPINLOCKS. Outputs are always: "global_int = 10" "global_int = 10" "global_int = 10" 2) Test program compiled with USE_MUTEXES. Outputs differ from each other: "global_int = 10000008" "global_int = 10000000" "global_int = 9763210" Could you explain me why outputs produced with USE_SPINLOCKS compilation differ from USE_MUTEXES ones? And what is the difference between (1) and (2) lines? Best, Andrew. P.S.: I use guest Ubuntu-8.04 installed on VirtualBox. Host OS = Vista.

2 1

Problem compiling boost libraries
by Daniel Veneros 28 Jan '10

28 Jan '10

Hi, I´m trying to compile a simple example in NetBeans 6.8 on Solaris platform, the code is: struct shm_remove { shm_remove() { shared_memory_object::remove("MySharedMemory"); } ~shm_remove(){ shared_memory_object::remove("MySharedMemory"); } } remover; //Create a shared memory object. shared_memory_object shm (create_only, "MySharedMemory", read_write); //Set size shm.truncate(1000); //Map the whole shared memory in this process mapped_region region(shm, read_write); //Write all the memory to 1 std::memset(region.get_address(), 1, region.get_size()); //Launch child process std::string s(argv[0]); s += " child "; if(0 != std::system(s.c_str())) return 1; That's it, no big deal, but when I try to build this I receive the error: Undefinded first referenced symbol in file shm_unlink, sched_yield, shm_open Anyone knows how can I fix this?? Thanks!!! Dann

4 4

Program options support for wide char
by Bo Jensen 28 Jan '10

28 Jan '10

Program options::options_description has a output operator for std::ostream, but none for std::wostream (if I am mistaken, please correct me). Shouldn't there be one ? I could surely need one :-) Regards Bo

2 1

[asio] Detecting tcp peer disconnection
by Igor R 28 Jan '10

28 Jan '10

Hello, This issue has previously been discussed in details, and IIRC, the conclusion was that the reliable method to detect peer disconnection is to try reading from the socket. Now I encountered strange situation: I connect tcp socket to some proprietry server, then pull out the ethernet cable from the server side. If async_read_some was in progress - nothing happens, no handler is called. If I start an additional async_read_some - nothing happens. I tried to set SO_KEEPALIVE option and waited - nothing happened. My machine runs WinXPSP3, so async_read_some is delegated to WSARecv(). I'd appreciate any idea on the subj. Thanks.

2 3

[boost-build] boost projects, like boost/python/boost_python
by Simon Pickles 28 Jan '10

28 Jan '10

Hello, Can anyone tell me how I find which jamfile is run when the line: <library>boost/python/boost_python is encountered by bjam? And are there equivalent 'shortcuts' to other boost libraries, particularly boost unit test framework? Many thanks Si

2 1

[String Algo] error in ireplace_first or ireplace_all with std::wstring under gcc 3.4.2 (MingW)
by Doug Swanson 28 Jan '10

28 Jan '10

I hope this is the appropriate place to post -- I apologize in advance if it is not! The following code compiles and runs without error under g++ in Windows, GCC 3.4.2 (MingW): <code> #include <cstdio> #include <string> #include <boost/algorithm/string.hpp> using namespace std; using namespace boost; int main( void ) { string test = "This is a test"; ireplace_first( test, "test", "success" ); printf( "%s\r\n", test.c_str() ); return 0; } </code> The output is correct: "This is a success". If I change the above code to use a std::wstring instead, it will compile, but it will crash on execution: <code> #include <cstdio> #include <string> #include <boost/algorithm/string.hpp> using namespace std; using namespace boost; int main( void ) { wstring test = L"This is a test"; ireplace_first( test, L"test", L"success" ); printf( "%ws\r\n", test.c_str() ); return 0; } </code> Setting a breakpoint on std::terminate() in gdb gives the following backtrace: Breakpoint 1, 0x00407ae6 in std::terminate() () (gdb) bt #0 0x00407ae6 in std::terminate() () #1 0x00404dc2 in __cxa_throw () #2 0x004021d2 in std::__throw_bad_cast() () #3 0x00434c69 in std::ctype<wchar_t> const& std::use_facet<std::ctype<wchar_t> >(std::locale const&) (__loc=@0x22fe8c) at C:/Applications/Dev-Cpp/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/locale_facets.tcc:112 #4 0x0043415c in wchar_t std::toupper<wchar_t>(wchar_t, std::locale const&) ( __c=84, __loc=@0x22fe8c) at C:/Applications/Dev-Cpp/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/locale_facets.h:4553 #5 0x0041648c in bool boost::algorithm::is_iequal::operator()<wchar_t, wchar_t> (wchar_t const&, wchar_t const&) const (this=0x22fe8c, Arg1=@0x3e3df4, Arg2=@0x43702e) at C:/Applications/Boost_new/boost/algorithm/string/compare.hpp:71 #6 0x004163fb in boost::iterator_range<__gnu_cxx::__normal_iterator<wchar_t*, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > > > boost::algorithm::detail::first_finderF<wchar_t const*, boost::algorithm::is_iequal>::operator()<__gnu_cxx::__normal_iterator<wchar_t*, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > > >(__gnu_cxx::__normal_iterator<wchar_t*, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > >, __gnu_cxx::__normal_iterator<wchar_t*, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > >) const (this=0x22fe80, Begin={_M_current = 0x3e3df4}, End={_M_current = 0x3e3e10}) at C:/Applications/Boost_new/boost/algorithm/string/detail/finder.hpp:76 #7 0x00413fe8 in void boost::algorithm::find_format<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, boost::algorithm::detail::first_finderF<wchar_t const*, boost::algorithm::is_iequal>, boost::algorithm::detail::const_formatF<boost::iterator_range<wchar_t const*> > >(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >&, boost::algorithm::detail::first_finderF<wchar_t const*, boost::algorithm::is_iequal>, boost::algorithm::detail::const_formatF<boost::iterator_range<wchar_t const*> >) ( Input=@0x22ff50, Finder=@0x22fe80, Formatter={m_Format = {m_Begin = 0x43701e, m_End = 0x43702e, singular = false}}) at C:/Applications/Boost_new/boost/algorithm/string/find_format.hpp:146 #8 0x004141b5 in void boost::algorithm::ireplace_first<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, wchar_t[5], wchar_t[8]> (std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >&, wchar_t[5] const&, wchar_t[8] const&, std::locale const&) (Input=@0x22ff50, Search=@0x43702e, Format=@0x43701e, Loc=@0x22ff40) at C:/Applications/Boost_new/boost/algorithm/string/replace.hpp:259 #9 0x004014e8 in main () at test.cpp:11 I am not competent enough with Boost to understand what the call stack is telling me, except that __throw_bad_cast( ) is the source of the crash. ireplace_all gives the same behavior as ireplace_first above. Furthermore, the problem does not arise if I use replace_first or replace_all instead of ireplace_first or ireplace_all. It compiles and runs correctly. Finally, the problem does not arise if I compile using MSVC 2008. It compiles and runs correctly. Does this indicate a problem with gcc (MingW) unicode support? Is there an easy way to circumvent it? Thank you very much for any suggestions!

2 1