- Boost-users - lists.boost.org

Building Boost 1.48 using Intel compiler
by Kim 19 Nov '11

19 Nov '11

First time posting to a mailing list, sorry if I've messed something up. I'm trying to build Boost 1.48 using Intel XE 12.1 and when running bjam it brings up "Windows can't open this file" for each file. I tried to adapt instructions from here: http://software.intel.com/en-us/articles/building-boost-with-intel-c/ I added the following to user-config.jam: using intel-win : 12.1 : "C:/Program Files (x86)/Intel/Composer XE/bin/ia32/icl.exe" : intel "C:/Program Files (x86)/Intel/Composer XE/bin/iclvars_ia32.bat" ; I tried building with the following command: C:\Users\blanked\Desktop\boost_1_48_0>bjam --toolset="intel" "-sINTEL_PATH=C :\Program Files (x86)\Intel\Composer XE\bin\ia32\" "-sINTEL_BASE_MSVC_TOOLSET=vc -10_0" "-sINTEL_VERSION=12.1" Building the Boost C++ Libraries. Performing configuration checks - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - iconv (libc) : no - iconv (separate) : no - icu : no - icu (lib64) : no - ../config//has_gcc_visibility builds : yes - ../config//has_long_double_support builds : yes 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. warning: No python installation configured and autoconfiguration note: failed. See http://www.boost.org/libs/python/doc/building.html note: for configuration instructions or pass --without-python to note: suppress this message and silently skip all Boost.Python targets Component configuration: - chrono : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - timer : building - wave : building ...patience... ...patience... ...patience... ...patience... ...found 6797 targets... ...updating 804 targets... compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\c_regex_traits.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\cpp_regex_traits.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\cregex.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\fileiter.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\icu.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\instances.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\posix_api.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\regex.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\regex_debug.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\regex_raw_buffer.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\regex_traits_defaults.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\static_mutex.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\w32_regex_traits.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\wc_regex_traits.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\wide_posix_api.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\winstances.obj compile-c-c++ bin.v2\libs\regex\build\intel-win\debug\link-static\threading-mult i\usinstances.obj intel-win.archive bin.v2\libs\regex\build\intel-win\debug\link-static\threading- multi\libboost_regex-iw-mt-gd-1_48.lib '/lib' is not recognized as an internal or external command, operable program or batch file. Thanks a lot for your time, guys.

5 8

has_binary_operator.hpp error
by Panagiotis Foteinos 19 Nov '11

19 Nov '11

Hello list. I just upgraded my system to the newest version of boost, i.e., 1.48.0. Boost compiled just fine. However, I recompile my applications (that link to boost) and I get the following error: ****************************************************************** usr/local/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN" ****************************************************************** Any suggestions? Regards, Panagiotis Foteinos

6 9

BOOST ASIO relation between I/O Service and a Socket and a Thread
by Gokulakannan Somasundaram 19 Nov '11

19 Nov '11

Hi, By going through ASIO, i find that the I/O Service gets run on a thread and the socket gets created with a I/O Service. So the data for the socket has to be always sent through the same thread. For trying take advantage of data localization, i am exploring whether it would be possible to have a thread per multi-core processor running the io_service::run() method. I am just wondering there is a way where in i can change the io_service associated with the socket. Can someone help me with that? Thanks, Gokul.

2 1

[Boost.Intrusive] Intrusive doubly linked list does not compile on xlC11.1
by Ioannis Papadopoulos 19 Nov '11

19 Nov '11

