- Boost-users - lists.boost.org

[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 16 Apr '14

16 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

can not compile nearest neighbors in d dimensions
by Georgios Samaras 16 Apr '14

16 Apr '14

I can not create a point in d(in the code M is dimensions) dimensions. The error is this: error: the value of ‘M’ is not usable in a constant expression note: ‘int M’ is not const error: template argument 2 is invalid and the line is this: int M; .. typedef bg::model::point<float, M, bg::cs::cartesian> point; Then, I am trying to create an Rtree (I have already the data in a 2D array), like this: // create the rtree using default constructor bgi::rtree< point, bgi::quadratic<16> > rtree; point tmp; for ( unsigned i = 0 ; i < N ; ++i ) { // insert new value for(int j = 0 ; j < M ; ++j) { bg::set<M>(tmp, a[i][j]); } rtree.insert(tmp); } and I think the error is in insert(). I am attaching a file with the minimal code and one with the errors I receive (I receive another one too). I am struggling to achieve that all day long. :/

6 32

Interprenting nearest's neighbor's output
by Georgios Samaras 15 Apr '14

15 Apr '14

I am running the code found here http://www.boost.org/doc/libs/1_54_0_beta1/libs/geometry/doc/html/geometry/… (not the intersect query, only the nn). The output is this: " knn query point: POINT(0 0) knn query result: POLYGON((4 4,4 4.5,4.5 4.5,4.5 4,4 4)) - 4 POLYGON((3 3,3 3.5,3.5 3.5,3.5 3,3 3)) - 3 POLYGON((2 2,2 2.5,2.5 2.5,2.5 2,2 2)) - 2 POLYGON((0 0,0 0.5,0.5 0.5,0.5 0,0 0)) - 0 POLYGON((1 1,1 1.5,1.5 1.5,1.5 1,1 1)) - 1 " What are the integers on the right? Indices of the polygons? Actually is not really clear to me what are we inserting in the tree..I tried finding some documentation on these methods, but I only found info on how to call them... What I want, is simply inserting some points in the tree and then search for nn of a query point. Thanks in advance, George

2 5

[Boost-Interprocess] Suggested approach for message_queue with dynamically sized messages
by Rob Conde 14 Apr '14

14 Apr '14

I want to use boost::interprocess and message_queue...however, the need to specify a max message size is an inhibitor because my message data doesn't necessarily have a limit in size. What is the suggested approach for this scenario? The best I can think of at the moment is to have a "start object" and "stop object" message, and then a "data" message. Then I just send the object in chunks of max_msg_size and reconstitute on the other side. This is all quite possible of course, but if there was a prescribed way to handle this without opening myself to these complexities it would be nice. Thanks in advance, Rob Conde

1 0

Boost Universal Build
by •°o.O sαмι O.o°• 14 Apr '14

14 Apr '14

Hi, I am trying to build boost for all Mac platforms universally, I am having PPC and Intel architecture both. I am using this command to build boost 1_46_1. * ./bjam architecture=combined address-model=32_64 * and got following errors for almost every file: *./boost/python/detail/make_tuple.hpp:25: error: no matching function for call to \'91incref(<type error>)\'92\./boost/python/detail/make_tuple.hpp:25: error: \'91class boost::python::tuple\'92 has no member named \'91ptr\'92\ ./boost/python/detail/make_tuple.hpp:25: error: there are no arguments to \'91PyTuple_SET_ITEM\'92 that depend on a template parameter, so a declaration of \'91PyTuple_SET_ITEM\'92 must be available\* and "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -dynamic -no-cpp-precomp -gdwarf-2 -Wno-long-double -fPIC -arch i386 -arch ppc -arch x86_64 -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/System/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6" -c -o "bin.v2/libs/python/build/darwin-4.0.1/release/address-model-32_64/architecture-combined/threading-multi/object/stl_iterator.o" "libs/python/src/object/stl_iterator.cpp"\ \ *...failed darwin.compile.c++ bin.v2/libs/python/build/darwin-4.0.1/release/address-model-32_64/architecture-combined/threading-multi/object/stl_iterator.o...\* please help me out if I am doing anything wrong or there is any other way of doing this. kind regards;

1 0

Re: [Boost-users] Is selective header including supposed to work?
by Johannes Lorenz 14 Apr '14

14 Apr '14

Joel de Guzman wrote: > It should work, but the savings in compile time will be minimal. > If you want to reduce compile and build time, follow the example > in the compiler tutorial from calc7 up. The trick is to modularize > your grammars and put the definitions in separate cpp files (TUs). I think I start getting how it works. However, the dependency between statement and expression is not circular in calc7: expression seems to have no knowledge about statement. So if my dependency is circular (like e.g. expression and factor in calc2_ast), is it possible to separate them, as you suggest? Also, is there any documentation for calc7 or about TUs (what does TU mean?)? Again, many thanks for your kind answers.

1 0