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

Re: [Boost-users] Problem building Boost 1.64.0 with Oracle Developer Studio 12.6
by Leo Carreon 12 Aug '17

12 Aug '17

BTW, I forgot to mention a third issue which has been acknowledged by Oracle as a problem with the compiler: 3. Problem with Boost.Log with this error message: >> Assertion: (../lnk/initializer.cc, line 1865) while processing ./boost/log/expressions/message.hpp at line 98. From: Leo Carreon Sent: Wednesday, August 9, 2017 10:52 AM To: Boost Users Mailing List Subject: Problem building Boost 1.64.0 with Oracle Developer Studio 12.6 Hi Boosters, I have been trying to build Boost 1.64.0 with Oracle Developer Studio 12.6 on Oracle Solaris 11.3 x86_64. There are two errors encountered during the build. They are: 1. Problem with Boost.Optional with this error messages: "libs/log/src/named_scope.cpp", line 118: Error: Use of overloaded binary operator '=' is ambiguous. "./boost/optional/optional.hpp", line 900: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. "./boost/optional/optional.hpp", line 962: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. 2. Problem with Boost.Python with this error message: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. Note that these two errors are the cause of 9 Boost shared libraries to not be generated. I would appreciate it very much if someone could give me some pointers on how to resolve the above issues. Kind regards, Leo

1 0

deleting operators to forbid mixed arithmetic? [multiprecision]
by Dani Brake 12 Aug '17

12 Aug '17

Hi, I'd like to forbid multiplication of Boost.Multiprecision floating point numbers by doubles. Any tips? I think I want to delete a family of operator*s, but am having a hard time coming up with which ones. Thanks, Dani Brake University of Wisconsin Eau Claire

3 2

Boost 1.65.0 Release Candidate 2
by Marshall Clow 12 Aug '17

12 Aug '17

The second release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1's are in that directory, too - make sure you get the right files! ] Changes from RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 786ccb478a82ef526fb8649841d2e863af90d7ea31217bb2e938d87aff06cf23 boost_1_65_0_rc2.7z 83dbc7179271825c55a59c26f30cf9de53bb8b42006d920948bad709f5372af9 boost_1_65_0_rc2.tar.bz2 493cbf33a8837b44f87e3ac8a37ec32b9a0a27b8cdb03eac6237a16027a03809 boost_1_65_0_rc2.tar.gz 40e4ccbd52322f9a8cb6e1829075c810d8aad8851f3efb2b3da7fcff6963e14d boost_1_65_0_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. Thanks! -- The release managers

2 4

[serialization] archive testing
by Sergey Spiridonov 09 Aug '17

09 Aug '17

Hi, 1. The following works with xml_archive: cd boost_1_64_0/libs/serialization/test bjam -sBOOST_ARCHIVE_LIST=xml_archive.hpp 2. Example from documentation[1] does not work for me. Documentation tells[1]: -------------------------- To test a new archive, for example, portable binary archives, with the gcc compiler, make a header file portable_binary_archive.hpp and invoke bjam with -sBOOST_ARCHIVE_LIST=portable_binary_archive.hpp This process in encapsulated in the shell or cmd script library_test whose command line is library_test --toolset=gcc -sBOOST_ARCHIVE_LIST=portable_binary_archive.hpp ------------------------- [1] http://www.boost.org/doc/libs/1_64_0/libs/serialization/doc/archive_referen… I created boost_1_64_0/libs/serialization/test/portable_binary_archive.hpp with following lines: #include <libs/serialization/example/portable_binary_oarchive.hpp> typedef portable_binary_oarchive test_oarchive; typedef std::ofstream test_ostream; #include <libs/serialization/example/portable_binary_iarchive.hpp> typedef portable_binary_iarchive test_iarchive; typedef std::ifstream test_istream; #define TEST_STREAM_FLAGS (std::ios_base::openmode)0 1. There is no "library_test" script in boost_1_64_0.tar.bz2. 2. cd boost_1_64_0/libs/serialization/test bjam -sBOOST_ARCHIVE_LIST=portable_binary_archive.hpp fails with many linking errors like that: ../../../bin.v2/libs/serialization/test/test_array_portable_binary_archive.test/gcc-6.3.0/debug/test_array.o: In function `portable_binary_oarchive::save(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)': /home/ss/src/boost_1_64_0/libs/serialization/test/../../../libs/serialization/example/portable_binary_oarchive.hpp:105: undefined reference to `boost::archive::basic_binary_oprimitive<portable_binary_oarchive, char, std::char_traits<char> >::save(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' What am i doing wrong? -- Best regards, Sergey Spiridonov GAMIC mbH, Roermonder Str. 151, 52072 Aachen, Germany Phone +49 241 889110 CEO Paul Malkomes Amtsgericht Aachen HRB 4029 VAT-ID: DE 121 677 540 Please use support(a)gamic.com for support requests and bug reports

