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

cmake + CUDA 6 + clang + boost errors on OS X Mavericks
by John Owens 24 Apr '14

24 Apr '14

Greetings, I’m using boost (1.55) (installed via macports) on: - OS X Mavericks - using clang (5.1, the Xcode default version, LLVM 3.4) - with CUDA 6 - and cmake (2.8.12.2). It has a large number of compile errors, shown here: http://pastebin.com/Qg2V0UwM that begin with: /opt/local/include/boost/type_traits/is_abstract.hpp(72): error: identifier "__is_abstract" is undefined I’d be delighted to have any advice on how to do cmake + CUDA 6 + clang + boost on OS X! JDO

1 0

include error in OS X 10.9.2
by Freddy Martinez Garcia 22 Apr '14

22 Apr '14

Hi guys I’m trying to use mongodb in my develop. MongoDB use Boost library in its implementation… I had installed boost 1.55 with macport… the problem is when the mongo c++ driver import son files like: #include <boost/function.hpp> and this file does not exists in my system… How can I fix this in Mac ?? I’m new in os x, because in linux I don’t have this error… best regards freddy

1 0

[Boost][Graph] vf2 implementation question
by Marc Viala 20 Apr '14

20 Apr '14

Hi, Recently,I tried to use Boost.Graph's VF2 implementation and after having played few days with this module, I was wondering if this implementation supports "adjacency_matrix" model as explained by the documentation (cf. http://www.boost.org/doc/libs/1_55_0/libs/graph/doc/vf2_sub_graph_iso.html) To demonstrate my point, you will find hereafter an C++ example extracted from the Boost.Graph's documentation. If the macro "ADJACENCY_LIST_STRUCT" is commented out, this code can't be compiled w/ VS2012 aka VC11 because the static assertion @line 837 of "boost/graph/vf2_sub_graph_iso.hpp" is triggered. My questions are: - Does this VF2 implementation supports "adjacency_matrix" model? - Is there any patch for supporting this model of graph? FYI: If I comment two static assertations in file "boost/graph/vf2_sub_graph_iso.hpp", at line 837 and line 843, the code compiles and runs correctly for "adjacency_matrix" model. #include <boost/graph/adjacency_list.hpp> #include <boost/graph/adjacency_matrix.hpp> #include <boost/graph/vf2_sub_graph_iso.hpp> using namespace boost; //#define ADJACENCY_LIST_STRUCT int main() { #ifdef ADJACENCY_LIST_STRUCT typedef adjacency_list<vecS, vecS, undirectedS> graph_type; #else typedef adjacency_matrix<undirectedS> graph_type; #endif // Build graph1. const int num_vertices1 = 8; graph_type graph1(num_vertices1); add_edge(0, 6, graph1); add_edge(0, 7, graph1); add_edge(1, 5, graph1); add_edge(1, 7, graph1); add_edge(2, 4, graph1); add_edge(2, 5, graph1); add_edge(2, 6, graph1); add_edge(3, 4, graph1); // Build graph2. const int num_vertices2 = 9; graph_type graph2(num_vertices2); add_edge(0, 6, graph2); add_edge(0, 8, graph2); add_edge(1, 5, graph2); add_edge(1, 7, graph2); add_edge(2, 4, graph2); add_edge(2, 7, graph2); add_edge(2, 8, graph2); add_edge(3, 4, graph2); add_edge(3, 5, graph2); add_edge(3, 6, graph2); // Compute de subgraph isomorphing. vf2_print_callback<graph_type, graph_type> cb(graph1, graph2); vf2_subgraph_iso(graph1, graph2, cb); } Best regards, Marc

1 0

[Iostream] how to build iostream with zlib on windows
by Pritesh Acharya 18 Apr '14

18 Apr '14

Boost version: 1.55.0 OS: Windows 8 IDE: Visual Studio 2010 Is there a good tutorial on building boost iostream with zlib on windows. I looked over reference manual but with no solution. I did download zlib dll and source code and made reference in visual studio. I have link error on gzip_decompressor();

3 2

Using metric_tsp_approx with bundled properties
by Alexis Praga 18 Apr '14

18 Apr '14

Hi, I am trying to use metric_tsp_approx on a graph defined as : typedef adjacency_list<vecS, vecS, undirectedS, City, Road> Graph; City contains the vertex id and Road the edge weight. After reading the documentation, I arrived to : metric_tsp_approx(g_init, weight_map(get(&Road::length, g_init)). vertex_index_map(get(&City::id, g_init)), make_tsp_tour_visitor(back_inserter(c))); I have compilation errors however. The relevant part seems to be : /usr/include/boost/property_map/property_map.hpp:382:58: error: no type named ‘key_type’ in ‘struct boost::property_traits<boost::bgl_named_params<boost::bundle_property_map<boost::adjacency_list<boost::vecS, boost::vecS, boost::undirectedS, City, Road>, long unsigned int, City, int>, boost::vertex_index_t, boost::no_property> >’ Any help appreciated, thanks. -- Alexis Praga, PhD Student (CERFACS) GPG key : AD4A AF6D BB5C 042F 9422 1223 06E1 C1BF E287 65D0

