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

Boost Asio support for OpenSSL 1.1.1
by Gehrs, Volker 14 Dec '20

14 Dec '20

Hi all, we are using boost.asio on windows. Does boost.asio support OpenSSL 1.1.1 in any new version? I could not find a hint in the Revision history of boost.asio. https://www.boost.org/doc/libs/1_75_0/doc/html/boost_asio/history.html Thanks in advance!

2 1

unresolved external symbol __DllMainCRTStartup@12
by Cruz, Petagay [USA] 13 Dec '20

13 Dec '20

I have built boost python. I am trying to use the boost_1_74_0\libs\python\example\tutorial example. I keep getting a fail in the build of the dll: msvc.link.dll bin\msvc-14.0\debug\boost_python.dll LINK : warning LNK4001: no object files specified; libraries used LINK : error LNK2001: unresolved external symbol __DllMainCRTStartup@12 bin\msvc-14.0\debug\boost_python.dll : fatal error LNK1120: 1 unresolved externals call "bin\standalone\msvc\msvc-14.0\msvc-setup.bat" x86 >nul link /NOLOGO /INCREMENTAL:NO /DLL /DEBUG /MACHINE:X86 /MANIFEST:EMBED /subsystem:console /out:"bin\msvc-14.0\debug\boost_python.dll" /IMPLIB:"bin\msvc-14.0\debug\boost_python.lib" @"bin\msvc-14.0\debug\boost_python.dll.rsp" Any advice as to what might be wrong. My Visual Studio 2019 does not have the corelibc.lib. I only find that under 'WinCE' libs, and so not found when I compile msvc 14... thanks

1 0

Where to find a complete boost example using ICL (intel 64bit compiler for windows 10)?
by Mehdi Est 13 Dec '20

13 Dec '20

Hi Everyone, Where can I find a complete boost example using ICL (intel 64bit C/C++ compiler for windows)? I would like to do it in header-only mode. Right now, I am compiling and linking using the below-mentioned flags/libraries. However, when I run the code I seem to experience deadlock because the execution stalls. Please let me know your valuable comments. Regards *Compile Flags* icl -I"C:/Program Files (x86)/IntelSWTools/sw_dev_tools/compilers_and_libraries_2020.2.254/windows/compiler/include" -I/../boost_1_73_0 -I../../../boost_1_73_0 -Qstd=c++0x -Qdiag-error-limit:3 -debug:all -Zi -Z7 -ZI -MDd -D_DEBUG -DBOOST_STACKTRACE_USE_WINDBG -Fo:../../Debug/obj/test.obj -c test.cpp *Link Flags* xilink -LIBPATH:"c:\Program Files (x86)\Windows Kits\10\Lib\10.0.19041.0\um\x64" -out:Debug/test.exe test.obj ole32.lib dbgeng.lib

1 0

[release] Boost 1.75.0
by Marshall Clow 11 Dec '20

11 Dec '20

Release 1.54.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 1 new library and numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.75.0> You can also download directly from: <https://dl.bintray.com/boostorg/release/1.75.0/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team Marshall Clow, Glen Fernandes, Michael Caisse

3 3

Fwd: [Beast] Slow HTTP connect on Windows. Normal?
by Dominique Devienne 11 Dec '20

11 Dec '20