1 0

[heap] Singular handle issue with MSVC iterator debug facilities
by Mateusz Loskot 09 Aug '17

09 Aug '17

Hi, Using VS2017 and Boost 1.64, I'm compiling a program which uses boost::heap::d_ary_heap. In debug configuration (with default _ITERATOR_DEBUG_LEVEL), I'm observing issues at run-time when a handle of item on the heap is compared against default-constructed instance of handle_type. BTW, the handle_type compiled in is based on std::list::iterator as defined in boost::heap::detail::priority_queue_mutable_wrapper. The issue is that MSVC iterator debug facilities break execution with File: c:\program files (x86)\microsoft visual studio\2017\professional\vc\tools\msvc\14.10.25017\include\list Line: 290 Expression: list iterators incompatible AFAIU, handle_type{}; seems to yield handle h object wrapping singular iterator. Below, minimal example to reproduces the problem is included. While debugging the sample, Visual C++ debugger does not show the iterator wrapped by the handle as default-constructed with null node pointer. Instead, it displays garbage: ((???, ???), ???) // ------------------------------------------------------------------ #include <cstdint> #include <functional> #include <boost/heap/d_ary_heap.hpp> using NodeID = std::uint32_t; using EdgeWeight = std::int32_t; using HeapData = std::pair<EdgeWeight, NodeID>; using HeapContainer = boost::heap::d_ary_heap< HeapData, boost::heap::arity<4>, boost::heap::mutable_<true>, boost::heap::compare<std::greater<HeapData>>>; using HandleType = HeapContainer::handle_type; int main() { HeapContainer heap; auto const handle = heap.push(std::make_pair(100, 1)); handle == HandleType{}; // _DEBUG_ERROR("list iterators incompatible"); return 0; } // ------------------------------------------------------------------ Is this a known MSVC drawback while working with boost::heap::d_ary_heap or above the handle_type is actually misused? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

Boost 1.65.0 Release Candidate 1
by Marshall Clow 09 Aug '17

09 Aug '17

The release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ The SHA256 checksums are as follows: 0f1352a7738f24b39b564263b66a8c38bc7d984b57406396400474602e961ad3 boost_1_65_0_rc1.7z c2a022d4d6706668ea94b8e799a76e38929e0e34db884ef451fa9d5db6103238 boost_1_65_0_rc1.tar.bz2 7e84a27276792209d48357a0671348768dbf4dd1d4eadbf01b855274208f148d boost_1_65_0_rc1.tar.gz 537c42771b2351b4ea3eb8e9a13a3423edcd155323d2c14c4606cd23fc22d09f boost_1_65_0_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. Thanks! -- The release managers

4 5

[filesystem] Pull request needs attention
by Robert Dailey 09 Aug '17

09 Aug '17

I have fixed a crash I found due to static initialization ordering in boost filesystem. I have a proposed fix here: https://github.com/boostorg/filesystem/pull/47 It hasn't gotten any attention yet, so I'm hoping someone can offer some advice and/or merge the PR for me. Thanks in advance.

2 1

Problem building Boost 1.64.0 with Oracle Developer Studio 12.6
by Leo Carreon 09 Aug '17

09 Aug '17

Hi Boosters, I have been trying to build Boost 1.64.0 with Oracle Developer Studio 12.6 on Oracle Solaris 11.3 x86_64. There are two errors encountered during the build. They are: 1. Problem with Boost.Optional with this error messages: "libs/log/src/named_scope.cpp", line 118: Error: Use of overloaded binary operator '=' is ambiguous. "./boost/optional/optional.hpp", line 900: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. "./boost/optional/optional.hpp", line 962: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. 2. Problem with Boost.Python with this error message: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. Note that these two errors are the cause of 9 Boost shared libraries to not be generated. I would appreciate it very much if someone could give me some pointers on how to resolve the above issues. Kind regards, Leo

1 0

Re: [Boost-users] [filesystem] Pull request needs attention
by Robert Dailey 08 Aug '17

08 Aug '17

