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

BoostLog and BoostASIO don't seem to play nice together
by james 08 Oct '16

08 Oct '16

Hi, I'm facing pretty much the same issue as was reported here in 2014: http://boost.2283326.n4.nabble.com/Boostlog-and-ASIO-crash-in-shared-librar… In short, I have a .so that wraps BoostASIO to create a HTTP client. Loading this .so into a program that also uses BoostLog results in either a segfault or no callbacks being fired (even async_resolve which I believe should eventually time-out). Removing all uses of and linking to BoostLog in the main program makes it all work again. Before I try to produce a minimum example, is this a known issue? Code is built with BOOST_LOG_DYN_LINK, asio is header only. We're using boost 1.55, and g++ (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 Thanks James

1 0

graph strongly connected components
by Mika S 07 Oct '16

07 Oct '16

I am trying to use the implementation for strongly connected components http://www.boost.org/doc/libs/1_61_0/libs/graph/doc/strong_components.html Is this the iterative or the recursive implementation of tarjan's algorithm ?

2 2

GCC 5.3.0 failing Features Check when building Boost
by Carlos Ferreira 06 Oct '16

06 Oct '16

Hello I'm having some issues regarding the features check, when build Boost using OpenWRT GCC 5.3.0 cross-compiler for armv7. I'm building against musl. I have passed -std=c++14 to the cxxflags, but it seems to have no effect. This is the features output > - 32-bit : yes > - arm : yes > - symlinks supported : yes > - C++11 mutex : yes > - lockfree boost::atomic_flag : no > - Boost.Config Feature Check: cxx11_auto_declarations : no > - Boost.Config Feature Check: cxx11_constexpr : no > - Boost.Config Feature Check: cxx11_defaulted_functions : no > - Boost.Config Feature Check: cxx11_final : no > - Boost.Config Feature Check: cxx11_hdr_tuple : no > - Boost.Config Feature Check: cxx11_lambdas : no > - Boost.Config Feature Check: cxx11_noexcept : no > - Boost.Config Feature Check: cxx11_nullptr : no > - Boost.Config Feature Check: cxx11_rvalue_references : no > - Boost.Config Feature Check: cxx11_template_aliases : no > - Boost.Config Feature Check: cxx11_thread_local : no > - Boost.Config Feature Check: cxx11_variadic_templates : no > - has_icu builds : no > warning: Graph library does not contain MPI-based parallel components. > note: to enable them, add "using mpi ;" to your user-config.jam > - zlib : yes > - iconv (libc) : no > - iconv (separate) : yes > - icu : no > - icu (lib64) : no > - native-atomic-int32-supported : yes > - pthread-supports-robust-mutexes : yes > - compiler-supports-visibility : yes > - gcc visibility : yes > - long double support : yes > - zlib : yes What am I missing, so that all those cxx_* features can be checked? -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - cmf(a)av.it.pt Skype & GTalk -> carlosmf.pt(a)gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira

1 1

[regex] link error on upgrade to 1.62.0
by James Walker 05 Oct '16

05 Oct '16

Hi, I'm trying to update from 1.60.0 to 1.62.0 on Mac with Xcode 4.6.3, and I'm getting link errors on Regex. I am definitely compiling all 17 of the .cpp files in libs/regex/src. The errors are shown below. Any idea what I might be missing? Undefined symbols for architecture i386: "boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::construct_init(boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags)", referenced from: boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, char const*) in BVHJointMap.o boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, char const*) in AnimationsManager.o "boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::find()", referenced from: bool boost::regex_search<char const*, char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >(char const*, char const*, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags) in BVHJointMap.o "boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::match()", referenced from: bool boost::regex_match<char const*, std::allocator<boost::sub_match<char const*> >, char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags) in AnimationsManager.o ld: symbol(s) not found for architecture i386

1 1

boost::asio cross-library link issue
by Stanley Friesen 05 Oct '16

05 Oct '16

