April 2014 - Boost - lists.preview.boost.org

Boost Parallel Graph Library: remove_vertex gives unexpected results
by Alok Kumbhare 09 Apr '14

09 Apr '14

Hi All, i need some help with parallel boost graph library. Sorry if this is not the right list to post. Posting here since it looks like it might be a but. In particular, i am trying to modify the structure of the graph (distributed adjacency list) after it is loaded. The code snippet is at http://pastebin.com/erizQ0Sf. The problem is that clear_vertex(v,g) and remove_vertex(v,g) does not seem to operate on the same vertex in the graph. Here is a sample graph in metis format: http://pastebin.com/qxy2w6aw (I use the default vertex distribution for this example) The graph_viz output is available here for different scenarios: https://onedrive.live.com/redir?resid=C3CDB6EFBD31B4A8!20818&authkey=!AJqEF…<https://onedrive.live.com/redir?resid=C3CDB6EFBD31B4A8!20818&authkey=!AJqEF…> As you can see in the above figure: The first image is the original graph split into two partitions (mpirun -np 2 ./test) The second image is after clear_vertex is called for one of the vertices. Notice vertex "0". All the edges are removed as expected. The third image is after remove_vertex is called (which is called after clear_vertex, as mentioned in the documentation here: http://www.boost.org/doc/libs/1_55_0/libs/graph_parallel/doc/html/distribut…). Notice here that the vertex "2" is removed instead of vertex "0" even when using the same vertex descriptor for both calls. One thing i noted is that the remove_vertex seems to remove the "last" vertex in that partition irrespective of the input. e.g. if i use v = vertex(1,g) in the above code, i still see that the vertex "2" is removed and the edges rearranged for that. Is this a bug or am i doing something wrong. Your help will be greatly appreciated. Thanks, Alok Kumbhare

1 1

[wrapper]
by Alexandra 09 Apr '14

09 Apr '14

HI, I have Ubuntu 13.10 with a Processor Intel Pentium CPU P6100 2.00GHz x 2. I download the boost library for linux, extract and install boostrap.sh. When I try to do ./b2 on terminal, the result is this: MPI auto-detection failed: unknown wrapper compiler mpic++ Please report this error to the Boost mailing list: http://www.boost.org You will need to manually configure MPI support. /home/alexandra/boost_1_55_0/tools/build/v2/tools/gcc.jam:148: in gcc.init from module gcc error: toolset gcc initialization: error: no command provided, default command 'g++' not found error: initialized from project-config.jam:12 /home/alexandra/boost_1_55_0/tools/build/v2/build/toolset.jam:41: in toolset.using from module toolset /home/alexandra/boost_1_55_0/tools/build/v2/build/project.jam:1007: in using from module project-rules project-config.jam:12: in modules.load from module project-config /home/alexandra/boost_1_55_0/tools/build/v2/build-system.jam:249: in load-config from module build-system /home/alexandra/boost_1_55_0/tools/build/v2/build-system.jam:412: in load-configuration-files from module build-system /home/alexandra/boost_1_55_0/tools/build/v2/build-system.jam:524: in load from module build-system /home/alexandra/boost_1_55_0/tools/build/v2/kernel/modules.jam:289: in import from module modules /home/alexandra/boost_1_55_0/tools/build/v2/kernel/bootstrap.jam:139: in boost-build from module /home/alexandra/boost_1_55_0/boost-build.jam:17: in module scope from module On user-config.jam i wrote # ------------------ # MPI configuration. # ------------------ using mpi ; in the final line. You can help me? THank you Alexandra

5 7

[filesystem] path noncopyable error with boost 1.55.0 and g++ 4.5.1
by Richard Hadsell 09 Apr '14

09 Apr '14

