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

Unable to build universal binary on Mac OS X
by Kevin Molcard 27 Nov '14

27 Nov '14

Hi all, I am trying to compile boost on Mac OS X 10.9.5 for 32 and 64 bit. I am using the following command: ./b2 link=static threading=multi architecture=x86 address-model=32_64 I get the following error message: darwin.compile.c++.pch bin.v2/libs/math/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/link-static/threading-multi/../src/tr1/pch.hpp.gch clang: error: cannot use 'precompiled-header' output with multiple -arch options "g++" -x c++-header -O3 -finline-functions -Wno-inline -Wall -gdwarf-2 -fexceptions -arch i386 -arch x86_64 -DBOOST_ALL_NO_LIB=1 -DBOOST_BUILD_PCH_ENABLED -DNDEBUG -I"." -I"libs/math/src/tr1" -c -o "bin.v2/libs/math/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/link-static/threading-multi/../src/tr1/pch.hpp.gch" "libs/math/build/../src/tr1/pch.hpp" ...failed darwin.compile.c++.pch bin.v2/libs/math/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/link-static/threading-multi/../src/tr1/pch.hpp.gch... Then 144 targets are skipped. Does anyone knows how to fix this? Thanks in advance Kevin

2 2

[review] [sort] Sort library review manager results
by Edward Diener 27 Nov '14

27 Nov '14

This is the results from the recent review of the Sort library of Steven Ross. First I would like to thank all those who made comments during the review, whether or not they officially gave a final Yes or No vote to whether the Sort library should be accepted as a Boost library. This list includes: Niall Douglas, Julian Gonggrijp, Phil Endecott, Vladimir Prus, Mathias Gaunard, Jeremy Murphy, Peter Dimov, Robert Ramey, Adam Walling, Anthony Polukhin, Phil Endecott, Paul Bristow, Thijs (M.A.) van den Berg Dupuis Etienne, and Frank Gennari If I have missed anyone I do apologize. Secondly I would like to thank Steven Ross for patiently answering all of the review comments to the best of his ability. My tally of Yes and No votes for acceptance are: Yes votes (5) : Niall Douglas ( conditional ), Julian Gonggrijp ( conditional ), Frank Gennari, Phil Endecott, Paul Bristow. No votes (3) : Vladimir Prus, Adam Walling ( conditional ), Anthony Polukhin I believe the condtional Yes vote from Julian Gonggrijp was completely met in the discussions of issues with Steven Ross and the conditional Yes vote from Niall Douglas was almost completely met in the discussion with Steven Ross about the issues mentioned, and enough to maintain his Yes vote. I want to also mention that the conditional No vote by Adam Walling has an implied Yes vote to it if the Sort library were one among other sort implementations. Since my final decision is not entirely based on the Yes and No votes I want to adumbrate some of the major issues brought up by the review without necessarily focussing on every one of the people who brought them up initially, as well as my own reactions to them as Review Manager. 1) The first major issue was whether a library whose basic merit lies in its algorithm and its speed/space constraints needs better theoretical backing. A number of reviewers discussed this after it was brought up. I tend to agree with reviewers that while the best theoretical basis is always desirable, it is not necessary for a Boost library whose empirical evidence can be and has been measured by its implementor and can be measured by any user. Furthermore Steven Ross has provided an extensive discussion in his documentation, as well as his original paper, about the theoretical merits of his technique. While much of this discussion is probably beyond the understanding of any but sorting experts and afficionados enough of it adequately explains the basic ideas behind SpreadSort for those who understand and have knowledge of basic sorting ideas and popular sorting techniques. 2) An important issue is the need for the Sorting library to provide extensive timing charts/tables comparing SpreadSort to at least std::sort ( and possibly other popular mainstream sorts ) with both different numbers of sort keys and different initial unsorted distributions. Steven Ross has been providing these charts/tables in the 'develop' branch of the library. 3) Connected to the previous issue is that a number of reviewers asked for better documentation on the conditions in which SpreadSort will show a marked improvement in speed compared to std::sort, as well as any condition(s) where SpreadSort performs worse than std::sort. While Steven Ross has explained that generally SpreadSort will fall back to using std::sort for some cases ( low N ), I too feel that the documentation needs to be more extensive for the average user in attempting to delineate the conditions where SpreadSort works best. 4) A really important issue discussed by a number of reviewers involves the creation of a synthetic radix, where most users of sorting algorithm are used to comparison based sorting functors. While the documentation provides information on the various individual sorts, as well as examples, I also feel that a discussion in the documentation of how to use SpreadSort when sorting structs/classes with multiple keys of different types would be invaluable. In other words, what and if are the common techniques for using SpreadSort with complicated keys which, when using comparison-based sorting, can be represented fairly easily be a functor. 5) Niall Douglas brought up the issue of exception guarantees when using SpreadSort, and I concur. The documentation should be stronger specifying what happens during the sorting algorithms if an exception occurs and/or does the sorting algorithm itself ever throw any exceptions and, if so, under what conditions. Steven Ross mentioned that he is adding exception guarantee information to his docs. 6) Many reviewers did not like the idea that the library should be called Sort when it is basically implementing a single sorting algorithm called SpreadSort. Alternate suggestions are: a) The library should be called SpreadSort. b) The library can be called Sort only if other sorting algorithms are added to it. c) The library can be called Sort with the proviso that it serves as a general library for sorting algorithms potentially added to it in the future. d) The library should be part of the Boost Algorithm library. Steven Ross mentioned other potential sorting implementations as part of the Sort library, under that general name, but all providing a good deal of extra work. These included a copy-based stable sorting algorithm, an LSD radix sorting, and an OpenMP based parallel implementation. Other reviewers mentioned some of the same types of sorting implementations and a few reviewers remarked that they also have created sorting implementations of their own. While I will give my own view at the end, I would like to mention here that I strongly believe that each sorting implementation needs to be reviewed separately for acceptance into Boost and never automatically added to a general library, whether it be called Sort or Algorithm or whatever. 7) Random issues brought up in comments I will mention, which have importance but which I do not believe are absolutely intrinsic yet still might be considered. a) C++11 techniques in general and inline namespaces in particular. b) A version that can work with less than random access. c) Optimizations for small sets of data ( Steven Ross has already addressed this to an extent in the 'developer' branch of the library ). d) Possible documentation of using SpreadSort as a subsort for parallel sorting techniques and possible discusion in the docs about SpreadSort and parallel sorts. e) General O() information in docs. f) SpreadSort examples hoisted directly into docs using Quickbook technique and updating the Spreadort docs to use Quickbook. Review Result: Based on the voting for acceptance or not, based on the discussions during the review period, and based on Steven Ross's responses, I have decided that Steven Ross's library should be accepted into Boost. My main reason for my decision, aside from the votes and comments and specific issues discussed, is twofold: 1) There is a general consensus that Steven Ross has an excellent understanding of sorting techniques and algorithms and will support and refine his library for the benefit of programmers. 2) The empirical tests show that SpreadSort offers an improvement over std::sort, significantly in the area of large data sets, and this could be a major benefit to programmers. I do not know if the review manager has a say in this but based on the remarks of the reviewers I would like to see the library as accepted be named 'SpreadSort' rather than just 'Sort'. I do think that Boost can have a library called 'Sort' but I agree with the general consensus that a 'Sort' library needs more than one type of sorting algorithm. I would like to see other people, who mentioned in the reviews/comments that they have their own sorting implementation, also submit their own implementations to Boost and, if this happens and they are accepted, I can see combining them with 'SpreadSort' into a general Boost sorting library called 'Sort' in the future.

