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

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

[Boost.Test] linking with shared lib (cannot find main)
by Andrew McFarlane 06 Apr '20

06 Apr '20

Hi all, I have been using Boost.Test for about a month now. Big fan so far, except for the atrocious compilation times, hence why I am moving toward using the shared library. using b2 to build and install Boost.Test's libs was simple enough, though after making the noted changes here: https://www.boost.org/doc/libs/1_72_0/libs/test/doc/html/boost_test/adv_sce… to customize the module's entry point, g++ cannot find the main executable: Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [Guest_T] Error 1 I tried digging through the docs for more information, but I came up short. For more context, I have written unit tests for each of my classes. For example, if my classes were A, B, and C, I would have A_T.cpp, B_T.cpp, and C_T.cpp for unit tests. - Should each of the unit tests have their own main() function? (I would think not..) - If not, how do I instruct g++ to first compile main.cpp before attempting to compile anything else? If you are curious, here are the contents of my Makefile: PROG := main CC := g++ SDIR := ../src PKG_DIRS := $(shell ls $(SDIR)) CXXFLAGS = -v -Wall -std=c++11 -I$(SDIR_TEST) \ $(addprefix -I$(SDIR)/,$(PKG_DIRS)) -I$(BOOST_ROOT) \ -L$(BOOST_LIBS) -Wl,-rpath,$(BOOST_LIBS) -lboost_unit_test_framework ODIR_TEST = ./bin SDIR_TEST = ./src OUTDIR = ./execs ODIR = ../sim/bin TEST_EXEC_NAMES = $(notdir $(basename $(wildcard $(SDIR_TEST)/*.cpp))) $(OUTDIR)/$(PROG) : $(SDIR_TEST)/main.cpp $(CC) $(CXXFLAGS) -o $@ $< $(OUTDIR)/$(PROG) : $(TEST_EXEC_NAMES) $(CC) $(CXXFLAGS) -o $@ $^ % : $(SDIR_TEST)/%.cpp $(CC) $(CXXFLAGS) -o $(OUTDIR)/$@ $^ >From what I can tell, g++ is failing to find the main the executable because it is attempting to compile one of my unit test files first. This may or may not be the case; either way, I would appreciate some help or direction as to what I should read to learn more about this. Let me know if you need more info. Thanks in advance. - AJ

2 2

[Boost.Test] duplicate symbol '_main' (manual test registration)
by Andrew McFarlane 06 Apr '20

06 Apr '20

Hi all, As the subject line suggests, I am attempting to manually employ a master test suite that registers several sub test suites. - Each subtest suite has its own header and translation unit. - Each header has a public "init_test_suite()" method and several private "test_case<number>()" methods, all of which are declared static. The public method creates a test suite, adds all the test cases for that translation unit, and adds the suite to the master test suite. This method is intended to be called from main.cpp. Here is a simplified version of my main.cpp: #define BOOST_TEST_DYN_LINK #define BOOST_TEST_NO_MAIN #include <boost/test/unit_test.hpp> #include "A.h" #include "B_T.h" #include "C_T.h" bool register_test_suites() { A_T::init_test_suite(); B_T::init_test_suite(); C_T::init_test_suite(); return 0; } int main(int argc, char *argv[], char *envp[]) { return boost::unit_test::unit_test_main(&register_test_suites, argc, argv); } Here's the issue. Despite the fact that I have defined BOOST_TEST_NO_MAIN, it appears that my compiler is still generating 2 objects files for the main executable entry: duplicate symbol 'register_test_suites()' in: /var/folders/bc/v2yqpsf96kn31tx8ybvy9gyw0000gn/T/main-58c6b3.o bin/main.o duplicate symbol '_main' in: /var/folders/bc/v2yqpsf96kn31tx8ybvy9gyw0000gn/T/main-58c6b3.o bin/main.o ld: 2 duplicate symbols for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [execs/main] Error 1 As you might be wondering, all of my test translation units define BOOST_TEST_DYN_LINK, and none of them define BOOST_TEST_MODULE, as the documentation suggests. I tried removing BOOST_TEST_NO_MAIN from main.cpp but that did not appear to do anything. I also tried removing the static and shared Boost.Unit lib files from my stage/lib directory and rebuilding only the shared version, and that did not work either. Also not that my g++ command does have the expected -L and -l flags for linking with Boost.Test: -L/usr/local/boost_1_72_0/stage/lib -lboost_unit_test_framework I am lost here. No idea why main() is being defined twice. Thanks in advance. - AJ

2 2

[Newbie][Interprocess] Placing a boost interprocess vector in an existing (not managed) shared memory
by Gaier, Bjoern 17 Mar '20

17 Mar '20

Hello Boost-Mailing-List, I have a question about the boost interprocess library - and I hope I can explain it correctly. I looked at the "Quick guide for the impatient" about the interprocess library - but I'm not sure if I can use this for our purpose. The main goal is to insert a STL vector (or different container) in a predefined portion of an already existing shared memory. The main problem is, that we cannot use the managed_shared_memory code from boost, because we rely on a different API to allocate the shared memory between Windows and other devices. Also the container should be placed at a fixed offset inside the created shared memory. I'm a complete newbie with boost and the interprocess library, that is why I'm not sure which interface I have to provide for the interprocess vector to be setup correctly. I hoped I could do something like: new (srh_mem_base + offset) boost::interprocess::vector<allocator>; I tried looking into the headers of the library to get an idea of that, but I honestly got lost. I'm really sorry if this a stupid or obvious question - and I thank for any help in advance! Kind greetings Björn Als GmbH eingetragen im Handelsregister Bad Homburg v.d.H. HRB 9816, USt.ID-Nr. DE 114 165 789 Geschäftsführer: Dr. Hiroshi Nakamura, Dr. Robert Plank, Markus Bode, Heiko Lampert, Takashi Nagano, Takeshi Fukushima. Junichi Tajika

3 3

Shared memory between Visual Studio build and MinGW build
by Da Xu 03 Mar '20

03 Mar '20

Hi folks, got a strange one here. I am trying to get two programs to communicate with each other on Windows 10 via shared memory. Both of them are using Boost 1.72, compiled from the same set of headers. I am only using the shared memory portion of boost. However, one is compiled with Visual studio 2019 community, and the other one is compiled with MinGW 64, g++ version 9.2.0. I have to use MinGW, because I am writing a plugin for another program, which only takes dlls compiled with MinGW. The program compiled with MinGW creates the shared memory and allocates several objects. Then I started the second program that was compiled with Visual Studio 2019. It was able to find and connect to the managed segment. When I am viewing the segment info from Visual Studio's debugger, everything looks ok. However, when I call get_free_memory(). It spits back 18446744073709551104, which is just bizarre. Then, when I tried to find_or_construct on the managed segment. It just hangs, apparently stuck in winapi::sleep_tick() with the following tracedll!boost::interprocess::winapi::sleep_tick() Line 1288 C++dll!boost::interprocess::ipcdetail::thread_sleep_tick() Line 187 C++dll!boost::interprocess::spin_wait::yield() Line 128 C++dll!boost::interprocess::ipcdetail::try_based_lock<boost::interprocess::ipcdetail::spin_mutex>(boost::interprocess::ipcdetail::spin_mutex & m) Line 71 C++dll!boost::interprocess::ipcdetail::spin_mutex::lock() Line 81 C++dll!boost::interprocess::ipcdetail::spin_recursive_mutex::lock() Line 95 C++dll!boost::interprocess::interprocess_recursive_mutex::lock() Line 165 C++dll!boost::interprocess::scoped_lock<boost::interprocess::interprocess_recursive_mutex>::scoped_lock<boost::interprocess::interprocess_recursive_mutex>(boost::interprocess::interprocess_recursive_mutex & m) Line 81 C++dll!boost::interprocess::segment_manager<char,boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,boost::interprocess::offset_ptr<void,__int64,unsigned __int64,0>,0>,boost::interprocess::iset_index>::priv_generic_named_construct<char>(unsigned char type, const char * name, unsigned __int64 num, bool try2find, bool dothrow, boost::interprocess::ipcdetail::in_place_interface & table, boost::interprocess::iset_index<boost::interprocess::ipcdetail::index_config<char,boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,boost::interprocess::offset_ptr<void,__int64,unsigned __int64,0>,0>>> & index, boost::interprocess::ipcdetail::bool_<1> is_intrusive) Line 1076 C++dll!boost::interprocess::segment_manager<char,boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,boost::interprocess::offset_ptr<void,__int64,unsigned __int64,0>,0>,boost::interprocess::iset_index>::priv_generic_construct(const char * name, unsigned __int64 num, bool try2find, bool dothrow, boost::interprocess::ipcdetail::in_place_interface & table) Line 760 C++dll!boost::interprocess::segment_manager<char,boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,boost::interprocess::offset_ptr<void,__int64,unsigned __int64,0>,0>,boost::interprocess::iset_index>::generic_construct<SharedMem_Info>(const char * name, unsigned __int64 num, bool try2find, bool dothrow, boost::interprocess::ipcdetail::in_place_interface & table) Line 705 C++dll!boost::interprocess::ipcdetail::named_proxy<boost::interprocess::segment_manager<char,boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,boost::interprocess::offset_ptr<void,__int64,unsigned __int64,0>,0>,boost::interprocess::iset_index>,SharedMem_Info,0>::operator()<char const (&)[17],int,int,int,int,bool,boost::interprocess::allocator<void,boost::interprocess::segment_manager<char,boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,boost::interprocess::offset_ptr<void,__int64,unsigned __int64,0>,0>,boost::interprocess::iset_index>> &>(const char[17] & <args_0>, int && <args_1>, int && <args_2>, int && <args_3>, int && <args_4>, bool && <args_5>, boost::interprocess::allocator<void,boost::interprocess::segment_manager<char,boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,boost::interprocess::offset_ptr<void,__int64,unsigned __int64,0>,0>,boost::interprocess::iset_index>> & <args_6>) Line 131 C++ It looks like it the segment manager was unable to get a mutex lock on the memory? But I don't believe I put a mutex lock on the segment manager from the other end. Everything works just fine if I am doing shared memory between two programs compiled with visual studio. So, it feels like somewhere some how memory alignment is off? Anybody ran into a similar issue before? Any help would be greatly appreciated! Thank you!!

4 5

Download permissions off
by Forwarding 29 Feb '20

29 Feb '20

Cannot seem to download sources. A sampling of directories, e.g. https://dl.bintray.com/boostorg/release/1.72.0/source/, all yield the following when choosing one of the archives:Forbidden!This is a new development, download was OK yesterday morning.Thx.-Matthew

2 1

(SOLVED) Re: [Boost.Test] duplicate symbol '_main' (manual test registration)
by Andrew McFarlane 29 Feb '20

29 Feb '20

Hello all, I just wanted to let you know that I figured out my problem. It had nothing to do with Boost.Test and had everything to do with my Makefile. My Makefile was literally telling g++ to try and compile main.cpp twice and place the output in bin. - I had defined an implicit rule to compile all .cpp files to .o files, like so: $(ODIR_TEST)/%.o : $(SDIR_TEST)/%.cpp $(CC) $(CXXFLAGS) -c $< -o $@ - And silly me, I wrote the default rule as follows: $(OUTDIR)/$(PROG) : $(SDIR_TEST)/main.cpp $(TEST_OBJS) $(CC) $(CXXFLAGS) -o $@ $^ $(TEST_OBJS) is just a list of all .o files prefixed with ./bin/. As you can imagine, taking $(SDIR_TEST)/main.cpp out of the list of prerequisites completely fixed the issue. I was able to compile and run all 34 tests successfully from one executable. Hurray!! It feels good to have figured this out, especially because I was able to do so on my own, but also makes me feel quite silly. Oh well, now I know. My apologies for burdening your inboxes with my stupidity. - AJ

1 0

Re: [Boost-users] Boost-users Digest, Vol 5327, Issue 1
by Andrew McFarlane 29 Feb '20

29 Feb '20

Okay, I have almost completely fixed my problems. I just spent the past hour: - creating test case headers for each test translation unit (don't worry, I sped this up using a macro hehe) - inserting static test case method declarations privately in said headers - eliminating method redefinitions by toying with test translation unit #includes I am ALMOST there. Going to start a new issue, as my current problem is now vastly different from what is stated in the subject line. Consider the original problem for this issue SOLVED. Cheers! On Fri, Feb 28, 2020 at 9:04 PM <boost-users-request(a)lists.boost.org> wrote: > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. [Boost.Test] linking with shared lib (cannot find main) > (Andrew McFarlane) > 2. Re: [Boost.Test] linking with shared lib (cannot find main) > (Andrew McFarlane) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 28 Feb 2020 18:50:38 -0800 > From: Andrew McFarlane <andrew.mcfarlane52(a)gmail.com> > To: Boost users list <boost-users(a)lists.boost.org> > Subject: [Boost-users] [Boost.Test] linking with shared lib (cannot > find main) > Message-ID: > < > CAG90r9S4rCVPXACn5o6zG9xZQe9oucr7zR6PYHKHqgdUGGJ1Bw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > I have been using Boost.Test for about a month now. Big fan so far, except > for the atrocious compilation times, hence why I am moving toward using the > shared library. > > using b2 to build and install Boost.Test's libs was simple enough, though > after making the noted changes here: > > https://www.boost.org/doc/libs/1_72_0/libs/test/doc/html/boost_test/adv_sce… > > to customize the module's entry point, g++ cannot find the main executable: > > Undefined symbols for architecture x86_64: > > "_main", referenced from: > > implicit entry/start for main executable > > ld: symbol(s) not found for architecture x86_64 > > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > > make: *** [Guest_T] Error 1 > > I tried digging through the docs for more information, but I came up short. > > For more context, I have written unit tests for each of my classes. For > example, if my classes were A, B, and C, I would have A_T.cpp, B_T.cpp, and > C_T.cpp for unit tests. > > - Should each of the unit tests have their own main() function? (I would > think not..) > > - If not, how do I instruct g++ to first compile main.cpp before attempting > to compile anything else? > > If you are curious, here are the contents of my Makefile: > > PROG := main > > CC := g++ > > SDIR := ../src > > PKG_DIRS := $(shell ls $(SDIR)) > > CXXFLAGS = -v -Wall -std=c++11 -I$(SDIR_TEST) \ > > $(addprefix -I$(SDIR)/,$(PKG_DIRS)) -I$(BOOST_ROOT) \ > > -L$(BOOST_LIBS) -Wl,-rpath,$(BOOST_LIBS) -lboost_unit_test_framework > > ODIR_TEST = ./bin > > SDIR_TEST = ./src > > OUTDIR = ./execs > > ODIR = ../sim/bin > > > TEST_EXEC_NAMES = $(notdir $(basename $(wildcard $(SDIR_TEST)/*.cpp))) > > > $(OUTDIR)/$(PROG) : $(SDIR_TEST)/main.cpp > > $(CC) $(CXXFLAGS) -o $@ $< > > > $(OUTDIR)/$(PROG) : $(TEST_EXEC_NAMES) > > $(CC) $(CXXFLAGS) -o $@ $^ > > > % : $(SDIR_TEST)/%.cpp > > $(CC) $(CXXFLAGS) -o $(OUTDIR)/$@ $^ > > >From what I can tell, g++ is failing to find the main the executable > because it is attempting to compile one of my unit test files first. This > may or may not be the case; either way, I would appreciate some help or > direction as to what I should read to learn more about this. > > Let me know if you need more info. > > Thanks in advance. > > - AJ >

1 0

[GSoC] Boost C++ and Slack channel
by Mateusz Loskot 27 Feb '20

27 Feb '20

Hi, I'm forwarding David's announcement copied below and available at https://lists.boost.org/Archives/boost/2020/02/248254.php You can join that Slack workspace at https://cppalliance.org/slack/ ML ------ Hi Boost community, we have a dedicated channel on Slack for all the discussions regarding the Google Summer of Code. Please join us on cpplang.slack.com on the channell #boost-gsoc. Cheers, David

1 0

[boost::regex] Build static library with ICU support on windows
by Eko palypse 27 Feb '20

27 Feb '20

I'm confused about the different post I've found on the web therefore would appreciate if someone could answer if it is possible to build a static regex library with ICU support on windows? Thank you Eren

2 2