3 7

[asio]Does the function of async_read can find the tcp connection has closed?
by lx 18 Apr '14

18 Apr '14

hi all: I want to know async_read or async_write can detect the tcp connection has closed, or not? thank you

3 4

[container] header reference for most containers is unavailable in Boost 1.55
by Adam Romanek 17 Apr '14

17 Apr '14

Hi! there's a problem with the documentation of most containers from Boost.Container in Boost 1.55. The problem is that hyper-links seem to be missing, i.e. I can't click on deque, list or map. However, the links to the reference of vector or string are fine... WBR, Adam Romanek [1] http://www.boost.org/doc/libs/1_55_0/doc/html/boost_container_header_refere…

1 0

boost serialize issue when compile 64 bit application
by gary jiang 17 Apr '14

17 Apr '14

Hi all, I am compiling 64 bit application, and got lots of errors about boost serializer, but I don't have any issue when compile 32 bit application. Is there some attention when transform from 32 bit boost to 64 bit boost? Any advice would be appreciate, thanks in advance! PS: We used intel toolchain to compile boost, and tried with different boost version, still got same errors. Regards, Gary Main.o: In function `boost::archive::detail::iserializer<CMyText_iarchive, AtworkPathInfo>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const': Main.cpp:(.text._ZNK5boost7archive6detail11iserializerI16CMyText_iarchive15AtworkPathInfoE16load_object_dataERNS1_14basic_iarchiveEPvj[_ZNK5boost7archive6detail11iserializerI16CMyText_iarchive15AtworkPathInfoE16load_object_dataERNS1_14basic_iarchiveEPvj]+0x4b): undefined reference to `void AtworkPathInfo::serialize<CMyText_iarchive>(CMyText_iarchive&, unsigned int)' Schedule.o: In function `boost::archive::detail::iserializer<CMyText_iarchive, GERINFO>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const': Schedule.cpp:(.text._ZNK5boost7archive6detail11iserializerI16CMyText_iarchive11GERINFOE16load_object_dataERNS1_14basic_iarchiveEPvj[_ZNK5boost7archive6detail11iserializerI16CMyText_iarchive11GERINFOE16load_object_dataERNS1_14basic_iarchiveEPvj]+0x4b): undefined reference to `void GERINFO::serialize<CMyText_iarchive>(CMyText_iarchive&, unsigned int)' Images.o: In function `boost::archive::detail::iserializer<CMyText_iarchive, MNTINFO>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const': Images.cpp:(.text._ZNK5boost7archive6detail11iserializerI16CMyText_iarchive9MNTINFOE16load_object_dataERNS1_14basic_iarchiveEPvj[_ZNK5boost7archive6detail11iserializerI16CMyText_iarchive9MNTINFOE16load_object_dataERNS1_14basic_iarchiveEPvj]+0x4b): undefined reference to `void MNTINFO::serialize<CMyText_iarchive>(CMyText_iarchive&, unsigned int)' Images.o: In function `boost::archive::detail::iserializer<CMyText_iarchive, VOLUMEINFO>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const': Images.cpp:(.text._ZNK5boost7archive6detail11iserializerI16CMyText_iarchive13VOLUMEINFOE16load_object_dataERNS1_14basic_iarchiveEPvj[_ZNK5boost7archive6detail11iserializerI16CMyText_iarchive13VOLUMEINFOE16load_object_dataERNS1_14basic_iarchiveEPvj]+0x4b): undefined reference to `void VOLUMEINFO::serialize<CMyText_iarchive>(CMyText_iarchive&, unsigned int)' Info.o: In function `boost::archive::detail::oserializer<CMyText_oarchive, MAPPINGINFO>::save_object_data(boost::archive::detail::basic_oarchive&, void const*) const': Info.cpp:(.text._ZNK5boost7archive6detail11oserializerI16CMyText_oarchive14MAPPINGINFOE16save_object_dataERNS1_14basic_oarchiveEPKv[_ZNK5boost7archive6detail11oserializerI16CMyText_oarchive14MAPPINGINFOE16save_object_dataERNS1_14basic_oarchiveEPKv]+0x5a): undefined reference to `void MAPPINGINFO::serialize<CMyText_oarchive>(CMyText_oarchive&, unsigned int)' Info.o: In function `boost::archive::detail::iserializer<CMyText_iarchive, MAPPINGINFO>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const': Info.cpp:(.text._ZNK5boost7archive6detail11iserializerI16CMyText_iarchive14MAPPINGINFOE16load_object_dataERNS1_14basic_iarchiveEPvj[_ZNK5boost7archive6detail11iserializerI16CMyText_iarchive14MAPPINGINFOE16load_object_dataERNS1_14basic_iarchiveEPvj]+0x4b): undefined reference to `void MAPPINGINFO::serialize<CMyText_iarchive>(CMyText_iarchive&, unsigned int)' make[1]: *** [service] Error 1 make[1]: Leaving directory `/home/gary/product_100/CoreService' make: *** [all] Error 1