Oops, this was meant for the list of course. --DD ---------- Forwarded message --------- From: Dominique Devienne <ddevienne(a)gmail.com> Date: Fri, Dec 11, 2020 at 6:54 PM Subject: Re: [Boost-users] [Beast] Slow HTTP connect on Windows. Normal? To: Vinnie Falco <vinnie.falco(a)gmail.com> On Wed, Nov 25, 2020 at 7:43 PM Vinnie Falco <vinnie.falco(a)gmail.com> wrote: > On Wed, Nov 25, 2020 at 2:55 AM Dominique Devienne via Boost-users > <boost-users(a)lists.boost.org> wrote: > > Given the high connect time on Windows, I thought I'd try to keep the > connection open on the client, and issue several send-request/read-response > pairs, using the Beast-based (sync) HTTP client, but only the first one > works correctly, the 2nd errors out with: > > > > Error: An established connection was aborted by the software in your > host machine > > This means that the server closed the connection. Are you setting > HTTP/1.1 in the request? For HTTP/1.1 the default is to enable > keep-alive. But for 1.0 the default is to close the connection. > Sorry for the delay. Just getting back to this. Yes, I'm in 1.1, and I verified that the request has Keep-Alive, and I'm (or the example, I don't recall) is setting the same value on the response. > it sounds like your connection is being closed after one request. Beast > definitely supports keep-alive, so this is certainly user error. > Please inspect the request/response messages taking place and post > them on the list unmodified (use a wire sniffer for this if necessary) > if you are still having problems. > Debugging this, I can see that the close arg to on_write is true, despite the Keep-Alive on the response. That response has an empty_body BTW, in case it matters. This route just replies 200 OK or 403 Forbidden, there's no body to return, only the headers matter to the client. The reason why the connection is closed after the 1st request seems to be because of need_eof(). The async server example has something like this in `send()`: template <typename RES> void send(RES&& msg) { // The lifetime of the message has to extend // for the duration of the async operation so // we use a shared_ptr to manage it. auto sp = std::make_shared<RES>(std::move(msg)); // Store a type-erased version of the shared // pointer in the class to keep it alive. res_ = sp; bool need_eof = sp->need_eof(); ctx_.out() << "send: sp->need_eof() = " << need_eof << std::endl; // Write the response http::async_write( stream_, *sp, beast::bind_front_handler( &session::on_write, shared_from_this(), sp->need_eof() ) ); } And `need_eof()` is true indeed. Which thus calls `on_write()` with `bool close = true`, resulting in a `do_close()` instead of waiting for the next request: void on_write( bool close, beast::error_code ec, std::size_t bytes_transferred ) { boost::ignore_unused(bytes_transferred); if (ec) { return; // fail(ec, "write"); } if (close) { // This means we should close the connection, usually because // the response indicated the "Connection: close" semantic. ctx_.out() << "on_write: close()" << std::endl; return do_close(); } // We're done with the response so delete it res_.reset(); // Read another request do_read(); } I stepped into `need_eof()`, and all conditions of the `if` are false, resulting in the `return true` at the end. template<bool isRequest, class Body, class Fields> bool message<isRequest, Body, Fields>:: need_eof(std::false_type) const { // VFALCO Do we need a way to let the caller say "the body is intentionally skipped"? if( this->result() == status::no_content || this->result() == status::not_modified || to_status_class(this->result()) == status_class::informational || has_content_length() || chunked()) return ! keep_alive(); return true; } So is the issue having an empty_body? I'm not supposed to have one on a GET? BTW, I tried commenting out the `do_close()` inside `on_write()`, just to see what happens, and it still doesn't work, with the same error, but an additional delay (timeout?) I think. Here's the response I'm sending: ctx_.out() << "Sending response: 200 OK" << std::endl; http::response<http::empty_body> res{http::status::ok, req_.version()}; res.set(http::field::server, BOOST_BEAST_VERSION_STRING); res.keep_alive(req_.keep_alive()); ctx_.out() << "on_read: res.keep_alive() = " << res.keep_alive() << std::endl; return send(std::move(res)); I'm fairly sure it's user-error, but it's not easy to figure out for a Beast novice like myself. --DD

2 2

Reminder that Outcome v2.2 is to become Boost.Outcome
by Niall Douglas 11 Dec '20

11 Dec '20

After three Boost releases and a year of warning, this is a reminder that Outcome v2.2 is to replace v2.1 as Boost.Outcome. This is a breaking change, all existing Boost.Outcome code shall need to be upgraded as of Boost 1.76 onwards. Changes: https://www.boost.org/doc/libs/1_75_0/libs/outcome/doc/html/changelog/v22.h… Upgrade guide: https://www.boost.org/doc/libs/1_75_0/libs/outcome/doc/html/changelog/upgra… You should see the merge land into boostorg/outcome next few days. It'll take some weeks to upgrade the tutorial and documentation. Niall

1 0

Boost.Beast base64 decode
by Dominique Devienne 11 Dec '20

11 Dec '20