We are using Boost 1.54. The issue i have is a strange problem with the ASIO library. We have two libraries build using ASIO from Boost 1.54 (libpcl and one of our own libraries). For some reason, despite being built with the same version of boost, the layout of class task_io_service differs between the two libraries. The member function instantiations are in the libraries as weak symbols, so we do not get a link error, but which version of each function that is called from any given place is unpredictable, and varies when we change out own code. In particular, at least op_queue_ and all following members have offsets that differ by 8 bytes (the size of a 64-bit pointer) between the two builds. The result is that sometimes the op_queue back pointer is corrupted (by the other version setting stopped_), or the stop flag is not seen because it was set by the other build. The result is either that run() returns immediately without doing anything, or out application crashes from trying to dereference an invalid pointer. (Often what is supposed to be a NULL back pointer is set to 1, which does not compare equal to NULL). I have looked for conditionally compiled elements in task_io_service, op_queue, and epoll_reactor with no luck. I can see no reason the two library builds should end up with different class layouts. So, does anybody have any clue what might be happening here? Or how to go about fixing the problem? [I hesitate to try forcing strong symbols in our library, since this would break libpcl, due to many functions being inline]. -- View this message in context: http://boost.2283326.n4.nabble.com/boost-asio-cross-library-link-issue-tp46… Sent from the Boost - Users mailing list archive at Nabble.com.

5 8

Different checksums for different SourceForge locations
by Carlos Ferreira 05 Oct '16

05 Oct '16

I'm having some issues in downloading the Boost 1.62 package from the SF servers. It seems that the Eastern US servers checksum values are not matching the rest of the servers, nor the checksum values provided at the Boost.org website. Is there anyone else having the same problem? -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - cmf(a)av.it.pt Skype & GTalk -> carlosmf.pt(a)gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira

2 8

Need help with errors while building boost for clang on android NDK
by Robert Dailey 04 Oct '16

04 Oct '16

I'm using NDK r11 and I'm setting up project-config.jam to build boost using clang + llvm STL. I'm running into a few errors that I do not know how to solve. I will post my config file at the bottom. First problem is that boost does not know where to find tools 'ar' and 'ranlib': clang-linux.archive bin.v2\libs\container\build\clang-linux-android\release\link-static\runtime-link-static\target-os-linux\threading-multi\libboost_container-clang-mt-s-1_61.a '"ar"' is not recognized as an internal or external command, operable program or batch file. '"ranlib"' is not recognized as an internal or external command, operable program or batch file. How can I explicitly specify the NDK path to these executables? Second problem is related to some assembler stuff, I think. I get these errors while compiling boost thread: clang-linux.compile.asm bin.v2\libs\context\build\clang-linux-android\release\link-static\runtime-link-static\target-os-linux\threading-multi\asm\make_i386_ms_pe_gas.o libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:1: error: unknown directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:22: error: unknown directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:36: error: expected identifier in directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:40: error: unknown directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:136:1: error: unknown directive .def __exit; .scl 2; .type 32; .endef ^ How can I solve this? I have no idea at this point. I'm invoking the build using: b2 --without-python threading=multi link=static runtime-link=static toolset=gcc-android target-os=linux threadapi=pthread --stagedir=android stage And my project-config.jam looks like: import option ; option.set keep-going : false ; androidNDKRoot = E:/android/ndk ; androidAbiVer = 4.9 ; androidPlatform = windows-x86_64 ; using clang : android : $(androidNDKRoot)/toolchains/llvm/prebuilt/$(androidPlatform)/bin/clang++ : <compileflags>--sysroot=$(androidNDKRoot)/platforms/android-15/arch-arm <compileflags>-Os <compileflags>-fno-strict-aliasing <compileflags>-O2 <compileflags>-DNDEBUG <compileflags>-g <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++abi/libcxxabi/include <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++/libcxx/include <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a <compileflags>-I$(androidNDKRoot)/sources/android/support/include <compileflags>-DANDROID <compileflags>-D__ANDROID__ <compileflags>-D__arm__ <compileflags>-D_REENTRANT ;

3 8

boost::lockfree::queue::reserve fail with fixed_sized = true
by Sam Sigbjørn 04 Oct '16

04 Oct '16