2 2

[container] vector::resize() - value-initialization vs default-initialization
by Adam Romanek 16 Apr '14

16 Apr '14

Hi! first, I'd like to focus on Boost 1.54. The documentation of boost::container::vector::resize(size_type) says the elements are *default constructed* [1]. The same applies to the respective constructor: boost::container::vector(size_type n). This is a significant deviation from what C++11 std::vector::resize(size_type) does as it *value-initializes* the new elements. Is the documentation of Boost.Container wrong in this case? Or the behavior of the container differs from the one defined by the standard? On the other hand in Boost 1.55 I see some changes related to the way elements are constructed (not mentioned in the release note). A new constructor and resize() method were added taking default_init_t to indicate default construction of new elements is desired. However, the documentation of boost::container::resize(size_type new_size, default_init_t) says the new elements are value initialized [2]. Note that the documentation of the respective constructor is correct and says the elements are default constructed. I also assume that the addition of the new constructor/resize method changed the behavior of the original constructor/resize method to be compliant with std::vector. Finally, @Ion: thanks for your good work on this library. I use it more and more often as it provides great features, useful especially in C++03 environments. If you want me to file any tickets on the above-mentioned issues please just say so. WBR, Adam Romanek [1] http://www.boost.org/doc/libs/1_54_0/doc/html/boost/container/vector.html#i… [2] http://www.boost.org/doc/libs/1_55_0/doc/html/vector.html#idp20954152-bb

2 4

Build boost on OSX 10.9 with GCC 4.8
by Jürgen Simon 16 Apr '14

16 Apr '14

Hello, I have a somewhat specific problem. I need to build Boost 1.55 with the GCC 4.8 compiler on the mac. I have installed gcc-4.8 using homebrew. Using the GCC compiler instead of clang is non-negotiable in my case, because I require OpenMP which is not implemented in clang yet. Given that, I tried to build boost this way: export CC=/usr/local/Cellar/gcc48/4.8.2/bin/gcc-4.8 export CXX=/usr/local/Cellar/gcc48/4.8.2/bin/g++-4.8 export LD=/usr/local/Cellar/gcc48/4.8.2/bin/g++-4.8 ./bootstrap.sh —with-toolset=gcc-4.8 gives an error: Building Boost.Build engine with toolset gcc-4.8... Failed to build Boost.Build build engine Consult 'bootstrap.log' for more details apparently it does not recognize the gcc-4.8 toolkit. Using gcc instead does create the b2 script, but running the script as is also created trouble: ./bootstrap.sh —with-toolset=gcc ./b2 common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1 common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release/threading-multi gcc.compile.c++ bin.v2/libs/atomic/build/gcc-4.2.1/release/threading-multi/lockpool.o In file included from libs/atomic/src/lockpool.cpp:3: In file included from ./boost/atomic.hpp:12: In file included from ./boost/atomic/atomic.hpp:17: In file included from ./boost/atomic/detail/platform.hpp:22: ./boost/atomic/detail/gcc-atomic.hpp:961:64: error: no matching constructor for initialization of 'storage_type' (aka 'boost::atomics::detail::storage128_type') explicit base_atomic(value_type const& v) BOOST_NOEXCEPT : v_(0) specifying the toolkit gcc-4.8 here does actually do something: ./bootstrap.sh —with-toolset=gcc ./b2 -d 2 toolset=gcc-4.8 but it results in linker errors, like the following two examples: "g++-4.8" -Wl,-R -Wl,"/System/Library/Frameworks/Python.framework/Versions/2.7/lib" -Wl,-R -Wl,"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config" -o "stage/lib/libboost_iostreams.dylib" -Wl,-h -Wl,libboost_iostreams.dylib -shared -Wl,--start-group "bin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi/file_descriptor.o" "bin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi/mapped_file.o" "bin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi/bzip2.o" -Wl,-Bstatic -Wl,-Bdynamic -lbz2 -Wl,--end-group ld: unknown option: -R "g++-4.8" -o "bin.v2/libs/atomic/build/gcc-4.8/release/threading-multi/libboost_atomic.dylib" -Wl,-h -Wl,libboost_atomic.dylib -shared -Wl,--start-group "bin.v2/libs/atomic/build/gcc-4.8/release/threading-multi/lockpool.o" -Wl,-Bstatic -Wl,-Bdynamic -Wl,--end-group ld: unknown option: -h I tried for two days without success to get GCC-4.8 and Boost to play ball together on the Mac. What am I missing? Kind Regards, Jürgen

2 2