Hi, I'm trying to compile the intrusive doubly linked list example from http://www.boost.org/doc/libs/1_47_0/doc/html/intrusive/list.html#intrusive… using xlC11.1 on AIX/Power5+ and I am getting the following error: 1540-0216 (S) An expression of type "overloaded function: base_hook_traits<MyClass,boost::intrusive::list_node_traits<void *>,1,boost::intrusive::default_tag,1>::to_node_ptr" cannot be converted to type "boost::intrusive::list_node<void *> *(boost::intrusive::detail::base_hook_traits<MyClass,boost::intrusive::list_node_traits<void *>,1,boost::intrusive::default_tag,1>::*)(MyClass &)". "/scratch/ipapado/usr/include/boost/intrusive/detail/utilities.hpp", line 383.20: 1540-0424 (I) "boost::intrusive::detail::base_hook_traits<MyClass,boost::intrusive::list_node_traits<void *>,1,boost::intrusive::default_tag,1>::to_node_ptr(reference)" is declared on line 383 of "/scratch/ipapado/usr/include/boost/intrusive/detail/utilities.hpp". "/scratch/ipapado/usr/include/boost/intrusive/detail/utilities.hpp", line 386.26: 1540-0424 (I) "boost::intrusive::detail::base_hook_traits<MyClass,boost::intrusive::list_node_traits<void *>,1,boost::intrusive::default_tag,1>::to_node_ptr(const_reference)" is declared on line 386 of "/scratch/ipapado/usr/include/boost/intrusive/detail/utilities.hpp". "/scratch/ipapado/usr/include/boost/intrusive/detail/is_stateful_value_traits.hpp", line 38.1: 1540-0700 (I) The previous message was produced while processing "boost::intrusive::function_detector::DetectMember_InstantiationKey_to_node_ptr<struct boost::intrusive::detail::base_hook_traits<MyClass,boost::intrusive::list_node_traits<void *>,1,boost::intrusive::default_tag,1>,struct boost::intrusive::list_node<void *> *(boost::intrusive::detail::base_hook_traits<MyClass,boost::intrusive::list_node_traits<void *>,1,boost::intrusive::default_tag,1>::*)(class MyClass &),struct boost::intrusive::list...". Any known workarounds? Thanks

2 3

predicate for bundled properties in filtered graph
by giridhar 18 Nov '11

18 Nov '11

Hello All, I am getting little confused in defining the predicate for filtered graph since my properties are bundled. I need to compare two bundled property inside the predicate, I am not getting any idea of how to access this property there. Bundled property is declared as: struct Edgep { int edge_index; int edge_w; std::string edge_name; int capacity; int residual_capcity; int bandwidth_used; }; typedef subgraph< adjacency_list<vecS, vecS, undirectedS, Vertexp, property< edge_index_t, unsigned int, Edgep > > > Graph; I am creating the edge bundled property map as typedef bundle_property_map<Graph, Graph::edge_descriptor, Edgep, int> EM; I need to filter those edges whose bandwidth_used < residual_capacity. According to my understanding, I need to create a map to bandwidth_used and residual_capacity and pass this to predicate function. But can I define a predicate to take 2 different input maps or what is the better way to do this? I need some help at this part. Your suggestions would be of great help for me to proceed. -- Regards, Giridhar

2 1

[boost] Reminder! Boost.Local Review officially ends Saturday, Nov 19, 2011
by Jeffrey Lee Hellrung, Jr. 18 Nov '11

18 Nov '11

Just a friendly reminder that the ongoing Boost.Local review is officially set to end tomorrow (Saturday), Nov 19, 2011. Please let me know if you plan on reviewing the library but need more time, possibly into early next week, and I'll either formally extend the review period (subject to the Review Wizards' approval) or simply informally allow late submissions. Copied below is the original review announcement: ---------------- Hi all, It is time! The review of Lorenzo Caminiti's proposed Boost.Local library begins tomorrow, ***November 10, 2011***, and ends on ***November 19, 2011***. Boost.Local implements local functions, local blocks, and local exits for the C++ programming language. It allows one to define a function at any declarative scope, including function scope; bind variables from the enclosing scope; and pass this function to templated STL-style algorithms. Please see the Introduction of the documentation for a longer but still brief overview. -------- The code and documentation are available from the Boost sandbox ( https://svn.boost.org/svn/boost/sandbox/) https://svn.boost.org/svn/boost/sandbox/local/ [everything] https://svn.boost.org/svn/boost/sandbox/local/boost/ [code] https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/index.htm… -------- Please state clearly whether you think this library should be accepted as a Boost library. Other questions you may want to consider: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Please also consider the following issues and proposals specific to Boost.Local. Your opinion is welcome on any or all of these. - Boost.Local's local exits provide the same functionality (and then some) as Boost.ScopeExit. Does this duplication of functionality need to be dealt with, and if so, how? - Lorenzo is proposing to add boost::local::function:: overload to Boost.Function as boost::function::overload. See https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/boost/loc… - Lorenzo is proposing to add BOOST_IDENTITY_TYPE to boost/utility. See https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/BOOST_IDE… - Likewise, Lorenzo is proposing to add BOOST_IDENTITY_VALUE to boost/utility. See https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/BOOST_IDE… -------- Lastly, please note that Boost.Local has included a copy of the Variadic Macro Data (VMD) library in boost/detail/preprocessor/variadic_macro_data. Since then, VMD has been modified and integrated into Boost.Preprocessor. After the review has concluded, Lorenzo will remove this local copy of the VMD library and replace its usage within Boost.Local with the Boost.Preprocessor variadic extensions. -------- Thanks in advance to all who participate in the review discussion; I'm looking forward to it! - Jeffrey Hellrung (Review Manager) - Gregory Crosswhite (Review Assistant)