Hello, When i compile lockfree::queue with option fixed_sized set to true i get a compilation error in reserve: void reserve(size_type n) { pool.template reserve<true>(n); } Btw, MSC version is 190024210 (Update 3) and i defined _ENABLE_ATOMIC_ALIGNMENT_FIX Thanks

1 0

[release] Boost 1.62.0 release available
by Rene Rivera 04 Oct '16

04 Oct '16

Release 1.62.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains two new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries * Fiber: Framework for userland-threads/fibers, from Oliver Kowalke. * QVM: Boost QVM is a generic library for working with quaternions, vectors and matrices of static size with the emphasis on 2, 3 and 4-dimensional operations needed in graphics, video games and simulation applications, from Emil Dotchevski. For details, including download links, see http://www.boost.org/users/ news/version_1.62.0 You can also download directly from SourceForge: http://sourceforge.net/ projects/boost/files/boost/1.62.0/ The SHA256 checksums are as follows: b91c2cda8bee73ea613130e19e72c9589e9ef0357c4c5cc5f7523de82cce11f7 boost_1_62_0.7z 36c96b0f6155c98404091d8ceb48319a28279ca0333fba1ad8611eb90afb2ca0 boost_1_62_0.tar.bz2 440a59f8bc4023dbe6285c9998b0f7fa288468b889746b1ef00e8b36c559dce1 boost_1_62_0.tar.gz 084b2e0638bbe0975a9e43e21bc9ceae33ef11377aecab3268a57cf41e405d4e boost_1_62_0.zip Tom Kent has made pre-built windows binaries, and they are available at: https://sourceforge.net/projects/boost/files/boost-binaries/1.62.0/ To install this release on your system, see http://www.boost.org/doc/libs/ release/more/getting_started/index.html Thanks, --The Boost release team

3 5

boost 1.62 msvc compilation error : regression from 1.61 ?
by Julien Schueller 04 Oct '16

04 Oct '16

Hello, I'm trying to update from boost 1.61 to 1.62 on msvc for conda and encountered this error: [00:03:41] Performing configuration checks [00:03:41] [00:03:41] - 32-bit : yes ... [00:03:41] - x86 : yes [00:03:41] - symlinks supported : yes [00:03:41] - C++11 mutex : no [00:03:41] - Boost.Config Feature Check: cxx11_auto_declarations : no ... [00:03:42] - has_icu builds : no ... [00:03:43] - zlib : yes [00:03:43] error: at C:/conda/conda-bld/work/boost_1_62_0/tools/build/src/kernel\modules.jam:107 [00:03:43] error: Name clash for '<pbuildboost\boost\bin.v2\standalone\ac\msvc-9.0\release\link-static\threading-multi>main.obj' [00:03:43] error: [00:03:43] error: Tried to build the target twice, with property sets having [00:03:43] error: these incompatible properties: [00:03:43] error: [00:03:43] error: - <dll-path>C:\conda\envs\_build\Library\lib <library-path>C:\conda\envs\_build\Library\lib <xdll-path>C:\conda\envs\_build\Library\lib [00:03:43] error: - none [00:03:43] error: [00:03:43] error: Please make sure to have consistent requirements for these [00:03:43] error: properties everywhere in your project, especially for install [00:03:43] error: targets. [00:03:43] [00:03:43] Command failed: cmd.exe /c bld.bat [00:03:43] Command exited with code 1 Full logs are available here: https://ci.appveyor.com/project/conda-forge/boost-feedstock/build/1.0.36 I've got the same error for vc9, vc10 and vc14 for both 32 and 64bits. I configure with the exact same script I used for 1.61, here's the configure part: call bootstrap.bat .\b2 install ^ --build-dir=buildboost ^ --prefix=%LIBRARY_PREFIX% ^ toolset=msvc-%VSTRING%.0 ^ address-model=%ARCH% ^ variant=release ^ threading=multi ^ link=static,shared ^ -j%CPU_COUNT% ^ -s ZLIB_INCLUDE="%LIBRARY_INC%" ^ -s ZLIB_LIBPATH="%LIBRARY_LIB%" It can be seen there: https://github.com/conda-forge/boost-feedstock/blob/master/recipe/bld.bat I've not seen it reported in the trac tickets, did someone get the same error ? -- J Schueller

1 0