1 0

Boost not compiling with arm-cross-compiler
by ustulation 27 Nov '14

27 Nov '14

{Ubuntu 14.04 64 bits, arm-g++ compiler 4.9 one that comes with google's ndk r10c) (The compiler has --sysroot pointing to platform android-14, and -march=armv7-a) on using arm cross-compiler for compiling boost I get the following error in "*socket_ops.ipp*": *<1> for all function (templates) of this type:* template <typename SockLenType> inline int call_getsockname(SockLenType msghdr::*, socket_type s, socket_addr_type* addr, std::size_t* addrlen) { SockLenType tmp_addrlen = (SockLenType)*addrlen; int result = ::getsockname(s, addr, &tmp_addrlen); *addrlen = (std::size_t)tmp_addrlen; return result; } /some-path/thirdparty/boost/boost_1_55_0_Android/boost/asio/detail/impl/socket_ops.ipp:1639: error: invalid conversion from 'int*' to 'socklen_t* {aka unsigned int*}' [-fpermissive] int result = ::getsockname(s, addr, &tmp_addrlen); ^ On changing the line to: int result = ::getsockname(s, addr, (socklen_t*)tmp_addrlen); it compiles fine ofcourse but i don't know if this is what is to be done. *<2> And in "mapped_region.hpp": /some-path/thirdparty/boost/boost_1_55_0_Android/boost/interprocess/mapped_region.hpp:49: error: sys/shm.h: No such file or directory # include <sys/shm.h> //System V shared memory... ^ * and points to: # if defined(BOOST_INTERPROCESS_XSI_SHARED_MEMORY_OBJECTS) # include <sys/shm.h> //System V shared memory... # endif in that file. Here are the flags in my user-config.jam file: using gcc : android : @AndroidNDKSrcDir@/bin/arm-linux-androideabi-g++ : <archiver>@AndroidNDKSrcDir@/bin/arm-linux-androideabi-ar <compileflags>-fexceptions <compileflags>-frtti <compileflags>-fPIC <compileflags>-std=c++11 <compileflags>-ffunction-sections <compileflags>-funwind-tables <compileflags>-D__ARM_ARCH_5__ <compileflags>-D__ARM_ARCH_5T__ <compileflags>-D__ARM_ARCH_5E__ <compileflags>-D__ARM_ARCH_5TE__ <compileflags>-Wno-psabi <compileflags>-march=armv5te <compileflags>-mtune=xscale <compileflags>-msoft-float <compileflags>-mthumb <compileflags>-Os <compileflags>-fomit-frame-pointer <compileflags>-fno-strict-aliasing <compileflags>-finline-limit=64 <compileflags>-I@AndroidNDKSrcDir@/include/c++/4.9 <compileflags>-Wa,--noexecstack <compileflags>-DANDROID <compileflags>-D__ANDROID__ <compileflags>-DNDEBUG <compileflags>-O2 <compileflags>-g <compileflags>-I@AndroidNDKSrcDir@/sysroot/usr/include <architecture>arm <compileflags>-fvisibility=hidden <compileflags>-fvisibility-inlines-hidden <compileflags>-fdata-sections <cxxflags>-D__arm__ <cxxflags>-D_REENTRANT <cxxflags>-D_GLIBCXX__PTHREADS ; *What is the way forward for those two errors - <1> and <2> above ?* -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-not-compiling-with-arm-cross-compi… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

[boost::accumulators::impl::immediate_mean_impl<Sample, Tag>::operator()<Args>] c++/cli
by It neophyte 26 Nov '14

26 Nov '14

Hi While computing a variance on my dataset, I end up with: error C2677: binary '+' : no global operator found which takes type 'System::Object ^const ' (or there is no acceptable conversion) The error message point to the line 65 of mean.hpp (see below piece of code). Can someone explain what's going wrong? Thanks template<typename Args> // line 59 void operator ()(Args const &args) //line 60 { // line 61 std::size_t cnt = count(args); // line 62 this->mean = numeric::fdiv( // line 63 (this->mean * (cnt - 1)) + args[parameter::keyword<Tag>::get()] // line 64 , cnt // line 65 ); // line 66 } // line 67 my code: #pragma once#include "stdAfx.h"#include "math.h"#include <boost/accumulators/accumulators.hpp>#include <boost/accumulators/statistics/stats.hpp>#include <boost/accumulators/statistics/variance.hpp> ..... accumulator_set< double, stats<tag::variance> > acc_variance; DataRow^i; for (int i=1;i-1<dbdataset->Rows->Count-1;i++){ dbdataset->Rows[i-1]["DataRet"]=log(System::Convert::ToDouble(dbdataset- >Rows[i-1]["Pop"])/System::Convert::ToDouble(dbdataset->Rows[i]["Pop"])); acc_variance(dbdataset->Rows[i-1]["DataRet"]); lblvol->Text = Convert::ToString(sqrt(variance(acc_variance))); }

1 0

boost::filesystem::extension crashes on Linux
by Jürgen Simon 26 Nov '14

26 Nov '14

Hello, I have a crash with boost 1.56 that happens on SUSE Linux for me (uname -a : Linux r105b.meteo.uni-bonn.de 3.7.10-1.28-desktop #1 SMP PREEMPT Mon Feb 3 14:11:15 UTC 2014 (c9a2c6c) x86_64 x86_64 x86_64 GNU/Linux) The crash happens in filesystem::extension() when listing a file from the following directory: $ ls -la core total 29802736 drwxr-xr-x 2 simon users 4096 Nov 25 14:40 . drwxr-xr-x 7 simon users 4096 Nov 25 15:05 .. -rw-r--r-- 1 simon users 30517985568 Nov 14 2013 rico.out.xy.core.nc As you can see there’s only one file in there that ends on “.nc”. The following code crashes on Linux but works fine on OSX (with the same data): fs::path f = fs::path(source_path); std::string extension = fs::extension(f); The GDB backtrace is: #0 0x00007fffe09403d5 in raise () from /lib64/libc.so.6 #1 0x00007fffe0941858 in abort () from /lib64/libc.so.6 #2 0x00007fffe11438cd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #3 0x00007fffe11419c6 in ?? () from /usr/lib64/libstdc++.so.6 #4 0x00007fffe11419f3 in std::terminate() () from /usr/lib64/libstdc++.so.6 #5 0x00007fffe1141c1e in __cxa_throw () from /usr/lib64/libstdc++.so.6 #6 0x00007fffe119336d in std::__throw_runtime_error(char const*) () from /usr/lib64/libstdc++.so.6 #7 0x00007fffe115e844 in std::locale::facet::_S_create_c_locale(__locale_struct*&, char const*, __locale_struct*) () from /usr/lib64/libstdc++.so.6 #8 0x00007fffe1153774 in std::locale::_Impl::_Impl(char const*, unsigned long) () from /usr/lib64/libstdc++.so.6 #9 0x00007fffe11547af in std::locale::locale(char const*) () from /usr/lib64/libstdc++.so.6 #10 0x00007ffff753036f in boost::filesystem::path::codecvt() () from /usr/local/lib/libboost_filesystem.so.1.55.0 #11 0x00007ffff75307ff in boost::filesystem::path::begin() const () from /usr/local/lib/libboost_filesystem.so.1.55.0 #12 0x00007ffff7530f88 in boost::filesystem::path::compare(boost::filesystem::path const&) const () from /usr/local/lib/libboost_filesystem.so.1.55.0 #13 0x00007ffff75310f4 in boost::filesystem::path::extension() const () from /usr/local/lib/libboost_filesystem.so.1.55.0 #14 0x0000000000448adb in boost::filesystem::extension (p=...) at /usr/local/include/boost/filesystem/convenience.hpp:36 Any ideas how to circumvent this problem? Jürgen

1 0

[Boos-users][Boost.accumulators.Statistics.variance.hpp]: How to Compute Sample Volatility on data stored in DataTable
by It neophyte 26 Nov '14

26 Nov '14

Hi Do you know how can I compute a sample volatility of the returns held in a particular column of my db Datable? Any code illustration would be appreciated. Best,

1 0

[accumulators->Statistics] How to Compute Sample Volatility_c++ Windows Form app
by It neophyte 25 Nov '14

25 Nov '14

Dear All Do you know how can I compute the sample volatility (sqrt(variance)) of the returns held in my Datable? For information, my db object contains a column "Return" which has been filled with values. DataTable^db=gcnew DataTable(); Thanks in advance Heron

1 0

Re: [Boost-users] fusion: map
by MM 25 Nov '14

25 Nov '14

Hi, At the point of _defining_ a fusion::map, do the key types have to be known or can they just be forward declared at that point? Rds,

1 0

Phoenix V2
by Mathieu Champlon 25 Nov '14

25 Nov '14

Hello, Has Phoenix V2 been removed from Boost 1.57 ? I used to be able to find it under boost/spirit/home/phoenix but it seems it's no longer the case. Thanks, MAT.

3 5

Re: [Boost-users] lockfree::spsc_queue & move semantics
by Thomas Danckaert 24 Nov '14

24 Nov '14

From: Bjorn Reese <breese(a)mail1.stofanet.dk> Subject: Re: [Boost-users] lockfree::spsc_queue & move semantics Date: Mon, 10 Nov 2014 20:39:24 +0100 > On 11/09/2014 09:49 PM, Thomas Danckaert wrote: >> I'd like to use a spsc_queue of unique_ptr's to bigger objects, to >> transfer ownership between threads. That way, I can create/allocate an > > This limitation inherited from atomic, and I am afraid that it is a > bit more complicated than adding a move constructor. Fortunately, > there > is a C++ proposal to address the problem: > > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4058.pdf Is this really the issue here? What I'm trying to do is not the same as what's discussed in the proposal, as the reading/writing of the unique_ptr doesn't have to be an atomic operation in my case. I just want to push a unique_ptr onto the queue, and spsc_queue can store all kinds of objects, which are not atomic either. It only uses atomic operations to keep track of the write and read indices, and those parts of the code don't need to be modified to make this work. As far as I see, the main problem storing unique_ptr's (or any other non-copyable but moveable object), is that the code relies on a copy constructor to store objects in its internal buffer. I added an overload using a move constructor and that seems to work (though I'm quite new to multi-threading or lockfree programming, so I could be missing some potential issues). Thomas

2 1