1 0

[boost] Boost.Local Review (Nov 10, 2011 to Nov 19, 2011)
by Jeffrey Lee Hellrung, Jr. 18 Nov '11

18 Nov '11

Hi all, It is time! The review of Lorenzo Caminiti's proposed Boost.Local library begins tomorrow, ***November 10, 2011***, and ends on ***November 19, 2011***. Boost.Local implements local functions, local blocks, and local exits for the C++ programming language. It allows one to define a function at any declarative scope, including function scope; bind variables from the enclosing scope; and pass this function to templated STL-style algorithms. Please see the Introduction of the documentation for a longer but still brief overview. -------- The code and documentation are available from the Boost sandbox ( https://svn.boost.org/svn/boost/sandbox/) https://svn.boost.org/svn/boost/sandbox/local/ [everything] https://svn.boost.org/svn/boost/sandbox/local/boost/ [code] https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/index.htm… -------- Please state clearly whether you think this library should be accepted as a Boost library. Other questions you may want to consider: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Please also consider the following issues and proposals specific to Boost.Local. Your opinion is welcome on any or all of these. - Boost.Local's local exits provide the same functionality (and then some) as Boost.ScopeExit. Does this duplication of functionality need to be dealt with, and if so, how? - Lorenzo is proposing to add boost::local::function:: overload to Boost.Function as boost::function::overload. See https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/boost/loc… - Lorenzo is proposing to add BOOST_IDENTITY_TYPE to boost/utility. See https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/BOOST_IDE… - Likewise, Lorenzo is proposing to add BOOST_IDENTITY_VALUE to boost/utility. See https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/BOOST_IDE… -------- Lastly, please note that Boost.Local has included a copy of the Variadic Macro Data (VMD) library in boost/detail/preprocessor/variadic_macro_data. Since then, VMD has been modified and integrated into Boost.Preprocessor. After the review has concluded, Lorenzo will remove this local copy of the VMD library and replace its usage within Boost.Local with the Boost.Preprocessor variadic extensions. -------- Thanks in advance to all who participate in the review discussion; I'm looking forward to it! - Jeffrey Hellrung (Review Manager) - Gregory Crosswhite (Review Assistant)

4 5

automatic conversion between boost::container::string and std::string
by Yi Ding 18 Nov '11

18 Nov '11

Hi, Thanks for the new containers library. There's a lot of useful stuff in there. I was wondering: is it possible to do automatic conversion between boost::container::string and std::string? A lot of libraries currently use std::string. Thanks, Yi

2 2

Re: [Boost-users] Building Boost 1.48 using Intel compiler
by Alex Perry 18 Nov '11

18 Nov '11