On Tue, Aug 8, 2017 at 12:07 PM, Daniela Engert <dani(a)ngrt.de> wrote: > Am 08.08.2017 um 18:20 schrieb Robert Dailey via Boost-users: >> I have fixed a crash I found due to static initialization ordering in >> boost filesystem. I have a proposed fix here: >> https://github.com/boostorg/filesystem/pull/47 > > There is actually an even older (from april) pull request > https://github.com/boostorg/filesystem/pull/43 (by me) open on the very > same subject. > > Ciao > Dani Ah I didn't realize someone else had solved this problem. I will close mine in favor of yours. I don't quite understand why they're trying to share globals/statics between threads without some synchronization, but it's not my battle to deal with. I just want the code to work and not crash my application. Thanks for the reply.

1 0

make file starting out
by Peter Koukoulis 08 Aug '17

08 Aug '17

Hi I am new to setting up make files, and even newer to Boost. I've been using Geany on Ubuntu to learn Boost. When I compile and link using a single file with the following : g++ -g -Wall -std=c++14 -o "%e" "%f" -lboost_thread -DBOOST_THREAD_VERSION=5 -lboost_system -ldl then everything works as expected, for the following that is: #include <iostream> #include <boost/thread.hpp> #include <boost/thread/mutex.hpp> #include <boost/bind.hpp> #include <boost/asio.hpp> class t { private: boost::asio::io_service ios; std::unique_ptr<boost::asio::io_service::work> work_ios; boost::thread_group tg; int f; boost::mutex mx; public: // Constructor t( int p ) : work_ios{std::make_unique<boost::asio::io_service::work>(ios)}, f{p} { if(p>0) p = boost::thread::hardware_concurrency()*2; for ( int i = 0; i < p; ++i ) tg.create_thread( boost::bind( &boost::asio::io_service::run, &ios ) ); } // Destructor ~t () { work_ios.reset(); tg.join_all(); ios.stop(); } template <typename Job> void run_job( Job job ) { boost::unique_lock< boost::mutex > lock( mx ); if ( 0 == f ) return; --f; ios.dispatch( boost::bind( &t::wrap_job, this, boost::function< void() >(job) )); } private: void wrap_job( boost::function< void() > job ) { try { job(); } catch ( const std::exception& ) {} boost::unique_lock< boost::mutex > lock( mx ); ++f; } }; int main() { t tp{2}; tp.run_job( [] () { std::cout << "some work \n"; } ); return 0; } But when I attempt to split "t" into a .h and .cpp file with a separate file for main to test with, my linking does not work. The make output is: g++ test_t.o t.o -o test_t test_t.o: In function `__static_initialization_and_destruction_0(int, int)': test_t.cpp:(.text+0x6e9): undefined reference to `boost::system::generic_category()' test_t.cpp:(.text+0x6f5): undefined reference to `boost::system::generic_category()' The files look as follows: # the makefile: CC=g++ CFLAGS=-c -Wall -std=gnu++14 -lboost_system -lboost_thread -DBOOST_THREAD_VERSION=5 -ldl -lpq all: test_t test_t: t.o test_t.o $(CC) test_t.o t.o -o test_t t.o: t.cpp $(CC) $(CFLAGS) t.cpp test_t.o: test_t.cpp $(CC) $(CFLAGS) test_t.cpp clean: rm *o test_t.o test_t // .h file #ifndef T_H_ #define T_H_ #include <boost/thread.hpp> #include <boost/thread/mutex.hpp> #include <boost/bind.hpp> #include <boost/asio.hpp> class t { private: boost::asio::io_service ios; std::unique_ptr<boost::asio::io_service::work> work_ios; boost::thread_group tg; int f; boost::mutex mx; public: t( int p = 0 ); ~t(); template <typename Job> void run_job( Job job ) { boost::unique_lock< boost::mutex > lock( mx ); if ( 0 == f ) return; --f; ios.dispatch( boost::bind( &t::wrap_job, this, boost::function< void() >(job) )); } private: void wrap_job( boost::function< void() > job ) { try { job(); } catch ( const std::exception& ) {} boost::unique_lock< boost::mutex > lock( mx ); ++f; } }; #endif // .cpp file #include "t.h" // Constructor t::t( int p ) : work_ios{std::make_unique<boost::asio::io_service::work>(ios)}, f{p} { if(p>0) p = boost::thread::hardware_concurrency()*2; for ( int i = 0; i < p; ++i ) tg.create_thread( boost::bind( &boost::asio::io_service::run, &ios ) ); } // Destructor t::~t () { work_ios.reset(); tg.join_all(); ios.stop(); } // main file #include <iostream> #include "t.h" int main() { t tp{4}; tp.run_job( [] () { std::cout << "some work \n"; } ); return 0; } Could somebody point out how the make file should look like ? thanks pkl

4 3