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

Under ubuntu, How to purge default boost-v1.58 then switch to the built version without any damages?
by Alex Luya 06 Nov '17

06 Nov '17

Under ubuntu 16,04 I have*built latest boost 1.65**.1 like this*: |./bootstrap.sh --prefix=/usr/local ./b2 sudo ./b2 install sudo ldconfig ***then when building something against boost,I got the**se errors:* /usr/local/include/boost/serialization/access.hpp: In instantiation of ‘static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’: /usr/local/include/boost/serialization/serialization.hpp:68:22: required from ‘void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/serialization/serialization.hpp:126:14: required from ‘void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/archive/detail/oserializer.hpp:150:40: required from ‘void boost::archive::detail::oserializer<Archive, T>::save_object_data(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/archive/detail/oserializer.hpp:103:1: required from ‘class boost::archive::detail::oserializer<boost::archive::text_oarchive, std::array<std::__cxx11::basic_string<char>, 10ul> >’ /usr/local/include/boost/archive/detail/oserializer.hpp:255:13: required from ‘static void boost::archive::detail::save_non_pointer_type<Archive>::save_standard::invoke(Archive&, const T&) [with T = std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/detail/oserializer.hpp:310:22: required from ‘static void boost::archive::detail::save_non_pointer_type<Archive>::invoke(Archive&, const T&) [with T = std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/detail/oserializer.hpp:534:18: required from ‘void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive; T = const std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/archive/detail/common_oarchive.hpp:70:22: required from ‘void boost::archive::detail::common_oarchive<Archive>::save_override(T&) [with T = const std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/basic_text_oarchive.hpp:83:9: required from ‘void boost::archive::basic_text_oarchive<Archive>::save_override(T&) [with T = const std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/detail/interface_oarchive.hpp:70:9: required from ‘Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(const T&) [with T = std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ examples/user_code/openpose_recognition.cpp:867:89: required from here /usr/local/include/boost/serialization/access.hpp:116:9: error: ‘struct std::array<std::__cxx11::basic_string<char>, 10ul>’ has no member named ‘serialize’ t.serialize(ar, file_version); ^ compilation terminated due to -Wfatal-errors. Makefile:478: die Regel für Ziel „.build_release/examples/user_code/openpose_recognition.o“ scheiterte make: *** [.build_release/examples/user_code/openpose_recognition.o] Fehler 1 make: *** Auf noch nicht beendete Prozesse wird gewartet … | |*I think ubuntu is still use default boost that installed by apt-get,so I tried to pur**ge it * sudo apt-get purge libboost1.58-dev| *the output asks me to remove a lot of stuffs **that depend on libboost1.58-dev **like these:* Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: docutils-common fltk1.3-doc fluid gazebo7 gazebo7-common gazebo7-plugin-base gir1.2-gtk-2.0 libapr1 libapr1-dev libaprutil1 libaprutil1-dev libarmadillo6 libassimp-dev libassimp3v5 libboost-atomic1.58.0 libboost-chrono1.58.0 libboost-context1.58.0 libboost-coroutine1.58.0 libboost-graph-parallel1.58.0 libboost-graph1.58.0 libboost-locale1.58.0 libboost-log1.58.0 libboost-math1.58.0 libboost-mpi-python1.58.0 libboost-mpi1.58.0 libboost-python1.58.0 libboost-random1.58.0 libboost-regex1.58.0 libboost-signals1.58.0 libboost-test1.58.0 libboost-thread1.58.0 libboost-timer1.58.0 libboost-tools-dev libboost-wave1.58.0 libboost1.58-tools-dev libbullet-dev libbulletcollision2.83.6 libbulletdynamics2.83.6 libbulletsoftbody2.83.6 libbz2-dev libcollada-dom2.4-dp-dev libcollada-dom2.4-dp0 libconsole-bridge-dev libconsole-bridge0.2v5 libcurl4-openssl-dev libdap-dev libdap17v5 libdapclient6v5 libdapserver7v5 libepsilon1 libflann-dev libflann1.8 libfltk-cairo1.3 libfltk-forms1.3 libfltk-images1.3 libfltk1.3-dev libfreeimage-dev libfreeimage3 libfreexl1 libgazebo7 libgdal-dev libgdal1i libgeos-3.5.0 libgeos-c1v5 libgeos-dev libgl2ps-dev libgtest-dev libgtk2.0-dev libgts-0.7-5 libgts-bin libgts-dev libhdf4-0-alt libhdf4-alt-dev libhdf5-mpi-dev libignition-math2 libignition-math2-dev libinput-dev libjs-jquery-ui libjsoncpp-dev libjxr0 libkmlbase1 libkmldom1 libkmlengine1 libldap2-dev liblinearmath2.83.6 liblog4cxx-dev liblog4cxx10-dev liblog4cxx10v5 liblz4-dev libminizip1 libnetcdf-c++4 libnetcdf-cxx-legacy-dev libnetcdf-dev libnetcdf11 libogdi3.2 libogre-1.9.0v5 libopenni-dev libopenni-sensor-pointclouds0 libopenni0 ....... ,and it may cause a lot of damage if continuing,so the question is |*How to purge default boost-v1.58 then switch to the built version without any damages?*|

3 2

[asio] Does ssl::stream allow multiple pending async operations?
by Phil Sean 06 Nov '17

06 Nov '17

The documentation for ssl::stream says: "Shared objects: Unsafe. The application must also ensure that all asynchronous operations are performed within the same implicit or explicit strand." Does this mean we have to wait for an async operation to finish before another is started (for read/read, read/write, and write/write)? (Async operations refer to async_read_some() and async_write_some(), not the composed operations.) If so, is the operation said to have finished when the handler is invoked or when the handler returns? That is: void handler( const boost::system::error_code& error, std::size_t bytes_transferred ) { // Does the operation finish here ... } // or here? If not, what's the difference between the async operations of ip::tcp::socket and ssl::stream then (as strand just avoids concurrency for the thread-unsafe)? I came across different views on this problem. This answer[1] suggests that simply using the same strand (ie. no concurrency) will suffice. Another one[2] says multiple pending asynchronous operations can be problematic for ssl::stream even if no concurrency occurs. Thanks. [1] https://stackoverflow.com/questions/27212123/executing-asynchronous-operati… [2] https://stackoverflow.com/questions/15352472/using-boosts-ssl-asio-code-asy…

4 5

Spirit: how to force backtracking
by Stian Zeljko Vrba 04 Nov '17

04 Nov '17

I have the following grammar rule: value = (int_ % ',') | *ascii::print; The intention is to parse either a comma-separated list of integers or a string. The rule as such fails in cases like "123ABC", which should be parsed as string. >From the description of the | operator, I would expect the parser to backtrack and try the other alternative when it sees that the first alternative does not match the input. However, I get a parse error instead (this rule is a part of a larger grammar), I guess because the first alternative matches the single integer but the rest of the grammar cannot be matched. How to rewrite the grammar to resolve this ambiguity, or force spirit to backtrack if the first alternative of 'value' cannot be matched?

3 3

[locale] how to read a local date from an istream?
by Frédéric 02 Nov '17

02 Nov '17

Hi, With boost::locale we can output a localized date: double d=...; std::cout<<boost::locale::as::date<<d; but how can I read a date from a string? std::cin>>boost::locale::as::date>>d; does not work. It stops reading at the first "/". For example, this small program #include <iostream> #include <sstream> #include <boost/locale/formatting.hpp> #include <boost/locale/generator.hpp> int main(int argc, char **argv) { boost::locale::generator gen; gen.categories(); auto loc = gen(""); double date = 5.; // default value to see if it changes std::istringstream iss("2/11/2017"); // November 1st, 2017 in French iss.imbue(loc); iss >> boost::locale::as::date >> boost::locale::as::local_time >> date; std::cout.imbue(loc); std::cout << "as_posix: " << boost::locale::as::posix << date << "\n" << "as_date: " << boost::locale::as::date << date << "\n"; return 0; } outputs as_posix: 2 as_date: 01/01/1970 instead of as_posix: 1509617233 (may be different) as_date: 02/11/2017 F

1 0

Re: [Boost-users] Many undefined references for libboost_filesystem
by mahmood n 01 Nov '17

01 Nov '17

I used another gcc version 4.5 (Ubuntu 11.04) and it works without any problem! I don’t know what is wrong with gcc-4.6. Though the problematic platform was Kubuntuu 12.04. I am know trying with Ubuntu 12.04 which uses gcc-4.6 to see if it is really a gcc problem or the platform! Sent from Mail for Windows 10 From: Alex Perry Sent: Wednesday, October 18, 2017 4:45 PM To: mahmood n Subject: RE: [Boost-users] Many undefined references for libboost_filesystem Actually one other thought (though you may well have solved this by now). Are you sure that the boost libraries you are attempting to link to are using the same abi? Ie how were they built. I only glanced at the github stuff you pointed too but I think I remember that the last commit was 5 years ago or some such – so probably wasn’t using C++11. I note you are using an old (54) version of boost whilst the current is (65) so about 5 years ago as well – but that probably supported being built with c++11.so you might need to rebuild them if they were using a different version of the C++ standard (or any abi breaking change such as 32 vs 64 bit, static runtime vs dynamically loaded etc). Under windows boost normally encodes the abi into the library name and you just automagically (using a msvc extension) link to the appropriate one. That is not the normal way on linux since gcc doesn’t have autolinking so you normally end up sticking them into a separate lib directory and swapping the -L path depending on which abi you want Again though please note this is not boost specific – is just standard C / C++ / Fortran or any obj/link based language issues with building dependencies – (and why most have swapped to using cmake rather than vanilla make to avoid the pain). A. From: Alex Perry Sent: 17 October 2017 16:14 To: 'mahmood n' <nt_mahmood(a)yahoo.com> Subject: RE: [Boost-users] Many undefined references for libboost_filesystem Dropped the rest of the boost list since I’m sure not many are interested! > I didn’t want to have another pain for “finding how the verbose variable is set in the Makefile”!!! Not hard that one… just add it to the command line when you call make make verbose=1 ….. > The libraries do exist, so why on earth it can not link :( > mahmood@vb:AES$ g++ -fPIC -L/home/mahmood/boost_1_54_0/stage/lib -lboost_filesystem -lboost_system -m64 -o /home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/release/AES obj/x86_64/release/aescuda.cpp.o obj/x86_64/release/aesCudaUtils.cpp.o obj/x86_64/release/aesHost.cu.o -L/usr/local/cuda/lib64 -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../lib -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../common/lib/linux -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../../shared//lib -lcudart -L/usr/local/cuda/lib64 -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../lib -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../common/lib/linux -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../../shared//lib -lcudart -lcutil_x86_64 -lshrutil_x86_64 …. Nope the computer is telling you they don’t exist on those paths as given – unfortunately the computer is more likely to be correct than you on this! You have a lot of library paths being set there – possibly you have multiple versions of boost libraries so its finding the wrong one first so you have a version conflict Possibly the simplest way is create a noddy test and play with the command line till you work out what the problem is http://rextester.com/live/JDVHT54458 That will give you similar compile errors without -lboost_filesystem -lboost_system added to the compile line. Obviously that is using clang rather than gcc which you are using but the syntax and principles are pretty much the same between any c++ compiler HTH A.

5 6

Boost graph library algorithms - is it possible to use previous solutions to "warm start" a new related problem
by F1E2D3 F1E2D3 29 Oct '17

29 Oct '17

Hello, I am primarily an Operations Researcher, and prior to boost, was writing my own C++ code for specific network flow problems. I am now hoping to transition to boost::graph completely for my network flow problem solution needs. However, I have one major concern. In linear programming (I use CPLEX https://www.ibm.com/us-en/marketplace/ibm-ilog-cplex as my primary linear programming (LP) solver), once a problem is solved, say a Dijkstra's shortest path problem, the solver maintains the optimal basis. Then, if some problem parameter changes, the linear program need not be solved from scratch, but the current basis is first tested for optimality for the new problem as well. An example of this would be an increase in the cost of an arc that does not feature on the optimal path from source to destination in a shortest path problem. This increase in cost does not change the optimal path, and hence, it would be wasteful to solve this problem again from scratch. Does boost::graph have this capability that LP solvers have? I posted this question first on stack overflow and am posting it here now. The question was not completely answered there. A working code and small example are provided there. I am giving the link below. https://stackoverflow.com/questions/46986312/are-boostgraph-algorithms-capa… Any help will be appreciated. Thanks.

1 0

[review][DoubleEnded] Review Results
by Thorsten Ottosen 27 Oct '17

27 Oct '17

Dear users and members of Boost, I'm happy to to announce that Benedek Thaler's Boost.DoubleEnded is /conditionally/ accepted into Boost provided that it can be integrated smoothly with Boost.Container. There are several other conditions, some major and some minor which I will outline below. For now, I would like to thank everyone that participated with reviews and comments. We didn't have that many reviews, but the reviewers did spend a lot of time both on review and the following discussions. Special thanks also goes to Benedek for his hard work. It is not too often that a GSOC code ends with something of this quality. Two of the world's expert C++ container developers used phrases like "solid" and "everything looks clean and beautiful" about the implementation, "tests look very good, corner cases and all", "The reference section is very good". Congratulations, Benedek. ============== A path forward ============== Ion has most kindly accepted the idea of merging the library into Boost.Container. This consists of A. taking selected elements from batch_deque and adding them to boost::container::deque. B. putting devector into boost.container after changes have been applied to code and documentation C. back-porting the devector code to C++03 (C) does not need to happen immediately, that is, we can have a release where devector is available in a C++11 version. Ion has also most kindly agreed to help with this process. I will help write a new introduction that focuses on the main principles of devector. We also have a number of benchmarks which we can gather and use for a small section of on that topic. I'll leave it to you and Ion to work out the details. ========================== Detailed comments devector ========================== Apart from the merging with Boost.Container, the most heard complaint was about the "fat", the non-essential parts if the interface, that could be removed. This includes -- Remove the direct support for small buffer optimization form devector. When the time comes, provide small_devector similar to the way we have vector/small_vector (there is no requirement that small_devector is provided). -- remove all of the following: - all constructors that uses reserve_only_tag, - all constructors that uses unsafe_uninitialized_tag, - void unsafe_uninitialized_resize_front(size_type); - void unsafe_uninitialized_resize_back(size_type); - unsafe_push_front(...); - unsafe_push_back(...); -- add instead - constructors that uses default_init_t like boost.container - resize versions that uses default_init_t - T& unchecked_emplace_back(...) noexcept(...) - T& unchecked_emplace_front(...) noexcept(...) At some point, I hope we can upgrade default_init_t to mean no construction for all trivially copyable types. There was a wish for more symmetry in devector and so functions that break symmetry or can appear ambiguous should be removed. This means we should remove: -- capacity() There is no need for front_capacity() and back_capacity(). We could remove reserve(), but then we can't use devector with a flat_set. Reserve() should not be an alias for reserve_back() though, but controlled by the policy. We could remove resize(), but even deque has it where it means resize_back(). I totally agree it would be ideal to remove all of reserve(),resize(),capacity(),clear(), but I see no easy way we can use devector with flat containers if we remove the first and the last. Unless we start deprecating stuff in boost::deque/boost::vector and provide new consistent alternatives, we will never get a 100% satisfactory solution. At the end of the day, we need to be pragmatic, so if deprecation is not on the table, this seems the best we can do. Since we don't want two allocations implied by calling reserve_back() and reserve_front(), you can add a mechanism for doing that. That is, you can provide -- reserve( new_capacity ); -- reserve_front( new_front_capacity ) -- reserve_back( new_back_capacity ) -- reserve( new_front_capacity, new_back_capacity ) or, since reserve() is such a weird beast, simply provide -- reserve( new_capacity ); // for flat containers -- anticipate_front( new_front_elements ) -- anticipate_back( new_back_elements ) -- anticipate( new_front_elements, new_back_elements ) to get rid of the funky -- container.reserve_front( container.size() + new_front_elements ) dance. There were suggestions for shrink_back/front_to_fit, but since we are trying to remove fat, I suggest that we wait for a use-case. There were also suggestions that clear() should be amended. As the growth (or resizing policy) mandates what clear does, we need a way to escape. The minimal change that allows that is to provide -- clear( front_free_capacity ) which gives full power to the user. You may provide clear_back() as clear(0) and clear_front() as clear(c.size()+c.front_free_capacity()+c.back_free_capacity()). Ideally, clear() would have been removed entirely like capacity()/resize(), but like reserve(), it just seems like impossible when we start using it with flat containers. Other minor comments: - drop strong exception safety guarantees and do it like boost.container - prefer to make iterator a type (should be easy with reuse from boost::container::vector - allocator should not be inherted from - make clear O(1) amortized gurantees depend on growth policy - consider calling growth policy for resizing policy - make sure SFINAE works properly with constructors - make the default growth factor 2 (as we heard from Sean Parent: no factor below 2 is empirically good) - consider renaming front_free_capacity to free_front_capacity. Rationale: "front_capacity" is a concept, noun, and "free" is the adjective. Ditto for back_free_capacity. - remove size_type from growth policy and take it from the allocator - make the allocator template argument the 2nd argument - fix remaning TODO in code - documentation should not sell devector as drop-in replacement for vector, but rather stress it is not - the allocator supports needs to be improved. I guess doing it the Boost.Container way ensures that (ask Daniel James for help) - exception-safety issues pointed out by Ion - postconditions of insert/erase needs to specify behavior to front_free_capacity/back_free_capcity - use of local containers should be avoided - rotate should be avoided - delegate range move operations to those defined in Boost.Container - make sure all functions excepting non-overlapping range uses memcpy (not just memmove). This includes: - range constructor - copy-constructor - copy-assignment - range-assignment - range insert - destructor should used std::has_trivial_destructor to avoid loop in that case to make sure all compilers optimize it away (similar for erase). There is one final puzzle and that is the growth policy. I hope we can finalize that by testing Joaquin's and Ion's suggestions over the coming weeks. ============================= Detailed comments batch_deque ============================= For deque, the comments were similar, although there was far less to discuss than for devector. All agreed that one should be able to control the segment size. - stable_insert was not needed. - segment iteration was good, but should be usable with range-based for loop. The segment iterator should return a segment type if possible, and the segment should have begin(),end(),size() members. - since boost::deque already has a resize with default_init_t, that should be sufficient to provide fast serialization load for trivial types. No need for - resize_front - resize_back - unsafe_uninitialized_resize_front - unsafe_uninitialized_resize_back - reserve - shrink_to_fit() - capacity() The following are still needed for optimal code (or code that can be known not to reallocate, or for better locality in deserialization, avoiding double initialization) - free_front_capacity; - free_back_capacity; - reserve_front - reserve_back - unchecked_emplace_front - unchecked_emplace_back Boost.Container's unit-tests should be extended with those from batch_deque where it makes sense. Since segmented iteration was somewhat faster, it should be use internally where it makes sense. In particular - copy-constructor - copy-assignment - destructor As for devector, all constructor/functions that iterate over non-overlapping ranges should use memcpy. destructor should use is_trivially_destructible to ensure it is optimized away (similar for erase). ====================== Serialization comments ====================== I suggest that the default versions just do what Boost.Serialization does, perhaps just replacing resize with resize with default_init_t. That ensures it works correctly for all archive types. It also needs to use make_nvp() so the output is identical to std::vector. We will then talk to Robert about how we can take advantage of the binary archive in a correct fashion. ====================== kind regards Thorsten, review manager

3 3

[Container] Does deque allocate memory in default constructor?
by dariomt＠gmail.com 25 Oct '17

25 Oct '17

It seems std::deque implementations are allowed to allocate in the default constructor [1] However, boost::container::deque I think does not allocate in the default constructor, but the docs are not explicit about it. I can see in the docs: *Throws*: If allocator_type's default constructor throws. Which would mean that it cannot throw due to memory exhaustion, so it cannot allocate memory. Is my reasoning right? If yes, would it be possible to make this explicit in the docs? I think it is relevant, because it might be the deciding factor for switching from std::deque to boost::container::deque (as it might be my case). Thanks! [1] https://stackoverflow.com/questions/40203494/why-does-stddeque-allocate-mem…

2 1

Fwd: Boost compilation problems
by Berkus Karchebnyy 24 Oct '17

24 Oct '17

Hello, in attempt to build boost for android with more or less reasonable strict settings (-Werror) I uncovered some bugs which I cannot report on github because these projects have Issues disabled. I will post them here in hopes they will eventually reach appropriate maintainers. == ONE: boost.containers == clang-darwin.compile.c android-build/boost/bin.v2/ libs/container/build/clang-darwin-5.0~x86/debug/address- model-32/link-static/target-os-android/threading-multi/alloc_lib.o In file included from libs/container/src/alloc_lib.c:19: libs/container/src/dlmalloc_ext_2_8_6.c:1097:8: error: variable 'ret' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes- uninitialized] if (!PREACTION(m)) { ^~~~~~~~~~~~~ libs/container/src/dlmalloc_ext_2_8_6.c:1125:11: note: uninitialized use occurs here return ret; ^~~ libs/container/src/dlmalloc_ext_2_8_6.c:1097:4: note: remove the 'if' if its condition is always true if (!PREACTION(m)) { ^~~~~~~~~~~~~~~~~~~ libs/container/src/dlmalloc_ext_2_8_6.c:1095:4: note: variable 'ret' is declared here boost_cont_malloc_stats_t ret; ^ 1 error generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTAINER_STATIC_LINK=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/ libs/container/build/clang-darwin-5.0~x86/debug/address- model-32/link-static/target-os-android/threading-multi/alloc_lib.o" "libs/container/src/alloc_lib.c" == TWO: boost.serialization and monty python == (cue Benny Hill music) clang-darwin.compile.c++ android-build/boost/bin.v2/ libs/serialization/build/clang-darwin-5.0~x86/debug/ address-model-32/link-static/target-os-android/threading- multi/polymorphic_iarchive.o In file included from libs/serialization/src/polymorphic_iarchive.cpp:20: In file included from ./boost/archive/polymorphic_iarchive.hpp:32: ./boost/archive/detail/iserializer.hpp:69:7: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined] #if ! DONT_USE_HAS_NEW_OPERATOR ^ ./boost/archive/detail/iserializer.hpp:63:12: note: expanded from macro 'DONT_USE_HAS_NEW_OPERATOR' || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590) \ ^ ./boost/archive/detail/iserializer.hpp:212:9: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined] #if DONT_USE_HAS_NEW_OPERATOR ^ ./boost/archive/detail/iserializer.hpp:63:12: note: expanded from macro 'DONT_USE_HAS_NEW_OPERATOR' || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590) \ ^ 2 errors generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c++ -ftemplate-depth-255 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++14 -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/libs/serialization/build/ clang-darwin-5.0~x86/debug/address-model-32/link-static/ target-os-android/threading-multi/polymorphic_iarchive.o" "libs/serialization/src/polymorphic_iarchive.cpp" == THREE: boost.program_options == clang-darwin.compile.c++ android-build/boost/bin.v2/ libs/program_options/build/clang-darwin-5.0~x86/debug/ address-model-32/link-stati c/target-os-android/threading-multi/cmdline.o libs/program_options/src/cmdline.cpp:104:41: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror ,-Wshadow] cmdline::init(const vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:508:48: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror ,-Wshadow] cmdline::parse_long_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:545:49: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_short_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:611:47: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_dos_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:632:58: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_disguised_long_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:663:47: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_terminator(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:683:55: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::handle_additional_parser(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ 7 errors generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c++ -std=c++14 -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/libs/program_options/build/ clang-darwin-5.0~x86/debug/address-model-32/link-static/ target-os-android/threading-multi/cmdline.o" "libs/program_options/src/ cmdline.cpp" The entire set of compile flags and NDK version can be seen in the provided snippets. Thanks. -- Sr. Software Engineer [image: twilio] <http://www.twilio.com/?utm_source=email_signature> EMAIL berkus(a)twilio.com

1 0

Help needed in learning to use Boost.Asio
by Osman Zakir 24 Oct '17

24 Oct '17

I want to learn how to use Boost.Asio so I can then create an abstraction layer over it for HTTP and create a server and client. I need it for a web app I want to make. I know C++ isn’t a good choice for this sort of thing, but it’s still growing and getting better, so I wonder if there’s really no hope for it becoming a better choice for web development. Especially if someone were to propose a networking library for boost that also provides support for the HTTP protocol and maybe also RESTful services out of the box. Libraries in Boost have a high chance of making it into the standard, after all, so this could be a good idea. I’ve heard from many people that C++ is a waste of time, especially if one wants to get into web development and make a lot of money. Most people who want to web development are abandoning C++ in favor of languages Python that provide better support for web development. I don’t like this and I hope that C++ will also become better for the job soon so that it can pull back programmers that have left it for other languages. That’s also the reason why I want to use C++ here. I’m hoping that the Networking TS would be standardized and that the standardizing committee would also do something to make C++ overall better for the web, preferably as good as Python if possible. The difficulty of getting into and using C++ is also overly-exaggerated but it seems to be more because of C++ programmers not making their code simple and beautiful enough, so it’s also the language users’ fault. I want to try to change the negative views that people have of C++, as well. By the way, would it be a good idea to send an email asking about the future of C++, especially for web development, to Dr. Stroustrup if I can find a way to contact him? I know he’s a busy man and I’m also reluctant to this, but since he’s also on the standard-making committee, if he finds some free time to reply to my email, he should be able to tell me what to expect about C++ and its future. I’m sorry if this email got too long, though. Best regards. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

5 7

boost asio
by Sharma, Nishant 23 Oct '17

23 Oct '17

Hi, I have created an Asynchronous TCP server and client and it works fine. Since it is asynchronous, it uses API's like async_read, async_write etc.. Is it possible that the same code be used to do "synchronous" communication which results in blocking any further task in the queue unless the current i/o task is complete ? I have attached the example hereby. It has two folder for server and client.. First the server needs to be run and then the client. Best Regards, Nishant Sharma

3 5

boost fileystem issue
by Olivier Tristan 20 Oct '17

20 Oct '17

Hi Guys, I would like to bump this particular issue that is quite annoying for me. Basically it crashes as soon as you call boost::filesystem::exists in the ctor of a static variable initialized at program startup https://svn.boost.org/trac10/ticket/12987 Looks like there was a fix 4 month ago but this hasn't been pushed into the trunk yet Any idea how to push the process forward ? Thanks ! -- Olivier Tristan Research & Development www.uvi.net

2 2

Reconnecting a SSL socket correctly
by David Demelier 18 Oct '17

18 Oct '17

Hello, I'm trying to reconnect a SSL socket (using ssl::stream with tcp::socket) that has been closed only remotely. It looks like a shutdown on my client causes "stream truncated" error so I have no idea how can I connect my client socket again. I was thinking of just creating a new instance but the stream class is not copyable. Do you have any recommandations? Regards, -- David

2 1

[asio] null reference in epoll_reactor
by Phil Sean 18 Oct '17

18 Oct '17

Hi, Running the tutorial async TCP server (http://www.boost.org/doc/libs/1_65_1/doc/html/boost_asio/tutorial/tutdaytim…) or any other asynchronous operation in valgrind yields an error like this: = Syscall param epoll_pwait(sigmask) points to unaddressable byte(s) = epoll_pwait (in /usr/lib/libc-2.26.so) = boost::asio::detail::epoll_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) (in /.../server) = boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) (in /.../server) = boost::asio::detail::task_io_service::run(boost::system::error_code&) (in /.../server) = boost::asio::io_service::run() (in /.../server) = main (in /.../server) = Address 0x0 is not stack'd, malloc'd or (recently) free'd I suspect it's due to some recent changes because it didn't use to be an error. Boost version is 1.65.1(Arch Linux). Thank you.

2 2

git clone of boost
by Tim Burgess 18 Oct '17

18 Oct '17

Hi, Just been trying to find the address to clone boost, but was unsuccessful. Can anybody help me out please? Best wishes. Tim Burgess

2 1

Re: [Boost-users] Many undefined references for libboost_filesystem
by Mahmood N 17 Oct '17

17 Oct '17

Hi Daniel, I tried some other versions based on the release date of the project and boosts. I tried 1.38 and 40 and 42 and 44 and 46. All of them return some undefined references. How can i find which boost version is used in the project? Regards, Mahmood -------------------------------------------- On Sat, 10/14/17, Daniel Anderson <wonixen(a)gmail.com> wrote: Subject: Re: [Boost-users] Many undefined references for libboost_filesystem To: boost-users(a)lists.boost.org Cc: "Mahmood N" <nt_mahmood(a)yahoo.com> Date: Saturday, October 14, 2017, 12:53 AM you are probably using the wrong version of filesystem, or maybe of boost. often those projects need a specific boost version. 2017-10-13 14:24 GMT-04:00 Mahmood N via Boost-users <boost-users(a)lists.boost.org>: > Hi, > > I am trying to build a suite as described at > https://github.com/gpgpu-sim/ispass2009-benchmarks > > Some of the benchmarks use boost. For example, AES/Makefile has > > > > LINKFLAGS := -L$(BOOST_LIB) -lboost_filesystem > > > > Also, the Makefile.ispass-2009 in the root folder has the following settings > > > > SETENV=export BINDIR=$(BINDIR); \ > > export ROOTDIR=$(NVIDIA_COMPUTE_SDK_LOCATION)/C/src/; \ > > export BINSUBDIR=$(BINSUBDIR); \ > > export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; \ > > export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; \ > > export BOOST_VER=""; \ > > export OPENMPI_BINDIR=/usr/bin/; > > > > > > I manually built boost_1_46_0 with the steps described at > http://www.boost.org/doc/libs/1_46_1/doc/html/bbv2/installation.html > > The installations was successful and I can see lib/ and include/ folders > > > > mahmood@vb:boost_1_46_0$ find lib -name libboost_system* > > lib/libboost_system.so.1.46.0 > > lib/libboost_system.so > > lib/libboost_system.a > > mahmood@vb:boost_1_46_0$ find lib -name libboost_filesystem* > > lib/libboost_filesystem.so > > lib/libboost_filesystem.a > > lib/libboost_filesystem.so.1.46.0 > > > > > > > > However, as I run “make -f Makefile.ispass-2009”, I get many undefined > errors about libboost_filesystem. Please see below > > > > > > > > export > BINDIR=/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/; > export ROOTDIR=/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src/; export > BINSUBDIR=release; export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; export > BOOST_ROOT=/home/mahmood/boost_1_46_0/include; export BOOST_VER=""; export > OPENMPI_BINDIR=/usr/bin/; make noinline=0 -C AES > > make[1]: Entering directory > `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `readFromFileForm(boost::filesystem3::path&, std::vector<unsigned int, > std::allocator<unsigned int> >&)': > > aesCudaUtils.cpp:(.text+0x97d): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `readFromFileNotForm(boost::filesystem3::path&, char*, unsigned int)': > > aesCudaUtils.cpp:(.text+0xe81): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `getFileSize(boost::filesystem3::path&)': > > aesCudaUtils.cpp:(.text+0x1244): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > aesCudaUtils.cpp:(.text+0x1257): undefined reference to > `boost::filesystem3::detail::file_size(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `initAesCuda(std::basic_string<char, std::char_traits<char>, > std::allocator<char> >, unsigned char*, unsigned int, > std::basic_string<char, std::char_traits<char>, std::allocator<char> >, > char*, unsigned int)': > > aesCudaUtils.cpp:(.text+0x1c54): undefined reference to > `boost::filesystem3::path::wchar_t_codecvt_facet()' > > aesCudaUtils.cpp:(.text+0x1cab): undefined reference to > `boost::filesystem3::path::wchar_t_codecvt_facet()' > > aesCudaUtils.cpp:(.text+0x1ce5): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > aesCudaUtils.cpp:(.text+0x1d02): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `_GLOBAL__sub_I_aesCudaUtils.cpp': > > aesCudaUtils.cpp:(.text.startup+0x2b): undefined reference to > `boost::system::generic_category()' > > aesCudaUtils.cpp:(.text.startup+0x37): undefined reference to > `boost::system::generic_category()' > > aesCudaUtils.cpp:(.text.startup+0x43): undefined reference to > `boost::system::system_category()' > > obj/x86_64/release/aescuda.cpp.o: In function `_GLOBAL__sub_I_aescuda.cpp': > > aescuda.cpp:(.text.startup+0x68b): undefined reference to > `boost::system::generic_category()' > > aescuda.cpp:(.text.startup+0x697): undefined reference to > `boost::system::generic_category()' > > aescuda.cpp:(.text.startup+0x6a3): undefined reference to > `boost::system::system_category()' > > collect2: ld returned 1 exit status > > make[1]: *** > [/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin//release/AES] > Error 1 > > make[1]: Leaving directory > `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' > > make: *** [default] Error 2 > > > > > > > > Any thought on that? > > > Regards, > Mahmood > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users -- Daniel L'action accède à la perfection quand, bien que vivant, vous êtes déjà mort Bunan

6 14

Many undefined references for libboost_filesystem
by Mahmood N 13 Oct '17

13 Oct '17

Hi, I am trying to build a suite as described at https://github.com/gpgpu-sim/ispass2009-benchmarks Some of the benchmarks use boost. For example, AES/Makefile has LINKFLAGS := -L$(BOOST_LIB) -lboost_filesystem Also, the Makefile.ispass-2009 in the root folder has the following settings SETENV=export BINDIR=$(BINDIR); \ export ROOTDIR=$(NVIDIA_COMPUTE_SDK_LOCATION)/C/src/; \ export BINSUBDIR=$(BINSUBDIR); \ export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; \ export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; \ export BOOST_VER=""; \ export OPENMPI_BINDIR=/usr/bin/; I manually built boost_1_46_0 with the steps described at http://www.boost.org/doc/libs/1_46_1/doc/html/bbv2/installation.html The installations was successful and I can see lib/ and include/ folders mahmood@vb:boost_1_46_0$ find lib -name libboost_system* lib/libboost_system.so.1.46.0 lib/libboost_system.so lib/libboost_system.a mahmood@vb:boost_1_46_0$ find lib -name libboost_filesystem* lib/libboost_filesystem.so lib/libboost_filesystem.a lib/libboost_filesystem.so.1.46.0 However, as I run “make -f Makefile.ispass-2009”, I get many undefined errors about libboost_filesystem. Please see below export BINDIR=/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/; export ROOTDIR=/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src/; export BINSUBDIR=release; export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; export BOOST_VER=""; export OPENMPI_BINDIR=/usr/bin/; make noinline=0 -C AES make[1]: Entering directory `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' obj/x86_64/release/aesCudaUtils.cpp.o: In function `readFromFileForm(boost::filesystem3::path&, std::vector<unsigned int, std::allocator<unsigned int> >&)': aesCudaUtils.cpp:(.text+0x97d): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `readFromFileNotForm(boost::filesystem3::path&, char*, unsigned int)': aesCudaUtils.cpp:(.text+0xe81): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `getFileSize(boost::filesystem3::path&)': aesCudaUtils.cpp:(.text+0x1244): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' aesCudaUtils.cpp:(.text+0x1257): undefined reference to `boost::filesystem3::detail::file_size(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `initAesCuda(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, unsigned char*, unsigned int, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, char*, unsigned int)': aesCudaUtils.cpp:(.text+0x1c54): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' aesCudaUtils.cpp:(.text+0x1cab): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' aesCudaUtils.cpp:(.text+0x1ce5): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' aesCudaUtils.cpp:(.text+0x1d02): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `_GLOBAL__sub_I_aesCudaUtils.cpp': aesCudaUtils.cpp:(.text.startup+0x2b): undefined reference to `boost::system::generic_category()' aesCudaUtils.cpp:(.text.startup+0x37): undefined reference to `boost::system::generic_category()' aesCudaUtils.cpp:(.text.startup+0x43): undefined reference to `boost::system::system_category()' obj/x86_64/release/aescuda.cpp.o: In function `_GLOBAL__sub_I_aescuda.cpp': aescuda.cpp:(.text.startup+0x68b): undefined reference to `boost::system::generic_category()' aescuda.cpp:(.text.startup+0x697): undefined reference to `boost::system::generic_category()' aescuda.cpp:(.text.startup+0x6a3): undefined reference to `boost::system::system_category()' collect2: ld returned 1 exit status make[1]: *** [/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin//release/AES] Error 1 make[1]: Leaving directory `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' make: *** [default] Error 2 Any thought on that? Regards, Mahmood

2 1

[coroutine] MinGW: terminate called after throwing an instance of 'boost::context::detail::forced_unwind'
by Jan Niklas Hasse 13 Oct '17

13 Oct '17

Hi :) I've tried to compile this simple Boost.Coroutine example: #include <iostream> #include <boost/coroutine2/all.hpp> void foo(boost::coroutines2::asymmetric_coroutine<void>::push_type& yield) { for (int i = 0; i < 10; ++i) { std::cout << i << std::endl; yield(); } } int main() { boost::coroutines2::asymmetric_coroutine<void>::pull_type coroutine(foo); for (int i = 0; i < 5; ++i) { coroutine(); } } On Linux this works as expected, just as on Windows with Visual Studio. But when I cross-compile on Linux using i686-w64-mingw32-g++ src/main.cpp -lboost_context-mt The resulting exe crashes with: 0 1 2 3 4 5 6 terminate called after throwing an instance of 'boost::context::detail::forced_unwind' abnormal program termination There's a similar problem on StackOverflow: https://stackoverflow.com/questions/45569418/how-to-use-boost-context-corre… But I'm having the crash only with the cross-compiled version, not MSVC. Am I doing something wrong? Or might this be a bug in Fedora's mingw32-boost package?

1 0

1.65.1 as modular packages on Conan.io
by Rene Rivera 13 Oct '17

13 Oct '17

Following on with the announcement before CppCon of the 1.64.0 modular packages here we are with more. I'm pleased to announce that the 1.65.1 Boost C++ Libraries are now available individually using the Conan package manager. There's even some improvements for the 1.64.0 package also :-) Find out more from the Bincrafters post here <http://bit.ly/2g6VEpp>[1]. For help using the packages you can bug the Bincrafters team in the #Conan CppLan Slack channel <http://bit.ly/2ykeqC0>[2]. Conan is a C/C++ (and more) package manager that supports an open ended set of build system and tool integrations including: VisualStudio, Xcode, CLion, Ninja, QMake, Premake, and yes even CMake <http://bit.ly/2xzhpbg>[3]. [1] <https://bincrafters.github.io/2017/10/13/Conan-Packages-Boost-1-65-1/> [2] <https://cpplang.now.sh/> [3] <http://docs.conan.io/en/latest/integrations.html> -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net

1 0

boost::filesystem and writing to Windows programdata structure
by Tim Burgess 12 Oct '17

12 Oct '17

Hi, I've an application that has been working fine under Windows 7, but I'm now fixing up for running on later Windows versions. I've been hitting unhandled exceptions when writing to c:\programdata\(my company)\(my app name)\ and understand that this is due to the permissions for such folders being more restrictive on Windows 8, 8.1 and 10. My research seems to indicate that I can modify my installer to set up my folders with appropriate permissions at install-time, but I'd prefer to use boost::filesystem to check folder/file permissions then change them at run-time, if necessary using appropriate csidl values. Can anybody offer any advice, please? Best wishes. Tim Burgess

4 5

[stacktrace] Trace information from GetExceptionInformation()?
by Nat Goodspeed 11 Oct '17

11 Oct '17

In an __except() filter expression (Microsoft Structured Exception), it's legal to call GetExceptionInformation() to retrieve a pointer to an _EXCEPTION_POINTERS struct. A little bit of Google searching turned up a few recipes for walking the stack information indirectly provided by that _EXCEPTION_POINTERS data. Would it be reasonable to have a Microsoft-specific stacktrace constructor accepting _EXCEPTION_POINTERS*? Or perhaps a factory function? I would like to be able to capture the platform-specific _EXCEPTION_POINTERS information, but then, once I have it in hand, engage the rest of the Boost.Stacktrace functionality. Apologies if this has already been asked and answered. If so, please simply point me to the previous discussion. Thank you!

2 1

boost::interprocess::managed_mapped_file filename
by Markus Bonk 10 Oct '17

10 Oct '17

Hi, Unfortunately wmanaged_mapped_file constructors use char instead of wchar for the filename. This causes big problems on windows where %appdata% and %localappdata% include the user name which may include Unicode characters that after conversion result in the windows ‘A’ methods failing to find the referenced file. I don’t know of any work around except using Unicode filenames. Does anyone know of a way around this. Are there any plans of making wmanaged_mapped_file use wchar for the filenames? Markus ________________________________ Markus Bonk Senior Software Engineer [cid:imageac7178.GIF@91f798f8.4ca4a8b2] 3Dconnexion GmbH Clarita-Bernhard-Str. 18 81249 München Germany Tel: +49 (89) 897 45 42 - 70 Fax: +49 (89) 897 45 42 - 50 markus_bonk(a)3dconnexion.com<mailto:markus_bonk@3dconnexion.com> www.3dconnexion.com<http://www.3dconnexion.com> Geschäftsführer: Antonio Pascucci Sitz der Gesellschaft: München Registergericht: München HRB 99232

1 0

Compiling boost with optional _GLIBCXX_DEBUG support
by Jayesh Badwaik 09 Oct '17

09 Oct '17

Hi, How to compile boost so that compilation of user programs both with _GLIBCXX_DEBUG and without _GLIBCXX_DEBUG is supported? Currently, if I compile boost with _GLIBCXX_DEBUG then I cannot compile my programs without this flag, and vice versa. The actual error comes from program_options attached in a file. I gather from the interweb that the error is well known, however, I could not find instructions to compile boost such that both options are supported. -- Cheers Jayesh Badwaik https://www.jayeshbadwaik.in

2 2

[review] The review period of Boost.DoubleEnded has ended -- thanks to all involved
by Thorsten Ottosen 09 Oct '17

09 Oct '17

Dear users and members of Boost, We are now done with the review of Benedek Thaler's Boost.DoubleEnded library. Many thanks to all those involved in discussions and reviews. It will take me some time to digest all the feedback and get back with the review results. kind regards Thorsten, review manager -- Best regards, Thorsten Jørgen Ottosen, Ph.D. Director of Research +45 23308797 Dezide (www.dezide.com)

1 0

[asio] "reverse" stream?
by Phil Sean 07 Oct '17

07 Oct '17

Hi, Is there a stream (or other implementation) in asio that reverses the next layer and the read()/write() layer of another stream? For example, a reverse ssl::stream would send/receive data in clear text, but read()/write() operations should rather expect encrypted data. Thanks.

2 1

[geometry] Best Fit Plane
by Manoj Lnu 07 Oct '17

07 Oct '17

Is there a function available in boost geometry to find the best fit plane ? I have a set of 3D points as input. Thanks, Manoj

2 1

Memory usage of boost::unordered_multimap and boost::unordered_multimap
by Ram 06 Oct '17

06 Oct '17

Hi, I need help in determining the amount of memory used by boost::unordered_multimap and boost::unordered_multimap. We have a large code base and we have some optimizations done using boost::unordered_multimap and boost::unordered_multimap. The speed it really good, but we want to measure the amount of space it is occupying. Can somebody please help with that? I would not be able to change to use a custom new/delete. Thanks

3 5

Why no mpl::_double?
by Florian Lindner 06 Oct '17

06 Oct '17

Hello, is there a reason why there are only integral types in the boost MPL, no double or alike? http://www.boost.org/doc/libs/1_65_1/libs/mpl/doc/refmanual/numeric.html What is the best way to achieve: template<> struct getArg<Multiquadrics> : boost::mpl::double_<1e-3> {}; so that it is compatible with mpl::list? besides just writing the struct myself :-) Thanks, Florian

1 0

[stacktrace] Test failures with Xcode 9
by Nat Goodspeed 06 Oct '17

06 Oct '17

I've just started building Boost 1.65.1 Stacktrace. On Mac with Xcode 9, I'm dismayed that it has failed a couple of its own self-tests. Lengthy (albeit snipped) output follows. darwin.compile.c++ bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o "g++" -O3 -Wall -pedantic -g -dynamic -gdwarf-2 -fexceptions -Wno-long-long -Wno-inline -fPIC -arch x86_64 -DBOOST_STACKTRACE_GNU_SOURCE_NOT_REQUIRED -O3 -fPIC -gdwarf-2 -stdlib=libc++ -mmacosx-version-min=10.9 -iwithsysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/ -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 -DNDEBUG -DPIC -DLL_DARWIN=1 -DLL_OS_DRAGDROP_ENABLED=1 -DCARES_STATICLIB -DLIB_NDOF=1 -Wno-c99-extensions -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-variadic-macros -std=c++14 -DBOOST_ALL_NO_LIB=1 -DBOOST_STACKTRACE_USE_ADDR2LINE -DNDEBUG -I"." -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include" -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include/zlib" -c -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o" "libs/stacktrace/test/test.cpp" darwin.compile.c++ bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o "g++" -O3 -Wall -pedantic -g -dynamic -gdwarf-2 -fexceptions -Wno-long-long -Wno-inline -fPIC -arch x86_64 -DBOOST_STACKTRACE_GNU_SOURCE_NOT_REQUIRED -O3 -fPIC -gdwarf-2 -stdlib=libc++ -mmacosx-version-min=10.9 -iwithsysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/ -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 -DNDEBUG -DPIC -DLL_DARWIN=1 -DLL_OS_DRAGDROP_ENABLED=1 -DCARES_STATICLIB -DLIB_NDOF=1 -Wno-c99-extensions -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-variadic-macros -std=c++14 -DBOOST_ALL_NO_LIB=1 -DBOOST_STACKTRACE_USE_ADDR2LINE -DNDEBUG -I"." -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include" -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include/zlib" -c -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o" "libs/stacktrace/test/test_impl.cpp" darwin.link bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho "g++" -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o" -g -Wl,-dead_strip -no_dead_strip_inits_and_terms -arch x86_64 testing.capture-output bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.run status=0 if test $status -ne 0 ; then echo Skipping test execution due to testing.execute=off exit 0 fi "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho" > "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" 2>&1 < /dev/null status=$? echo >> "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" echo EXIT STATUS: $status >> "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" if test $status -eq 0 ; then cp "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.run" fi verbose=0 if test $status -ne 0 ; then verbose=1 fi if test $verbose -eq 1 ; then echo ====== BEGIN OUTPUT ====== cat "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" echo ====== END OUTPUT ====== fi exit $status ====== BEGIN OUTPUT ====== ... 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 14# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 15# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 16# void test_nested<15ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 17# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho libs/stacktrace/test/test.cpp(200): test 'min_size > 2' failed in function 'void test_frame()' ' 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 300# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 301# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 302# void test_nested<300ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 303# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ' 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 300# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 301# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 302# void test_nested<300ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 303# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho libs/stacktrace/test/test.cpp(282): test 'boost::stacktrace::stacktrace(1, 1).size() == 1' failed in function 'int main()' 2 errors detected. EXIT STATUS: 1 ====== END OUTPUT ======

1 3

[Units]
by CD Clark 06 Oct '17

06 Oct '17

I am trying to create a set of units to use in a library, but I having trouble getting IO to work for some of them. Here is a simple example that demonstrates the problem. ============================ #include<iostream> #include <boost/units/systems/si.hpp> #include <boost/units/systems/si/io.hpp> using namespace boost::units; // short hand for meter namespace t { typedef si::length m; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m, t::m ); } // centimeter namespace t { typedef make_scaled_unit< si::length, scale< 10, static_rational<-2> > >::type cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( cm, t::cm ); } // meter squared namespace t { typedef multiply_typeof_helper< m, m>::type m_m; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m_m, t::m_m ); } // centimeter squared namespace t { typedef multiply_typeof_helper< cm, cm>::type cm_cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( cm_cm, t::cm_cm ); } // meter centimeter namespace t { typedef multiply_typeof_helper< m, cm>::type m_cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m_cm, t::m_cm ); } // override default output, which prints "c(m^2)" namespace boost { namespace units { inline std::string name_string(const t::m_cm&) { return "meter centimeter"; } inline std::string symbol_string(const t::m_cm&) { return "m cm"; } } } // trying to overload output for centimeter squared namespace boost { namespace units { inline std::string name_string(const t::cm_cm&) { return "centimeter squared"; } inline std::string symbol_string(const t::cm_cm&) { return "cm^2"; } } } int main(int argc, char *argv[]) { std::cout << i::m << std::endl; std::cout << i::cm << std::endl; std::cout << i::m_m << std::endl; std::cout << i::m_cm << std::endl; //std::cout << i::cm_cm << std::endl; // this won't compile quantity<t::m_m> a1(100*i::cm_cm); std::cout << a1<< std::endl; // should be 0.01 m^2 quantity<t::m_m> a2(100*i::m_cm); std::cout << a2<< std::endl; // should be 1 m^2 return 0; } ============================ Basically, I am just trying to create a convenient set of short hands. Unit types are put in a 't' namespace and instances are put in a 'i' namespace with the same name. This works fine for doing calculations and conversions with the units, but I am having trouble with getting output to work for some of them. In the example above I create a centimeter unit by scaling the meter. Then I create three different area units with the product_typeof_helper struct: meter squared, meter centimeter, and centimeter squared. Conversions work for all three of these, but output will not work for the centimeter squared unit. The program above outputs m cm m^2 m cm 0.01 m^2 1 m^2 If I uncomment the line that tries to print i::cm_cm it won't compile. I get an error that says 'symbol' is not a member of ... and points at a line that says str += Begin::item::symbol() I can't understand why it doesn't work for a product of two scaled units. cdclark

2 4

Re: [Boost-users] boost::process
by Chris Rodgers 05 Oct '17

05 Oct '17

To answer my own question - this is one working possibility using boost::process::extend... #include <boost/process.hpp> #include <boost/process/extend.hpp> int main() { boost::filesystem::path myPath(".........toRun.exe......."); auto set_own_window = [](auto & exec) { exec.creation_flags |= boost::detail::winapi::CREATE_NEW_CONSOLE_; std::cerr << "in set_own_window" << std::endl; /* just for debugging */ }; bp::child c(myPath, "argument1", boost::process::extend::on_setup=set_own_window); return 0; } This works. Is it the right approach, or is there a better way? Best wishes, Chris. On 05/10/2017 17:14, Chris Rodgers wrote: > Hi, > > I'm trying to use Boost 1.65.1's boost::process::child in a Windows > console program. > > At the moment, the child process is launched in the same console window > as the parent. > > Is there an option to make a new console window for the child? > > The pre-boost-incorporation version of boost::process seemed to allow > manipulation of the startupInfo struct directly (e.g. > https://stackoverflow.com/questions/43582022/boostprocess-hide-console-on-w…) > and then a win32_launch call. But this seems to have been removed now? > > Any tips gratefully received. > > Thanks, > > Chris. >

1 0

PolyCollection requiring copyable
by d3fault 05 Oct '17

05 Oct '17

I'm impressed with PolyCollection. I use the list<interface*> strategy tons in my projects, and I didn't think NOT using a pointer there was even possible... but somehow you managed. It also makes sense why PolyCollection is faster to execute etc, the tutorial was well written. The only 'con' is that it requires a copy constructor. You mention later that some copy traits thing can be used to move the "copy code" outside of the class, but I am questioning the need for copying altogether. Is "copying" of the polymorphic types necessary for: a) Technical requirement otherwise it wouldn't compile b) Design decision because you think it's superior and helpful c) To facilitate copying of the PolyCollection object itself ....? If (b) or (c), can there be a slightly altered version of PolyCollection which does not allow/require copying? I'm completely fine (and even happier) _not_ being able to copy the PolyCollection. When I use the list<interface*> strategy, I tend to consider the list to be the owner of it's objects (and delete them when the list is deleted). There should be PolyCollection::emplace and the poly instances should "live" in the PolyCollection. Accessing the poly instances should be by [const] reference only (isn't this already the case? what benefit does the copy constructor bring?!?). I didn't examine the source so maybe it's (a) after all, in which case I apologize for wasting precious time, bandwidth, and disk space. d3fault

5 11

boost::process
by Chris Rodgers 05 Oct '17

05 Oct '17

Hi, I'm trying to use Boost 1.65.1's boost::process::child in a Windows console program. At the moment, the child process is launched in the same console window as the parent. Is there an option to make a new console window for the child? The pre-boost-incorporation version of boost::process seemed to allow manipulation of the startupInfo struct directly (e.g. https://stackoverflow.com/questions/43582022/boostprocess-hide-console-on-w…) and then a win32_launch call. But this seems to have been removed now? Any tips gratefully received. Thanks, Chris.

1 0

looking for a memory leak in an asio based application
by David Medine 05 Oct '17

05 Oct '17

I know that the answer to this question is /always/ 'no'. But is it possible, just possible that one can leak memory out of boost::asio? Let me explain. I work on an open source client/server data streaming library for multi-modal data streaming called labstreaminglayer (https://github.com/sccn/labstreaminglayer) At the core of the data transmission architecture is boost::asio. Now, to avoid calling collisions, the original author of the library shipped the source code with a name-mangled version of boost. Over the years this has yet to be updated so we are still relying on boost 1.57. The memory leak starts on the server side after a client is connected to it. This went undetected for years because it is very very slow and it depends on the sampling rate of the data stream. LSL (labstreaminglayer) is widely used in the neurophysiological research community (for whom the tool was intended), but normally in that field you are not sending samples faster than 500 Hz or so. But some devices are now available that offer relatively high sampling rates (e.g. Brain Products' actiCHamp can go as fast as 100kHz). The amount of memory that leaks seems to depend on how often data is sent, not how much data is send at a time. So, when the data is flowing quickly, the leak is severe. I am 99.99% sure that the allocation of memory for all the data I am sending is getting deallocated correctly. I don't see any leaking memory according to Visual Studio's diagnostic tools, nor can Deleaker spot anything. However, when I look at a server process in task manager, I can see the memory rising. I tried the asio::io_service::work trick (https://stackoverflow.com/questions/32258890/c-boost-asio-async-send-to-mem…) on my io_services, but this didn't have any effect. I have not gone through the whole pipeline yet, but I've been at this for two harrowing days already. So I just thought I would ask the list if anyone has seen anything like this before or if there has been any slow-leak fixes in boost (particularly asio) since 1.57 (I didn't see anything in the logs, but maybe I missed something). Due to the state of the project at this moment, it is non-trivial to update the name-mangled boost to another version, but it is far less trivial than the needle-in-a-haystack game I am playing right now. So, if someone can say with authority a boost update will fix everything I'll just do that and be happy. It's a long-shot, I know.

2 1

Bost Logging
by Mário Costa 04 Oct '17

04 Oct '17

Hi, I'm havving a bad time trying to figure out how to add and log custom keywords using boost/log. I havent been able to understand how exactly attribute keywords (BOOST_LOG_ATTRIBUTE_KEYWORD) bind with logging e.g. using BOOST_LOG_STREAM_WITH_PARAMS(logger, (??) (??)). For instance, if I define a keyword line_number, BOOST_LOG_ATTRIBUTE_KEYWORD(line_number, "LineNumber", unsigned int) and add it to the formmater logging::formatter formatter = expr::stream << "[" << line_number << "]" How do I use BOOST_LOG_STREAM_WITH_PARAMS(logger, (??)) Tanking an exemple from the severities, I should use a keyword parameter defining something like BOOST_PARAMETER_KEYWORD(sometag, line_number) then I should be able to use BOOST_LOG_STREAM_WITH_PARAMS(logger, (line_number = 10)) But those things just don add up together. I for sure missing the logics of the logging ... Thanks for any help! Cheers, mc

1 0

[geometry] Get points within certain radius?
by Florian Lindner 03 Oct '17

03 Oct '17

Hello, first of all thanks for the repliest to my previous geometry question! What is the best, especially fastest way to get all points within a certain radius of a point? Using the iterator method with nearest(pt, X) highly depends on X. Since I don't know this number, I have to guess it rather high. for (auto it = rtree.qbegin(bgi::nearest(point, results)) ; it != rtree.qend() ; ++it) { std::ignore = it; break; } results = 10 => time = 3.0s results = 100 => time = 22.6s results = 200 => time = 71.4s results = 300 => time = 153.2s though I always use just one result. The loop is inside another loop, not depending on results, so of course, the times are multiples of the actual times for that query. But clearly, choosing high numbers for results is not feasible. Another idea is to use the within() query with a circle of a radius. But bg seems to have no circle or sphere model. A workaround would be to use a box instead of a sphere. That means I have to test the results again, whether they are actually contained in th sphere. Alternatively, I could use the satisfies predicate. But wouldn't I give up all spatial information? This predicate needs to compare all vertices, don't it? It does include the knowledge, that when one point is discarded, all other points with a greater distance will discarded too. According to https://stackoverflow.com/questions/22909171/boostgeometry-nearest-neighbor…, the way to go seems to be to combine within(boundingBox) and satisfies(). Any other ideas? Thanks, Florian

2 1

[test] Is standalone use possible?
by Adam Nielsen 02 Oct '17

02 Oct '17

Hi all, I'm in the process of trying to remove the Boost dependency from my project, as it is causing too many difficulties for non-developers trying to run my code. This has been mostly solved by switching to C++11 and using the std:: implementations instead, however rather than rewrite all my unit tests I am hoping I can use a standalone version of Boost.Test, and distribute the code alongside my own. Unfortunately I am not quite sure how to extract the Test library out of the main Boost distribution. I have compiled "bcp" and used it to copy "test" into a new folder, but it seems to copy a huge chunk of Boost as well, including a bunch of libraries (system, thread, date_time, etc.) and I end up with 29 MB of source files, which seems wrong (especially considering my own codebase is barely 500 kB). Am I doing something wrong? I was hoping to use the header-only version of Boost.Test and this does seem to work when I #include the system-wide version of Boost (and don't link to any libraries), so it would seem that I don't need all those libraries that bcp copies. Is there any other way to access a slimmed-down standalone version of Boost.Test? Many thanks, Adam.

6 12

ק
by Ami Tavory 29 Sep '17

29 Sep '17

1 0

Enhancing the boost::asio::connect() socket interface
by martin doc 29 Sep '17

29 Sep '17

(apologies if this should be on -developers...) The connect() interface provided by boost caters to most common use and through access to the socket, various options can be managed without much hindrance. But there's one situation that boost does not handle well - when it is desirable to specify the local address to bind to. Going back to C, the usual program flow in this situation is something like this: fd = socket() bind(fd, local ip address) connect(fd, remote ip address) As boost::asio::connect() closes an open socket passed to it before making the remote connection, it's not possible to pass connect() a prebaked socket. In fact the amount of code required to use boost when binding a socket to a local address is more complicated than simply not using boost. What I'd like the boost community to consider is extending boost::asio to provide one or more variants of connect() that allows for a local endpoint (whether or not as an iterator I'll leave to others to debate but this isn't necessary - and then there's the M*N behavior or paired to decide) to be supplied in addition to the remote endpoint. I suppose I'm open minded as to whether or not the local address is supplied as an Iterator/endpoint as an extra arg or whether connect() is adopted to take endpoint pairs. Thoughts?

5 4

Analogous to DESTDIR for Boos installation
by Leo Cacciari 29 Sep '17

29 Sep '17

Hi, I need to prepare a binary distribution of Boost for deploying on company hosts. For this, I need to configure libraries with a prefix of say /usr/local, doing as per documentation ./bootstrap.sh --prefix=/some/path where /some/path is the actual path where the libraries and header flles will be installed on the various hosts. To prepare the package to be distributed (the actual packaging system used is irrelevant here, simply assuming a tar.gz would do) I need, however, to "install" everything under some other path, say /path/to/package/content. When using gnu packages, I usually do something like ./configure --prefix=/some/path make make DESTDIR=/path/to/package/content install and then I can prepare and distribute my package. I'm unable to find an analogous procedure for Boost. More exactly, I do not found a way to invoke the install phase of b2 with a different prefix than the one specified to the stage phase through the --prefix options to boostrap.sh I solved the problem in a unsatisfactory way by manually copying the files from both the source and the build directory to the content folder, but I'd really like to have an automated way to do it. Is this possible? If yes, how? And if not, does anyone have a better idea than manual copying? Thanks for the help -- Leo Cacciari Aliae nationes servitutem pati possunt. Populi Romani est propria libertas.

2 1

[review] The review period of Boost.DoubleEnded has been extended with one week. Now ends 7th of October.
by Thorsten Ottosen 28 Sep '17

28 Sep '17

Dear users and members of Boost, People have been requesting extra time for the review of Boost.DoubleEnded. We therefore continue one week extra, so the final date will be October the 7th. kind regards Thorsten Original review announcement ------------------------------------------ I'm proud to announce that the formal review of Benedek Thaler's Boost.DoubleEnded library starts today, September 21, and runs through September 30. This library is the result of Benedek's participation in Google Summer of Code 2015. The library may be downloaded from https://github.com/erenon/double_ended and the documentation may be found here: http://erenon.hu/double_ended/ Anyone is welcome to post a review and/or take part in subsequent discussions (see below for review guidelines). Introduction ------------ This is a container library that provides two containers: A. boost::devector B. boost::batch_deque Both containers provides efficient push_front and push_back operations, hence the name DoubleEnded. The boost::devector class can be seen as an extension of std::vector with efficient support for push_front (so boost::devector provides contiguous storage). In addition, it provides a customizable small buffer optimization like boost::small_vector(*). It furthermore allows for customization of the growth factor such that the user can decide if a reallocation should allocate 1.5 or 2 or whatever more memory. And finally it provides new functionality that does not exist in normal vector implementations -- this functionality allow the class to excel in performance in certain situations like serialization or transfer of data from sources that require a preallocated buffer. The boost::batch_deque is similar to std::deque, but with two important twists. Like std::deque, it provides reference stability when calling push_front/push_back. Reference stability is crucial for programs that uses intrusive containers e.g. using Boost.Intrusive (**). boost::batch_deque has the following main advantages: 1. It allows the user to specify the segment size 2. It allows for external iteration over the segments Taken together, they provide a very efficient and flexible basis for intrusive containers. Access to the segments also increases performance for tasks such as serialization. Finally, boost::batch_deque may be seen as an efficient alternative to std::vector if you want to replace a percent-wise memory overhead with a constant memory overhead and have no need for contiguous storage. Review guidelines ----------------- Please provide in your review whatever information you think is valuable to understand your final choice of ACCEPT or REJECT including Boost.DoubleEnded as a Boost library. Please be explicit about your decision. Some other questions you might want to consider answering: - 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 which compiler(s)? 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? More information about the Boost Formal Review Process can be found here: http://www.boost.org/community/reviews.html Kind regards Thorsten, Review manager (*) boost::small_vector: https://tinyurl.com/ycslp4ot (**) http://www.boost.org/doc/libs/1_64_0/doc/html/intrusive.html -- Best regards, Thorsten Jørgen Ottosen, Ph.D. Director of Research +45 23308797 Dezide (www.dezide.com)

1 0

[geometry] Runtime dimensionality
by Florian Lindner 28 Sep '17

28 Sep '17

Hello, I just started yesterday looking into boost.geometry to use on our own legacy system of Vertices (Points) in Meshes. I'm quite impressed how easy it is to adapt to existing code and got it working (with some workarounds) really quick. However, some problems remain. We have a Vertex object, with a dimension determined at runtime. The actual position is saved as VECTOR_T (usually an Eigen::VectorXd (double vector of arbitrary dimension)). One can get the coordinates using "const Eigen::VectorXd& Vertex::getNormal()" I was able to adapt to geometry by adding getters/setts for the dimensions: double getX() and getY() and BOOST_GEOMETRY_REGISTER_POINT_2D_GET_SET(mesh::Vertex, double, cs::cartesian, getX, getY, setX, setY) and it works! But in theory the vertices can be of arbitrary dimension, in practice it's usually 1, 2 or 3. What is the best way to adapt our Vertex object to geometry? - Change our Vertex so that it meets the model::point requirements. It worked so far, for the access I use: template<size_t Dimension> struct access<Vertex, Dimension> { static double get(Vertex const& p) { return p.getCoords()[Dimension]; } static void set(Vertex& p, double const& value) { Eigen::VectorXd vec = p.getCoords(); vec[Dimension] = value; p.setCoords(p); } }; In our code we rarely set the entries of an vector, so the code is a but ugly. Will likely change that to a compile-time get<Dim>() as a member of Vertex. My biggest problem is the dimensionality template<> struct dimension<Vertex> : boost::mpl::int_<2> {}; but I have no idea currently how to get that for an Eigen::VectorXd at compile-time? Do you have any idea? Thanks! Florian

5 8

Problem updating code to boost 1.64
by Tim Burgess 26 Sep '17

26 Sep '17

Hi, I have an application that I'm resurrecting. I originally coded it using Visual Studio 2010 with the boost that was current at the time (not sure what version that was). The following line of code used to build fine: if (CurrentAction[ 0].As <std::wstring>().compare( wstrFunctionName) == 0) With my current boost 1.64, I get the following error: >c:\users\tim\projects\surfacereader\screenreaderfunctionsdlg.cpp(146): error C2039: 'As': is not a member of 'boost::any' The intent of the code is as follows: If CurrentAction[ 0] (which is a boost::any) contains an std::wstring value, compare it to wstrFunctionName. Can anybody offer some guidance, please? Best wishes. Tim Burgess

2 1

[review][Fit] Review Results
by Matt Calabrese 24 Sep '17

24 Sep '17

Hello everyone, It is my privilege to announce that the Boost library count will once again be incremented as Paul Fultz II's library Fit has been accepted into Boost without conditions. Further details about this decision follow, but before that I'd like to thank Paul for all of the hard work he has put into Fit. Thanks also to everyone who participated in the review, with additional thanks to Vicente who was the review manager for the previous Fit review and who also provided a very detailed review and discussion during this review period. //////////////////////////////////////////////////////////////////////////////// Overview //////////////////////////////////////////////////////////////////////////////// Complete Reviews Considered: Zach Laine: Accept Vicente J. Botet Escriba: Accept John P. Fletcher: Accept Robert Ramey: Accept Jason Rice: Accept Barrett Adair: Accept Lee Clagett: Accept Glen Fernandes: Accept Louis Dionne: Accept Partial Reviews/Discussions Considered: Edward Diener Andrea Bocci Further Discussions (Previous Review): Steven Watanabe Peter Dimov Vladimir Batov Gavin Lambert Rob Stewart Bjorn Reese Manu Sanchez Artyom Beilis //////////////////////////////////////////////////////////////////////////////// Summary //////////////////////////////////////////////////////////////////////////////// Though not all responders reviewed every single aspect of the library, the reviews together adequately covered everything that is necessary for a decision to be made. This decision is made with additional confidence coming from usage of the library by some reviewers going back since during or before the initial review in early 2016. //////////////////////////////////////////////////////////////////////////////// Improvements Since Previous Review //////////////////////////////////////////////////////////////////////////////// This time around we received several more complete reviews than in the previous review period making it easier to be confident in a decision. A couple of notable changes since the 2016 review include: * Improved documentation * Default semantics for "capture" no longer try to determine whether to capture by reference or by value based on the argument being an lvalue or an rvalue (users can still get this via basic_capture) * Improved ADL awareness (internal calls are qualified) Throughout all of the discussions in this second review period, there were no explicit rejections of the library as a whole, though there were several recommendations from participants. A selection of those are listed here, though no changes are strictly required for acceptance: //////////////////////////////////////////////////////////////////////////////// Current Concerns //////////////////////////////////////////////////////////////////////////////// ////////// Design concerns: * Inheritance from user-callables has some potential pitfalls * Generated "infix" operators are "gimmicky" and don't add much value/may cause confusion * Placeholders should live in their own namespace ////////// Documentation concerns (not a complete list): * More examples requested * It is not always clear what files need to be #included for certain facilities in early examples * Better rationale for ConstFunctionObjects * Raw code is not linked from the examples ////////// Suggested name changes from reviewers: * Suggested rename of "partial()" to "partial_apply()" or "curry()" * Suggested rename of "conditional()" to "invoke_first()" or "call_first_of()" * Suggested rename of "apply" to "invoke" * Refer to "Callables" instead as "Invocables" (due to C++17 direction) * Library name "Fit" is not indicative of what it provides //////////////////////////////////////////////////////////////////////////////// Regarding the Author //////////////////////////////////////////////////////////////////////////////// Paul has been active in the Boost community for several years now. He is aware of his responsibilities going forward and I am confident that he will be a reliable maintainer for Fit for the foreseeable future (or whatever the library may be called). //////////////////////////////////////////////////////////////////////////////// Comments on the Name Boost.Fit //////////////////////////////////////////////////////////////////////////////// Note that what I say here is my personal opinion as a member of the community and does not necessarily reflect the opinions of others in the community nor of those in the steering committee. A few reviewers voiced that they would like to see a change of the library name "Fit". While multiple people did suggest this, my opinion is that this should be up to the author to choose whether or not he will change the name before it is added to boost and so I do not think it would be appropriate for us to strictly require or encourage such a change. If the author found the arguments against the name compelling, then he is welcome to change the name, but he should not feel obligated to do so. As a quick note on that, we have several high quality and highly regarded libraries in Boost with names that may not directly tell users what the library is for. Based on their popularity, I do not believe that it has significantly negatively affected their usage or ability to be found. A library name also may be important to an author as a creative outlet and I think it would be... poor form us to force such a change in this particular case and in other cases unless there are very strong reasons (i.e. the name is overly or intentionally misleading or there are legal concerns). I am not convinced that the current name is misleading enough to strictly require a change. As for existing precedent, some examples of libraries already in Boost with names that do not directly tell the user what the library is for include some of Boost's most highly regarded libraries such as Boost.Spirit (including Qi and Karma), Boost.Phoenix, Boost.Wave, Boost.Hana, and the recently accepted Boost.Beast. //////////////////////////////////////////////////////////////////////////////// Thanks again to everyone who participated in this review and in the previous review, and once again, congratulations to Paul on his library's acceptance into Boost. -- -Matt Calabrese -- -Matt Calabrese

1 0

[review] The review of Boost.DoubleEnded starts today: September 21 - September 30
by Thorsten Ottosen 21 Sep '17

21 Sep '17

Dear users and members of Boost, I'm proud to announce that the formal review of Benedek Thaler's Boost.DoubleEnded library starts today, September 21, and runs through September 30. This library is the result of Benedek's participation in Google Summer of Code 2015. The library may be downloaded from https://github.com/erenon/double_ended and the documentation may be found here: http://erenon.hu/double_ended/ Anyone is welcome to post a review and/or take part in subsequent discussions on the boost developer list (see below for review guidelines). Introduction ------------ This is a container library that provides two containers: A. boost::devector B. boost::batch_deque Both containers provides efficient push_front and push_back operations, hence the name DoubleEnded. The boost::devector class can be seen as an extension of std::vector with efficient support for push_front (so boost::devector provides contiguous storage). In addition, it provides a customizable small buffer optimization like boost::small_vector(*). It furthermore allows for customization of the growth factor such that the user can decide if a reallocation should allocate 1.5 or 2 or whatever more memory. And finally it provides new functionality that does not exist in normal vector implementations -- this functionality allow the class to excel in performance in certain situations like serialization or transfer of data from sources that require a preallocated buffer. The boost::batch_deque is similar to std::deque, but with two important twists. Like std::deque, it provides reference stability when calling push_front/push_back. Reference stability is crucial for programs that uses intrusive containers e.g. using Boost.Intrusive (**). boost::batch_deque has the following main advantages: 1. It allows the user to specify the segment size 2. It allows for external iteration over the segments Taken together, they provide a very efficient and flexible basis for intrusive containers. Access to the segments also increases performance for tasks such as serialization. Finally, boost::batch_deque may be seen as an efficient alternative to std::vector if you want to replace a percent-wise memory overhead with a constant memory overhead and have no need for contiguous storage. Review guidelines ----------------- Please provide in your review whatever information you think is valuable to understand your final choice of ACCEPT or REJECT including Fit as a Boost library. Please be explicit about your decision. Some other questions you might want to consider answering: - 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 which compiler(s)? 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? More information about the Boost Formal Review Process can be found here: http://www.boost.org/community/reviews.html Kind regards Thorsten, Review manager (*) boost::small_vector: https://tinyurl.com/ycslp4ot (**) http://www.boost.org/doc/libs/1_64_0/doc/html/intrusive.html

1 0

Linker error when using Boot regex on AIX
by Jyoti Sharma 18 Sep '17

18 Sep '17

I am using boost_1_61_0. In my code I have: #include <boost/regex.hpp> static boost::regex testxp("["); I have these libraries: libboost_regex.a libboost_regex.so I can see these libraries have symbols: LIBRARY: Shared object libboost_regex.so: 136 symbols imported. LIBRARY: Shared object libboost_system.so: 7 symbols imported. To build my program I have added these linking options: -Wl,-bnoquiet -Wl,-Bstatic -lboost_regex -lboost_system -Wl,-Bdynamic But I get this error during linking: ld: 0711-317 ERROR: Undefined symbol: .boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int) But that symbol is there: machine:/home> nm libboost_regex.so nm libboost_regex.so |grep do_assign ._ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE9do_assignEPKcS7_j T 268508592 machine:/home> c++filt ._ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE9do_assignEPKcS7_j .boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int)

2 3

Last Day for Boost Community Dinner Sign up
by Jon Kalb 18 Sep '17

18 Sep '17

Boost Users, Today is the last day to register for the Boost Community Dinner at CppCon. http://sched.co/Bhcr You do not need to be registered to attend CppCon to register for the Boost Community Dinner: https://cppcon.org/registration/ If you are going to be in the Seattle area a week from Tuesday, join us for a rare face-to-face get together of the Boost Community. See you there. Jon

1 0

[fiber] pooled_fixedsize_stack
by DePizzottri 14 Sep '17

14 Sep '17

Hi, I'm trying to replace fixedsize_stack with pooled_fixedsize_stack in my application witch spawns many fibers to reduce allocations, and got random crashes. For reproduction it is enough to replace fixedsize_stack with pooled_fixedsize_stack in performance\fiber\skynet_stealing_detach.cpp. Playing with stack size parameter does not help. Can anyone give some tip how to use pooled stack with fiber correctly? -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

3 5

Help trying to compile boost 1_65_1 on Windows (Visual Studio 2017) with LZMA filter support
by Diego Luna 12 Sep '17

12 Sep '17

Hello everyone, this is my first post. Like the subject says, I need some help compiling boost 1_65_1 on Windows (Visual Studio 2017) on 64 bits with LZMA filter support. I've been compiling boost on Windows and Linux for some time without any problems, but the LZMA support in Windows, caused me some problems. I've downloaded and compiled the LZMA lib (XZ utils from https://tukaani.org/xz/) producing static (lib) and shared(dll+lib) libraries, in release and debug variants, then I have written the following user config jam (I think the problem is in the syntax of the file): ########################################## ## Using Python 3.6 (64 bits). ## using python : 3.6 : C:\\APPS\\PROGRAMMING\\Python36-64\\python.exe : C:\\APPS\\PROGRAMMING\\Python36-64\\include : C:\\APPS\\PROGRAMMING\\Python36-64\\libs : <address-model>64 ; ## Using lzma library 5.2.3. ## ## using lzma : 5.2.3 : <name>liblzma <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>release <link>shared ; using lzma : 5.2.3 : <name>liblzmad <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>debug <link>shared ; using lzma : 5.2.3 : <name>liblzma_static <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>release <link>static ; using lzma : 5.2.3 : <name>liblzma_staticd <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>debug <link>static ; ########################################## The command line for the actual compiling (after bootstrap), (omitting the path to the other libraries for shortness, those are linked\compiled without any problem) is: .\b2 -j6 --user-config=.\user-config-64.jam --build-type=complete -q -sZLIB_SOURCE="%ZLIB_ROOT%" -sBZIP2_SOURCE="%BZIP2_ROOT%" -sICU_PATH="%ICU_LIB%" toolset=msvc-14.1 link="static,shared" threading=multi ^ variant="debug,release" architecture=x86 address-model=64 runtime-link=shared stage --debug-symbols=on --debug-store=database --debug-configuration -d2 The output is: notice: found boost-build.jam at E:/DATA/TMP/boost/boost_1_65_1/boost-build.jam notice: loading Boost.Build from E:/DATA/TMP/boost/boost_1_65_1/tools/build/src notice: Searching 'C:\WINDOWS' 'C:\Users\bakaneko' 'C:\APPS\TOOLS\UNIX-HOME' 'C:\Users\bakaneko' 'E:\DATA\TMP\boost\boost_1_65_1\tools/build/src' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/kernel' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/util' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/build' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/tools' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/contrib' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/.' for site-config configuration file 'site-config.jam'. notice: Configuration file 'site-config.jam' not found in 'C:\WINDOWS' 'C:\Users\bakaneko' 'C:\APPS\TOOLS\UNIX-HOME' 'C:\Users\bakaneko' 'E:\DATA\TMP\boost\boost_1_65_1\tools/build/src' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/kernel' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/util' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/build' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/tools' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/contrib' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/.'. notice: Loading explicitly specified user configuration file: E:\DATA\TMP\boost\boost_1_65_1\user-config-64.jam notice: Searching 'E:\DATA\TMP\boost\boost_1_65_1' for user-config configuration file 'user-config-64.jam'. notice: Loading user-config configuration file 'user-config-64.jam' from 'E:/DATA/TMP/boost/boost_1_65_1'. notice: [python-cfg] Configuring python... notice: [python-cfg] user-specified version: "3.6" notice: [python-cfg] user-specified cmd-or-prefix: "C:\APPS\PROGRAMMING\Python36-64\python.exe" notice: [python-cfg] user-specified includes: "C:\APPS\PROGRAMMING\Python36-64\include" notice: [python-cfg] user-specified libraries: "C:\APPS\PROGRAMMING\Python36-64\libs" notice: [python-cfg] user-specified condition: "<address-model>64" notice: [python-cfg] Checking interpreter command "C:\APPS\PROGRAMMING\Python36-64\python.exe"... notice: [python-cfg] running command 'DIR /-C /A:S "C:\APPS\PROGRAMMING\Python36-64\python.exe" 2>&1' notice: [python-cfg] running command 'C:\APPS\PROGRAMMING\Python36-64\python.exe -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1' notice: [python-cfg] ...requested configuration matched! notice: [python-cfg] Details of this Python configuration: notice: [python-cfg] interpreter command: "C:\APPS\PROGRAMMING\Python36-64\python.exe" notice: [python-cfg] include path: "C:\APPS\PROGRAMMING\Python36-64\include" notice: [python-cfg] library path: "C:\APPS\PROGRAMMING\Python36-64\libs" notice: [python-cfg] DLL search path: "C:\APPS\PROGRAMMING\Python36-64" notice: [python-cfg] Checking for NumPy... notice: [python-cfg] running command 'C:\APPS\PROGRAMMING\Python36-64\python.exe -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())"' notice: [python-cfg] NumPy enabled notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>shared <variant>release notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>shared <variant>debug notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>static <variant>release notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>static <variant>debug notice: Searching '.' for project-config configuration file 'project-config.jam'. notice: Loading project-config configuration file 'project-config.jam' from '.'. notice: [msvc-cfg] msvc-14.0 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl.exe' notice: [msvc-cfg] msvc-11.0 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\cl.exe' notice: [msvc-cfg] msvc-14.1 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.11.25503\bin\HostX64\arm\cl.exe' notice: will use 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.11.25503\bin\HostX64\arm\cl.exe' for msvc, condition <toolset>msvc-14.1 'notice: [generate-setup-cmd] 14.1 is 14.1' 'notice: [generate-setup-cmd] 14.1 is 14.1' 'notice: [generate-setup-cmd] 14.1 is 14.1' 'notice: [generate-setup-cmd] 14.1 is 14.1' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>32', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>32', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>64', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>64', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>ia64/<address-model>', setup: 'call "C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Auxiliary/Build/vcvarsall.bat" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>ia64/<address-model>64', setup: 'call "C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Auxiliary/Build/vcvarsall.bat" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_arm_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>32', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_arm_.cmd" >nul ' notice: [zlib] Building zlib from source as boost_zlib notice: [zlib] Condition notice: [zlib] found zlib source in C:\APPS\PROGRAMMING\LIBRARIES\zlib\src_inc notice: [bzip2] Building bzip from source as boost_bzip2 notice: [bzip2] Condition notice: [bzip2] found bzip source in C:\APPS\PROGRAMMING\LIBRARIES\bzip2\src notice: [lzma] Using pre-installed library notice: [lzma] Condition Performing configuration checks - 32-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes - symlinks supported : no - junctions supported : yes - hardlinks supported : yes - C++11 mutex : yes - Boost.Config Feature Check: cxx11_auto_declarations : yes - Boost.Config Feature Check: cxx11_constexpr : yes - Boost.Config Feature Check: cxx11_defaulted_functions : yes - Boost.Config Feature Check: cxx11_final : yes - Boost.Config Feature Check: cxx11_hdr_mutex : yes - Boost.Config Feature Check: cxx11_hdr_tuple : yes - Boost.Config Feature Check: cxx11_lambdas : yes - Boost.Config Feature Check: cxx11_noexcept : yes - Boost.Config Feature Check: cxx11_nullptr : yes - Boost.Config Feature Check: cxx11_rvalue_references : yes - Boost.Config Feature Check: cxx11_template_aliases : yes - Boost.Config Feature Check: cxx11_thread_local : yes - Boost.Config Feature Check: cxx11_variadic_templates : yes - icu (64-bit) : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - lzma : yes - iconv (libc) : no - iconv (separate) : no - native-atomic-int32-supported : yes - message-compiler : yes - native-syslog-supported : no - pthread-supports-robust-mutexes : no - compiler-supports-visibility : no - compiler-supports-ssse3 : yes - compiler-supports-avx2 : yes - gcc visibility : no - long double support : 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. - libbacktrace builds : no - addr2line builds : no - WinDbg builds : yes - WinDbgCached builds : yes - lzma : yes (cached) - lzma : yes - lzma : yes (cached) Component configuration: - atomic : building - chrono : building - container : building - context : building - coroutine : building - date_time : building - exception : building - fiber : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - metaparse : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - stacktrace : building - system : building - test : building - thread : building - timer : building - type_erasure : building - wave : building ...patience... ...patience... ...patience... ...patience... ...patience... ...found 29592 targets... ...updating 2728 targets... ... When the compiling is done the related libraries (iostream) are: boost_iostreams-vc141-mt-1_65_1.dll boost_iostreams-vc141-mt-1_65_1.lib boost_iostreams-vc141-mt-gd-1_65_1.dll boost_iostreams-vc141-mt-gd-1_65_1.lib libboost_iostreams-vc141-mt-1_65_1.lib libboost_iostreams-vc141-mt-gd-1_65_1.lib The problem is that both, "boost_iostreams-vc141-mt-gd-1_65_1.dll" and "boost_iostreams-vc141-mt-1_65_1.dll" were linked to the debug version of the LZMA dll (libzmad.dll), and examining the log, both "libboost_iostreams-vc141-mt-gd-1_65_1.lib" and "libboost_iostreams-vc141-mt-1_65_1.lib" were statically linked to the debug version of the static LZMA library (liblzma_staticd.lib). I tried with some more combinations in the user jam file, but without success, and in most cases failing to detect LZMA. If you require any further information to help find the problem, please, let me know, I'd appreciate any help with this problem. Sorry for my English, best regards, Diego. P.S: The config log can be found here: config.log <https://www.dropbox.com/s/kkut7kuka2jgi57/config.log?dl=0>.

1 0

Re: [Boost-users] [stacktrace] Getting a stacktrace from unhandled exception in windows
by Don 12 Sep '17

12 Sep '17

-------- Original Message -------- Subject: Boost-users Digest, Vol 4770, Issue 1 From: boost-users-request(a)lists.boost.org To: boost-users(a)lists.boost.org Date: 9/10/2017 10:56 PM > Subject: Re: [Boost-users] [stacktrace] Getting a stacktrace from unhandled exception in windows > From: Stian Zeljko Vrba <vrba(a)quine.no> > Date: 9/10/2017 10:54 PM > > Unless you need the stacktrace to be logged to a text file, I suggest you look at this system-provided >facility: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).… ><https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85…> > > ...> IOW, you can get out more information than with boost.stacktrace with zero coding. > >> *Sent:* Monday, September 11, 2017 1:27:47 AM >> *To:* boost-users(a)lists.boost.org >> *Subject:* [Boost-users] [stacktrace] Getting a stacktrace from unhandled exception in windows >>>> I am trying use boost stacktrace to get a stack dump when my program encounters an unhandled exception >> under windows. I have installed a signal handler as described in the stacktrace documentation, and it >> gets called. However, the resulting stack trace is after everything has been unwound. >> >> For example, when I force a failure by dereferenceing a null pointer many levels down in my function >> hierarchy, the stack trace shows: >> >> 0# boost::stacktrace::detail::this_thread_frames::safe_dump_to_impl<char const *> at f:\home\tools\boost\boost\stacktrace\safe_dump_to.hpp:68 >> 1# boost::stacktrace::safe_dump_to at f:\home\tools\boost\boost\stacktrace\safe_dump_to.hpp:120 >> 2# my_signal_handler at f:\home\test\main.cpp:233 >> 3# 0x5171407B >> 4# my_signal_handler at f:\home\test\main.cpp:235 >> 5# 0x51713883 >> 6# __tmainCRTStartup at f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c:603 >> 7# WinMainCRTStartup at f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c:403 >> 8# BaseThreadInitThunk in kernel32 >> 9# RtlInitializeExceptionChain in ntdll >> 10# RtlInitializeExceptionChain in ntdll >> >> This is not particularly helpful, of course -- I want to know the call stack at the point of the >> failure. Is there any way to get that? What am I missing? Thanks for the suggestion, but yes, I want to log the data to a log file. It seems from the stacktrace documentation that this should work. Don

1 0