On Fri, 18 Nov 2011 15:40:23 +0100 Sergiu Dotenco <sergiu.dotenco(a)gmail.com> wrote:- > Am 17.11.2011 23:52, schrieb Kim: > > First time posting to a mailing list, sorry if I've messed something up. > > > > I'm trying to build Boost 1.48 using Intel XE 12.1 and when running > > bjam it brings up "Windows can't open this file" for each file. > > ...snip... > It works for me if I setup the environment variables first by executing > iclvars.bat. After that bjam toolset=intel can be used to compile Boost > without additional settings. > > Unfortunately, two problems remain. The first one is a compilation error > related to Boost.PropertyTree: > ...snip... > > The second one is related to Boost.Locale: bjam is unable to detect the > Windows version of ICU. This is due the fact, that bjam tries to locate > icudata.lib and icui18n.lib instead of icudt.lib and icuin.lib respectively, which > are the Windows names of the former libraries. > Have you built ICU from source? And set ICU_PATH in environment - I think I remember similar chasing of errors when building regex with the optional ICU support - problem was obvious in retrospect I'd installed ICU with prebuilt binaries and didn't have debug version available on machine. HTH Alex > > ------------------------------ > > Message: 6 > Date: Fri, 18 Nov 2011 06:48:12 -0800 > From: Steven Watanabe <watanabesj(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Trivial logging with boost.log > Message-ID: <4EC6702C.6080906(a)providere-consulting.com> > Content-Type: text/plain; charset=ISO-8859-1 > > AMDG > > On 11/18/2011 03:57 AM, Konstantin Ribel wrote: > > I finally managed to build the boost lib including boost.log. Now I am > > trying to get trivial logging to work, but I am experiencing some > > issues with it. Here is what I have done so far: > > > > <snip> > > > > When I hit the build button I get 10 errors. The build log is attached > > to this email. > > > > Does anybody know what to do in this situation? Do I have to define some > symbols? > > > > You need to link to the library. (-lboost_log) > > In Christ, > Steven Watanabe > > > ------------------------------ > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > End of Boost-users Digest, Vol 2909, Issue 4 > ********************************************

2 2

[MPI] request::test() crashes or returns garbage
by Patrik Jonsson 18 Nov '11

18 Nov '11

Hi, I'm having some problem with nonblocking p2p communications. This is with boost 1.47 and openmpi-1.5.3 compiled with icpc 12.0.3. Here's an example that exhibits the problem: #include <boost/mpi.hpp> #include <iostream> #include <vector> using namespace boost::mpi; using namespace std; int main(int argc, char* argv[]) { environment env(argc, argv); communicator world; vector<request> handshake_reqs_; for(int i=0; i<world.size(); ++i) { if(i!=world.rank()) { printf("Task %d posting recv from %d\n",world.rank(), i); handshake_reqs_.push_back(world.irecv(i, 13)); printf("Task %d sending to %d\n",world.rank(), i); world.isend(i, 13); } } for(int i=0; i<handshake_reqs_.size(); ++i) { boost::optional<status> s=handshake_reqs_[i].test(); if(s.is_initialized()) { const int source_task = s.get().source(); const int tag = s.get().tag(); printf("Task %d received message tag %d from task %d\n",world.rank(), tag, source_task);cout.flush(); } } } So, essentially, all tasks send a message with tag 13 to all other tasks, who have posted nonblocking receives for such a message. The output from this program is something like: [pjonsson@sunrise03 ~]$ mpirun -np 3 ./a.outTask 0 posting recv from 1 Task 0 sending to 1 Task 1 posting recv from 0 Task 1 sending to 0 Task 1 posting recv from 2 Task 0 posting recv from 2 Task 0 sending to 2 Task 1 sending to 2 Task 1 received message tag 0 from task 0 [sunrise03:06504] *** Process received signal *** [sunrise03:06504] Signal: Segmentation fault (11) [sunrise03:06504] Signal code: Address not mapped (1) [sunrise03:06504] Failing at address: 0x100000037 Task 2 posting recv from 0 Task 2 sending to 0 Task 2 posting recv from 1 Task 0 received message tag 1 from task 0 [sunrise03:06504] [ 0] /lib64/libpthread.so.0 [0x3d6c20eb10] [sunrise03:06504] [ 1] /n/home00/pjonsson/lib/libboost_mpi.so.1.47.0(_ZN5boost3mpi7request4testEv+0xc) [0x2b2fe9863a3c] [sunrise03:06504] [ 2] ./a.out(main+0x35d) [0x40ab37] [sunrise03:06504] [ 3] /lib64/libc.so.6(__libc_start_main+0xf4) [0x3d6b61d994] [sunrise03:06504] [ 4] ./a.out(_ZNSt8ios_base4InitD1Ev+0x41) [0x407039] [sunrise03:06504] *** End of error message *** [sunrise03:06503] *** Process received signal *** [sunrise03:06503] Signal: Segmentation fault (11) [sunrise03:06503] Signal code: Address not mapped (1) [sunrise03:06503] Failing at address: 0x100000037 [sunrise03:06503] [ 0] /lib64/libpthread.so.0 [0x3d6c20eb10] [sunrise03:06503] [ 1] /n/home00/pjonsson/lib/libboost_mpi.so.1.47.0(_ZN5boost3mpi7request4testEv+0xc) [0x2b44a0822a3c] [sunrise03:06503] [ 2] ./a.out(main+0x35d) [0x40ab37] [sunrise03:06503] [ 3] /lib64/libc.so.6(__libc_start_main+0xf4) [0x3d6b61d994] [sunrise03:06503] [ 4] ./a.out(_ZNSt8ios_base4InitD1Ev+0x41) [0x407039] [sunrise03:06503] *** End of error message *** [sunrise03:06505] *** Process received signal *** [sunrise03:06505] Signal: Segmentation fault (11) [sunrise03:06505] Signal code: Address not mapped (1) [sunrise03:06505] Failing at address: 0x100000037 Task 2 sending to 1 Task 2 received message tag 0 from task 0 [sunrise03:06505] [ 0] /lib64/libpthread.so.0 [0x3d6c20eb10] [sunrise03:06505] [ 1] /n/home00/pjonsson/lib/libboost_mpi.so.1.47.0(_ZN5boost3mpi7request4testEv+0xc) [0x2b7c652b4a3c] [sunrise03:06505] [ 2] ./a.out(main+0x35d) [0x40ab37] [sunrise03:06505] [ 3] /lib64/libc.so.6(__libc_start_main+0xf4) [0x3d6b61d994] [sunrise03:06505] [ 4] ./a.out(_ZNSt8ios_base4InitD1Ev+0x41) [0x407039] [sunrise03:06505] *** End of error message *** Sometimes it doesn't crash but just returns garbage for the source/tag, like all messages have source 0 and tag value that is the source task. Using test_some gives similar results. If I write the same using the C API, it works correctly: int main(int argc, char* argv[]) { MPI_Init(&argc, &argv); int rank, size; MPI_Comm_rank(MPI_COMM_WORLD, &rank); MPI_Comm_size(MPI_COMM_WORLD, &size); vector<MPI_Request> handshake_reqs_; for(int i=0; i<size; ++i) { if(i!=rank) { handshake_reqs_.push_back(MPI_Request()); MPI_Irecv(0,0, MPI_INT, i, 13, MPI_COMM_WORLD, &handshake_reqs_.back()); printf("Task %d sending to %d\n",rank, i); MPI_Request r; MPI_Isend(0,0, MPI_INT, i, 13, MPI_COMM_WORLD, &r); } } while(true) { for(int i=0; i<handshake_reqs_.size(); ++i) { int complete; MPI_Status s; MPI_Test(&handshake_reqs_[i], &complete, &s); if(complete) { const int source_task = s.MPI_SOURCE; const int tag = s.MPI_TAG; printf("Task %d received message tag %d from task %d\n",rank, tag, source_task);cout.flush(); MPI_Irecv(0,0, MPI_INT, i, 13, MPI_COMM_WORLD, &handshake_reqs_[i]); } } } } returns: [pjonsson@sunrise03 ~]$ mpirun -np 3 ./a.out Task 2 sending to 0 Task 2 sending to 1 Task 0 sending to 1 Task 0 sending to 2 Task 0 received message tag 13 from task 2 Task 2 received message tag 13 from task 0 Task 1 sending to 0 Task 0 received message tag 13 from task 1 Task 1 sending to 2 Task 2 received message tag 13 from task 1 Task 1 received message tag 13 from task 0 Task 1 received message tag 13 from task 2 Any ideas what might be going wrong? Regards, /Patrik

2 4