I'm decoding a Java Web Token, composed of 3 separate base64 encoded parts (header.payload.signature). Before I was using Boost.Serialization: using namespace boost::archive::iterators; using It = transform_width<binary_from_base64<std::string::const_iterator>, 8, 6>; std::string tmp(It(std::begin(base64_str)), It(std::end(base64_str))); return boost::algorithm::trim_right_copy_if(tmp, [](char c) { return c == '\0'; }); But since I'm already using Boost.Beast, I thought I'd drop the above dependency, and use this instead: using namespace boost::beast::detail; std::string decoded(base64::decoded_size(base64_str.size()), '\0'); auto rc = base64::decode(decoded.data(), base64_str.data(), base64_str.size()); decoded.resize(rc.first); But turns out some (all?) JWTs do not include the trailing equals that "proper" base64 should have. And in that case, Beast's rc.first does not include the last character, which I can still see in decoded variable prior to the .resize() in the debugger. Here's the payload part: eyJwYXNzd29yZCI6IlAiLCJ1c2VybmFtZSI6IlUifQ What it should decode to: {"password":"P","username":"U"} What Beast's decode yields: {"password":"P","username":"U" Is this on purpose? Could Beast's base64::decode() be changed to be more lenient about the absence of trailing equals from the base64 encoded string? JWT handling seems like a natural fit within the context of Beast, and although this is an implementation detail, it would seem logical for decode() to cope with that, no? Thanks, --DD

3 4

Boost 1.75.0 Release Candidate 1 -- macOS (gcc 10.2.0)
by DV Henkel-Wallace 10 Dec '20

10 Dec '20

> Date: Thu, 3 Dec 2020 06:54:13 -0800 > From: Marshall Clow <mclow.lists(a)gmail.com <mailto:mclow.lists@gmail.com>> > > [release] Boost 1.75.0 Release Candidate 1 > Built fine on macOS 11.0.1 using brew-installed g++-10 ./b2 cxxstd=2a boost.locale.icu=off boost.locale.std=off threading=multi -sNO_COMPRESSION=1 Darwin KA-19.local 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 gcc version 10.2.0 (Homebrew GCC 10.2.0) Target: x86_64-apple-darwin19 Lots of deprecated warnings for #pragma GCC diagnostic ignored "-Wdeprecated-copy", use of boost/bind.hpp and boost/detail/iterator.hpp. But otherwise OK. Net: Apple's clang and g++ generated pretty similar warnings. Clang-11 did not.

1 0

Boost 1.75.0 Release Candidate 1 -- macOS (system compiler)
by DV Henkel-Wallace 10 Dec '20

10 Dec '20

> Date: Thu, 3 Dec 2020 06:54:13 -0800 > From: Marshall Clow <mclow.lists(a)gmail.com <mailto:mclow.lists@gmail.com>> > > [release] Boost 1.75.0 Release Candidate 1 > Built fine on macOS 11.0.1 using the system compiler installed with latest Xcode (12.2) ./b2 cxxstd=2a boost.locale.icu=off boost.locale.std=off threading=multi -sNO_COMPRESSION=1 Darwin KA-19.local 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 Apple clang version 12.0.0 (clang-1200.0.32.27) Target: x86_64-apple-darwin20.1.0 Lots of deprecated warnings for #pragma GCC diagnostic ignored "-Wdeprecated-copy", use of boost/bind.hpp and boost/detail/iterator.hpp. But otherwise OK.

1 0

Boost 1.75.0 Release Candidate 1 -- macOS
by DV Henkel-Wallace 10 Dec '20

10 Dec '20

> Date: Thu, 3 Dec 2020 06:54:13 -0800 > From: Marshall Clow <mclow.lists(a)gmail.com <mailto:mclow.lists@gmail.com>> > > > [release] Boost 1.75.0 Release Candidate 1 > Built fine on macOS 11.0.1 using llvm 11.0.0 ./b2 cxxstd=2a boost.locale.icu=off boost.locale.std=off threading=multi -sNO_COMPRESSION=1 Darwin KA-19.local 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 clang version 11.0.0 Target: x86_64-apple-darwin20.1.0 Lots of deprecated warnings for use of boost/bind.hpp and boost/detail/iterator.hpp as well as using enums as bitfields. But otherwise OK.

2 1

QT MinGW32 : bootstrap stacktrace (header only) not showing function names and lines numbers shows only address
by Mehdi Est 05 Dec '20

05 Dec '20

Hi Everyone, I am trying to print stack-trace using boost *HEADER-ONLY. *I am using descriptions under Configuration and Build <https://www.boost.org/doc/libs/1_74_0/doc/html/stacktrace/configuration_and…> to compile a simple code using QT MinGW32 I also use the below macros to tune boost: -DBOOST_STACKTRACE_USE_WINDBG -DBOOST_STACKTRACE_USE_ADDR2LINE -DBOOST_STACKTRACE_ADDR2LINE_LOCATION I have no clue why the function names and line numbers are not showing up. Any comment is appreciated. Mike *Below are compile and build instructions:* g++ -g3 -DBOOST_STACKTRACE_USE_WINDBG -DBOOST_STACKTRACE_USE_ADDR2LINE -DBOOST_STACKTRACE_ADDR2LINE_LOCATION=C:\Qt_5_12\Tools\mingw730_32\bin\addr2line.exe -I../../../boost_1_73_0 -c main.cpp -omain.o g++ main.o -o stack_traces.exe -L"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.19041.0\um\x86" -L"C:\temp\libbacktrace" -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -lole32 -luuid -lodbc32 -lodbccp32 -lDbgEng *And here is the output ... * 0# 0x00402C75 in stack_traces 1# 0x00401602 in stack_traces 2# 0x004016CE in stack_traces 3# 0x0040138B in stack_traces 4# _BaseThreadInitThunk in KERNEL32 5# _RtlGetAppContainerNamedObjectPath in ntdll 6# _RtlGetAppContainerNamedObjectPath in ntdll 1 + 2 = 3 *The code (main.cpp)* Is fairly simple as below: #include <iostream> #include <boost/stacktrace.hpp> double add(double a, double b){ std::cout << boost::stacktrace::stacktrace(); std::cout << a << " + " << b << " = " << (a+b) << std::endl; return a+b; } int main(){ add(1,2); return 0; }

2 2

[release] Boost 1.75.0 Release Candidate 1
by Marshall Clow 04 Dec '20

04 Dec '20

[release] Boost 1.75.0 Release Candidate 1 The first release candidates for the 1.75.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.75.0/source/> The SHA256 checksums are as follows: caf36d7c13b3d8ce62282a64a695113945a13b0f1796a45160726d04295f95ed boost_1_75_0_rc1.zip aeb26f80e80945e82ee93e5939baebdca47b9dee80a07d3144be1e1a6a66dd6a boost_1_75_0_rc1.tar.gz 953db31e016db7bb207f11432bef7df100516eeb746843fa0486a222e3fd49cb boost_1_75_0_rc1.tar.bz2 3a8b314871646e7404886736273c053278ba71b11347f72d4751411d65d6d1a5 boost_1_75_0_rc1.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

3 4

Boost.Numeric.Interval: Please specify rounding control mechanism
by Bastien Commelongue 01 Dec '20

01 Dec '20

Hello, I am building an app for IOS (ARM) and I had this issue while compiling: *Boost.Numeric.Interval: Please specify rounding control mechanism.* C99 version should be used in this case but __USE_ISOC99 is not defined. Modifying the condition with this code (using __cplusplus) fixed the issue: *boost/numeric/interval/hw_rounding.hpp(36)* *#if defined(BOOST_NUMERIC_INTERVAL_NO_HARDWARE) && (defined(__USE_ISOC99) || defined(__MSL__) || (defined __cplusplus && __cplusplus >= 201103L))# include <boost/numeric/interval/detail/c99_rounding_control.hpp>#endif* Let me know if I missed something or if you plan to integrate this modification in a next version. Cheers, Bastien Commelongue

2 1

PolyCollection
by Brian Wood 30 Nov '20

30 Nov '20

Shalom Hey, is anyone using PolyCollection? I have serialization support for it: https://github.com/Ebenezer-group/onwards/tree/master/example/poly If you considered it, but chose an alternative library, what was the reason? Thanks. Brian Ebenezer Enterprises - Enjoying programming again. https://webEbenezer.net

1 0

Re: [Boost-users] [multi_array] Feature request: constructor and resize from values
by DV Henkel-Wallace 30 Nov '20

30 Nov '20

If an object does not have a default constructor what could it mean to have a block of memory holding one that has not been initialized? How would your program know if the object had been properly initialized or not? There are three ways to address this: 1 - A pointer, as already mentioned. A null pointer means the spot does not refer to ("contain") a valid object -- or any object at all. 2 - use a variant 3 - create a default constructor (which you could do by changing the signature of your constructor to something like (int = 0) or (int = -1) assuming those values are invalid). In all cases, regardless of semantics or implementation you'll either have to check at runtime for a valid object OR, if you know for other reasons which locations are valid, use the default constructor with any value you'd like. If you don't want to use pointers there are a couple of other possibilities: > > Date: Sun, 22 Nov 2020 12:06:04 +0100 > From: Eugenio Bargiacchi <svalorzen(a)gmail.com <mailto:svalorzen@gmail.com>> > > Ah, sorry, I thought it would have been automatically clear. Consider this > example: > > class A { > public: > A(int) {} > }; > > boost::multi_array<A,2> array(boost::extents[2][2]); // Compiler error > boost::multi_array<A,2> array(boost::extents[2][2], A(3)); // What I would > like > > array.resize(boost::extents[2][2]); // Again, compiler error > array.resize(boost::extents[2][2], A(2)); // What I would like > > The variable `array` cannot be constructed in any way, as multi_array will > try to default-construct it, and that will fail. Trying to simply create > `array` with its default constructor works (although it will obviously be a > zero-sized array), but when trying to resize it (to actually store things), > the same thing will happen.

2 1

[multi_array] Feature request: constructor and resize from values
by Eugenio Bargiacchi 22 Nov '20

22 Nov '20

I'd love to be able to use multi_array with classes that do not have a default constructor. At the moment, this is impossible, as both the constructor and resize functions only take extents as arguments (and possibly some other options), but no value_type, as for example std::vector does. Thus, trying to store objects without a default constructor in a multi_array results in hard compiler errors, with no workaround that I know of. This happens to me fairly often, as I use multi_array to organize sets of complex objects. If there is a technical reason why this is not possible, I would also be happy to learn it. Best regards, Eugenio Bargiacchi

2 2

[xpressive] I got a crash in after i upgrade from 1.44 to 1.74
by forston_shi＠trendmicro.com 20 Nov '20

20 Nov '20

Hi Boost Users I met a crash in following code after I upgrade from 1.44 to 1.74, When I used "-O1 -DNDEBUG" to compile, it will crash. But when I used "-O1" or "-DNDEBUG" or "-O0 -DNDEBUG", it will not crash. In 1.44, all of them are ok. My GCC version is 4.1.2 and test in redhat-AS 4 32 bit. callstack #0 at ./boost_1_74_0_bk/boost/xpressive/detail/static/transmogrify.hpp:160 160 char const *name_end = m.name_ + std::strlen(m.name_); #1 at ./boost_1_74_0_bk/boost/proto/transform/detail/preprocessed/fold_impl.hpp:80 #2 at ./boost_1_74_0_bk/boost/proto/transform/detail/preprocessed/fold_impl.hpp:80 #3 at ./boost_1_74_0_bk/boost/xpressive/detail/static/compile.hpp:79 #4 at ./boost_1_74_0_bk/boost/xpressive/detail/static/compile.hpp:99 #5 0x08049d5f in main () at ./boost_1_74_0_bk/boost/xpressive/basic_regex.hpp:252 Can you help to check this problem? Best regards Forston callstack Following is source code. #include <boost/xpressive/basic_regex.hpp> #include <boost/xpressive/regex_primitives.hpp> #include <boost/xpressive/match_results.hpp> #include <boost/xpressive/regex_algorithms.hpp> int main(int argc, char* argv[]) { std::wstring uri_string = L"https://192.168.1.1/test"; printf("begin regex_match %ls \n ", uri_string.c_str()); using namespace boost::xpressive; static wsregex const uri_regex = bos >> (s1 = (alpha >> *(alnum | L'+' | L'-' | L'.'))) >> L"://" >> (s2 = *(alnum | L'-' | L'.' | L':' | L'@' | L'[' | L']' | L'_')) >> !(as_xpr(L'/') >> (s3 = (*_))) >> eos ; wsmatch result; try { if (!regex_match(uri_string, result, uri_regex)) { printf( "regex_match failed %ls \n ", uri_string.c_str()); return -1; } } catch (std::exception& e) { printf("regex_match failed %ls \n ", uri_string.c_str()); return -1; } printf("end regex_match success %ls \n ", uri_string.c_str()); return 0; } TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. For details about what personal information we collect and why, please see our Privacy Notice on our website at: Read privacy policy<http://www.trendmicro.com/privacy>

1 0

[asio] Prevent socket inheritance on Windows
by Klebsch, Mario 17 Nov '20

17 Nov '20

Hello everybody, I am using boost as communication framework in a library for Windows. I am getting problems, when the client code, that uses our library, creates windows processes and inherits handles, e.g. by using popen(). I currently observing two problems. 1. Even though my library has closed the socket, the peer keeps an active connection. 2. When there is a pending async read operation, calling close() does not lead to the read handler being invoked with an error. My library closes a socket in its shutdown process and because it also terminates the io_service during shutdown, it waits for the termination of the pending read operation. The second problem is the one, that is visible to the client, since our library hands during shutdown. Unfortunately it is not triggered by just inheriting a socket handle to a child process. I know, the socket handle gets inherited to the child process and when I kill the child process, the pending async operation terminates. I also have seen the pending read operation to terminate, then the peer system sends some data. The data seems to be read fine, although the socket has already been closed by our library. The io_service is blocked in the call to GetQueuedCompletionStatus() on its io completion port. It seems, the io completion port still is linked the the socket, although the socket has been closed. The problem is triggered reliably, when using my fully integrated library, but I have not yet managed to write a small simple sand alone program to demonstrate this problem. * Does anybody on this mailing list has a clue, what may cause the 2nd problem, where the async operation does not terminate upon closing the socket. * Does anybody know of a reliable way to prevent an asio socket from being inherited. I found some web pages mentioning WSA_FLAG_NO_HANDLE_INHERIT, but have not found a way to get boots to use this flag other than patching my boost source code. Thanks to everybody, Mario -- Mario Klebsch Actia I+ME GmbH Mario.klebsch(a)ime-actia.de<mailto:Mario.klebsch@ime-actia.de> Dresdenstrasse 17/18 Fon: +49 531 38 701 716 38124 Braunschweig Fax: +49 531 38 701 88 Germany

1 0

[release] Boost 1.74.0 beta 1 released
by Marshall Clow 14 Nov '20

14 Nov '20

Boost release 1.75.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.75.0.beta1/source/> The SHA256 checksums are as follows: 3f01d3e5dc822e151892040d4667e364ea808d208d2e49cc7a1802bd4da3d4cc boost_1_75_0_b1.7z 9b75a80f845d4ae312e3c9151ffdfe3fed450973095e0a15c68d0be394f2f2df boost_1_75_0_b1.tar.bz2 123519d4b056fbbd69e452db880abe2c7e55f21779d44a4d6b6c714d5c13c3ee boost_1_75_0_b1.tar.gz b73e01d22d5b3d2ff82f14a371e3974fab30448bf6ff5ac8b9c829539a19c2d7 boost_1_75_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_75_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.75.0 Beta 1 Release Candidate 2
by Marshall Clow 13 Nov '20

13 Nov '20

The second release candidates for the 1.75.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.75.0.beta1/source/> The SHA256 checksums are as follows: 3f01d3e5dc822e151892040d4667e364ea808d208d2e49cc7a1802bd4da3d4cc boost_1_75_0_b1_rc2.7z 9b75a80f845d4ae312e3c9151ffdfe3fed450973095e0a15c68d0be394f2f2df boost_1_75_0_b1_rc2.tar.bz2 123519d4b056fbbd69e452db880abe2c7e55f21779d44a4d6b6c714d5c13c3ee boost_1_75_0_b1_rc2.tar.gz b73e01d22d5b3d2ff82f14a371e3974fab30448bf6ff5ac8b9c829539a19c2d7 boost_1_75_0_b1_rc2.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

3 5

Compile issues when cross compiling for iOS with external dependencies
by Ardavon Falls 10 Nov '20

10 Nov '20

When attempting to cross-compile boost 1.69.0 for iOS (with clang) and using external dependencies it fails to compile because when it tests to see if the dependencies are valid, it fails to compile the test program correctly due to it attempting to add incorrect linker flags. I tried modifying the boost.build to not add those flags but it seemed to unravel a rat's nest of issues (attempting to link with librt even though its for iOS, compiled the test program for x86 and not arm, etc.., etc..) The error I keep getting is... ld: unknown option: --start-group Thank you for your help. I am using the following b2 options.. ./b2 --prefix=/Users/afalls/delete-me/build-boost/install/ \ --build-dir=/Users/afalls/delete-me/build-boost/build/ \ --user-config=/Users/afalls/delete-me/build-boost/ios-config.jam \ --with-math \ --with-wave \ --with-container \ --with-contract \ --with-exception \ --with-graph \ --with-iostreams \ --with-locale \ --with-log \ --with-program_options \ --with-random \ --with-regex \ --with-mpi \ --with-serialization \ --with-coroutine \ --with-fiber \ --with-context \ --with-timer \ --with-thread \ --with-chrono \ --with-date_time \ --with-atomic \ --with-filesystem \ --with-system \ --with-graph_parallel \ --with-stacktrace \ --with-test \ --with-type_erasure \ -q \ -j 16 \ toolset=clang \ threading=multi \ architecture=arm \ abi=aapcs \ binary-format=mach-o \ address-model=64 \ cxxflags="${IOS_CXXFLAGS}" \ cflags="${IOS_CFLAGS}" \ target-os=iphone \ link=static \ variant=release \ define=_LITTLE_ENDIAN \ install My user-config.jam file is below... import os ; using clang : : /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -arch arm64 -DBOOST_AC_USE_PTHREADS -DBOOST_SP_USE_PTHREADS -Wno-unused-local-typedef -Wno-nullability-completeness -miphoneos-version-min=9.0 -fPIC : <stripper> <root>/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk <architecture>arm <target-os>iphone <include>/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/include ; using zlib : 1.2.11 : <include>/Users/afalls/.conan/data/zlib/1.2.11/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/zlib/1.2.11/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>z ; using lzma : 5.2.4 : <include>/Users/afalls/.conan/data/xz_utils/5.2.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/xz_utils/5.2.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>lzma ; using bzip2 : 1.0.8 : <include>/Users/afalls/.conan/data/bzip2/1.0.8/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/bzip2/1.0.8/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>bz2 ; using zstd : 1.4.4 : <include>/Users/afalls/.conan/data/zstd/1.4.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/zstd/1.4.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>zstd ;

1 0

Boost version not matching according to the manual
by Arnab Chaudhuri 08 Nov '20

08 Nov '20

To whom it may concern, I have installed boost and to the version is 1.65.1.0ubuntu1 . It is written while installing that the minimum requirement is 1.66. Can you please tell me how to update my version. The commands I used to install boost are as follows: *sudo apt install libboost-dev**sudo apt install libboost-all-dev* *Thanking you,* *Arnab Chaudhuri.*

1 0

Validating downloads on Windows
by Kenneth Porter 08 Nov '20

08 Nov '20

I thought I had a corrupted download and wanted to relate my experience on how to validate the zip file downloads on Windows. The Boost archives (tar, zip, etc.) all have a matching small .json file that contains a SHA256 hash of the archive file. Under Windows 10, you can use certutil.exe from a command line to compute the hash for the archive and compare it to the value in the .json file: C:\Users\ken\Downloads>certutil -hashfile boost_1_75_0_b1_rc1.zip SHA256 SHA256 hash of boost_1_75_0_b1_rc1.zip: 07ddca7c39ea9152bad73bee4f10f2c9c8e3a2d7e153aa945a343f83eca5db59 CertUtil: -hashfile command completed successfully. (I thought my download was corrupted because I was using an ancient version (5.50) of InfoZip's unzip program and it was reporting errors. I updated to version 6 and it unpacked the same file just fine.)

1 0

[release] Boost 1.75.0 Beta 1 Release Candidate 1
by Marshall Clow 07 Nov '20

07 Nov '20

The first release candidates for the 1.75.0 beta release are now available at: <https://dl.bintray.com/boostorg/release/1.75.0.beta1/source/> The SHA256 checksums are as follows: c271f488c7c8de7c147bf8675d578fb2f06c6c171d9547c5a40cddccb9f2a6c4 boost_1_75_0_b1_rc1.7z 0db0944e9d2250907e011900eea304ca055d1c418d38b3fbb1eee692a6b851a6 boost_1_75_0_b1_rc1.tar.bz2 624bd6b03d86bf1387b4e8927dab16b4198f255f15dd71d6a8c1c5ec270584b3 boost_1_75_0_b1_rc1.tar.gz 07ddca7c39ea9152bad73bee4f10f2c9c8e3a2d7e153aa945a343f83eca5db59 boost_1_75_0_b1_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

2 4

Why did ip::basic_resolver::query get depreciated in 1.66?
by Luke Knoble 06 Nov '20

06 Nov '20

I ask because I replaced its return value with an endpoint in a tcp resolver function and my dns resolution started working..! Cheers, Luke Knoble

1 0