I am trying to upgrade from Boost 1.52 to 1.55. Everything is fine with Clang 3.3, but I get this error with G++ 4.5.1: In file included from /netDISKS/master/netmt/LINUX_INTF14/cgi/boost/1.55.0/Include/libboost/boost/system/error_code.hpp:18:0, from /netDISKS/master/netmt/LINUX_INTF14/cgi/boost/1.55.0/Include/libboost/boost/filesystem/path_traits.hpp:23, from /netDISKS/master/netmt/LINUX_INTF14/cgi/boost/1.55.0/Include/libboost/boost/filesystem/path.hpp:25, from bssConfig.h:24, from bssConfig.cc:13: /netDISKS/master/netmt/LINUX_INTF14/cgi/boost/1.55.0/Include/libboost/boost/noncopyable.hpp:27:37: error: 'boost::noncopyable_::noncopyable::noncopyable()' declared with non-public access cannot be defaulted in the class body /netDISKS/master/netmt/LINUX_INTF14/cgi/boost/1.55.0/Include/libboost/boost/noncopyable.hpp:28:22: error: 'boost::noncopyable_::noncopyable::~noncopyable()' declared with non-public access cannot be defaulted in the class body The OS is Linux Fedora 14. The compiler is gcc version 4.5.1 20100924 (Red Hat 4.5.1-4). I am compiling with these flags: -march=core2 -msse4.1 -m64 -mpc64 -std=c++0x -pedantic-errors -mieee-fp -fPIC -pthread -O2 -g -fno-strict-aliasing -fno-tree-ccp -- Dick Hadsell 203-992-6320 Fax: 203-992-6001 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studioshttp://www.blueskystudios.com 1 American Lane, Greenwich, CT 06831-2560 Follow Blue Sky Studios on Facebook <http://www.facebook.com/BlueSkyStudios> and Twitter <http://twitter.com/#%21/blueskystudios>

3 4

Reboot all the CREST server machines to apply the updated openssl lib
by Kim, DongInn 09 Apr '14

09 Apr '14

Dear All, I am advised to reboot all our CREST servers to fully apply the updated OpeeSSL library. The new OpenSSL library was patched to RHEL 6 (RedHat Enterprise Linux 6) packages yesterday and they were installed on all the CREST server machines at around 10am Apr 8, 2014. (Note: all the CREST server machines are setup with RHEL6). The OpenSSL bug is serious and we needed to take immediate actions. http://heartbleed.com Even though our server seem to be safe with the new OpenSSL library now, I would like to make sure that there is no any leaking spots in our server machines by refreshing all the systems with the new OpenSSL library. I would like to setup a schedule to reboot all the CREST server machines at 9am tomorrow (Apr 10, 2014). Date: April 10, 2014 Time: 6:00am-7:00am Pacific US time 7:00am-8:00am Mountain US time 8:00am-9:00am Central US time 9:00am-10:00am Eastern US time 1:00pm-2:00pm GMT Please let me know if you have any questions or concerns about rebooting our servers. Regards, -- - DongInn

1 0

Compile error on function.mem_fun_cxx98 regression test
by Chris Cooper 09 Apr '14

09 Apr '14

I’m trying to get all of the regression tests to work on my Mac which is running OSX 10.9.2 with Xcode 5.1. "clang++ —version” reports “Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)”. I’m building the boost libraries for c++11. I realize boost 1.55 doesn’t officially support this compiler (yet) so I’m out on the bleeding edge, but it’s almost working. I am cheating a little by manually applying a few of the post-1.55 patches, and if I need to do that to get the regression tests to build that’s fine. When I try to compile function.mem_fun_cxx98 it gives me this error: mem_fun_cxx98.cpp:34:46: error: invalid operands to binary expression ('std::__1::basic_ostream<char>' and 'ostream' (aka 'basic_ostream<char>')) BOOST_TEST(f2(&x, boost::ref(std::cout)) == std::cout); ../../../boost/detail/lightweight_test.hpp:186:28: note: expanded from macro 'BOOST_TEST' #define BOOST_TEST(expr) ((expr)? (void)0: ::boost::detail::test_failed_impl(#expr, __FILE__, __LINE__, BOOST_CURRENT_FUNCTION)) 1 error generated. The error looked to me like a stdlib vs. libc++ kind of thing, so I double-checked the compiler options. For the regression test, bjam is calling the compiler like so: "clang++" -x c++ -std=c++11 -stdlib=libc++ -O3 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"../../.." -c -o "/tmp/boost/bin.v2/libs/function/test/mem_fun_cxx98.test/clang-darwin-4.2.1/release/link-static/threading-multi/libs/function/test/mem_fun_cxx98.o” “[SNIP]/mem_fun_cxx98.cpp" The boost libraries are build by calling the compiler: "clang++" -x c++ -std=c++11 -stdlib=libc++ -O3 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_COROUTINES_SOURCE -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"." -c -o “[SNIP]/bin/boost/bin.v2/libs/coroutine/build/clang-darwin-4.2.1/release/link-static/threading-multi/exceptions.o" "libs/coroutine/src/exceptions.cpp" Whether I bootstrap for toolset clang or darwin doesn’t seem to change anything. Building the library and regression test using clang++ without the c++11 flags works correctly. Is this a known problem that has already been patched for the 1.56 release (I can’t find it if so)? Any suggestions on why this might be happening? Thanks, Chris

2 1

[graph/adjacency_list] edge have many costs
by aymen kaabi 08 Apr '14

08 Apr '14

Good morning, I want to create a graph that their egdes have array of cost ( i dont mean bundle property) because i want to create this graph and try dijikstra for every cost values . can i have an example. example: graph have 2 edge 1->2 ( cost 1,2,3,4,7) 2->3(cost 2,5,3,8,9) thanks for your helps

1 0

[serialization] proposed improvements: forward-compatibility of serialization
by Andrzej Horoszczak 08 Apr '14

08 Apr '14

1 0

phoenix bind vs boost bind?
by Robert Dailey 07 Apr '14

07 Apr '14

First of all, I'm using boost 1.55.0 on MSVC9. I've been using boost::phoenix in various places in my code base for easier usage of std::for_each and friends. However, I do not create lazy functions for a lot of the functions I bind to because they are only needed in one place most of the time. As a result, I use boost::phoenix::bind the same as I'd use boost::bind(). However I have read in various places that boost::bind is being deprecated. I'm not sure if there is truth to this, but is there a reason to choose one over the other? Is phx::bind() basically an "upgrade" to boost::bind? If I intermingle them, I have a lot of issues out of placeholder ambiguities that results in more boilerplate code (i.e. using boost::phoenix::placeholders::_1 everywhere). Any tips? I haven't used boost in a few years so I just want to make sure I'm not using it incorrectly. Thanks in advance.

1 0

Re: [boost] [container] Vector-like container, which takes, feedback for Jeremy M.
by Alexander Kuprijanov 07 Apr '14

07 Apr '14

> Message: 3 > Date: Sun, 6 Apr 2014 09:59:20 +1000 > From: Jeremy Murphy <jeremy.william.murphy(a)gmail.com> > On 6 April 2014 00:45, Alexander Kuprijanov <alexkupri(a)gmail.com> wrote: > >> Hi, everybody! >> The most important feature of my container is performance. However, other >> features will appear later. >> https://github.com/alexkupri/array/blob/master/description/description.txt >> Today I compared my container with rope. My container outperformed it 10 >> times. > > > Hi Alex, > > could you include a build file (I recommend CMake)? My cursory attempt to > compile main.cpp spewed lots of errors. Thanks, cheers. > > Jeremy > Hi, Jeremy! Well, I provided makefiles, but I'm not sure if they help. The line: g++ -O3 main.cpp worked well. If you still have problems, be specific and tell, which project (trunk or performance), which errors and which system. "trunk" should be compiled, because I checked it on Linux and Windows; performance is more platform specific and uses __gnu_cxx::rope. Best regards, A.K.

1 0

Network change of the Boost main web/mail server (wowbagger)
by Kim, DongInn 07 Apr '14

07 Apr '14

Dear All, The boost server machine (wowbagger.crest.iu.edu) is requested to change its subnet and I am planning to switch its IP address for the change of the subnet. I have arranged the schedule to update the DNS information of the following hostnames in wowbagger. - www.boost.org - svn.boost.org - lists.boost.org - boostcon.boost.org - beta.boost.org - www.boostcon.org - wiki.boost.org The IP transition date and time: April 07, 2014 6:00am-7:00am Pacific US time 7:00am-8:00am Mountain US time 8:00am-9:00am Central US time 9:00am-10:00am Eastern US time 1:00pm-2:00pm GMT The list of services that may not be available: - Web services: www.boost.org svn.boost.org lists.boost.org ... - Mail services including mailing lists: boost(a)lists.boost.org boost-users(a)lists.boost.org … - Subversion svn.boost.org The old IP address: 129.79.13.33 The new IP address: 129.79.39.203 I have already prepared the IP transition on wowbagger to make the new IP address provide the same services on it so that I hope that there is no actual outage of the services other than the rebooting time. If you happened to use the IP address on your cronjob or programs, please make sure that you switch it with the new one. IMPORTANT ========================================= wowbagger will need to reboot to kick in a new kernel and mount the NFS space with the new IP address at the same time. ========================================== Please let me know if you have any questions or concerns about this IP transition. Regards, -- - DongInn

1 1