July 2014 - Boost - lists.preview.boost.org

[boostdep] Unable to build on 'develop' branch
by Edward Diener 18 Jul '14

18 Jul '14

When I try to build boostdep on the 'develop' branch with gcc-4.8.1 I get: > gcc.compile.c++ ..\..\..\bin.v2\tools\boostdep\src\gcc-mingw-4.8.1\release\link-static\boostdep.o > boostdep.cpp: In function 'void scan_module_dependencies(const string&, module_primary_actions&)': > boostdep.cpp:193:46: error: no matching function for call to 'std::basic_ifstream<char>::basic_ifstream(const value_type*)' > std::ifstream is( it->path().c_str() ); > ^ > boostdep.cpp:193:46: note: candidates are: > In file included from ..\..\../boost/filesystem/operations.hpp:46:0, > from ..\..\../boost/filesystem.hpp:17, > from boostdep.cpp:11: > c:\utilities\mingwcurrent\lib\gcc\mingw32\4.8.1\include\c++\fstream:467:7: note: std::basic_ifstream<_CharT, _Traits>::basic_ifstream(const char*, std::ios_base::openmode) [with _CharT = char; _Traits = std::char_traits<char>; std::ios_base::openmode = std::_Ios_Openmode] > basic_ifstream(const char* __s, ios_base::openmode __mode = ios_base::in) > ^ > c:\utilities\mingwcurrent\lib\gcc\mingw32\4.8.1\include\c++\fstream:467:7: note: no known conversion for argument 1 from 'const value_type* {aka const wchar_t*}' to 'const char*' > c:\utilities\mingwcurrent\lib\gcc\mingw32\4.8.1\include\c++\fstream:453:7: note: std::basic_ifstream<_CharT, _Traits>::basic_ifstream() [with _CharT = char; _Traits = std::char_traits<char>] > basic_ifstream() : __istream_type(), _M_filebuf() > ^ > c:\utilities\mingwcurrent\lib\gcc\mingw32\4.8.1\include\c++\fstream:453:7: note: candidate expects 0 arguments, 1 provided > c:\utilities\mingwcurrent\lib\gcc\mingw32\4.8.1\include\c++\fstream:427:11: note: std::basic_ifstream<char>::basic_ifstream(const std::basic_ifstream<char>&) > class basic_ifstream : public basic_istream<_CharT, _Traits> > ^ > c:\utilities\mingwcurrent\lib\gcc\mingw32\4.8.1\include\c++\fstream:427:11: note: no known conversion for argument 1 from 'const value_type* {aka const wchar_t*}' to 'const std::basic_ifstream<char>&' > In file included from ..\..\../boost/filesystem/path_traits.hpp:23:0, > from ..\..\../boost/filesystem/path.hpp:25, > from ..\..\../boost/filesystem.hpp:16, > from boostdep.cpp:11: > ..\..\../boost/system/error_code.hpp: At global scope: > ..\..\../boost/system/error_code.hpp:221:36: warning: 'boost::system::posix_category' defined but not used [-Wunused-variable] > static const error_category & posix_category = generic_category(); > ^ > ..\..\../boost/system/error_code.hpp:222:36: warning: 'boost::system::errno_ecat' defined but not used [-Wunused-variable] > static const error_category & errno_ecat = generic_category(); > ^ > ..\..\../boost/system/error_code.hpp:223:36: warning: 'boost::system::native_ecat' defined but not used [-Wunused-variable] > static const error_category & native_ecat = system_category(); Similar error occurs if I build with clang. Anybody know what the problem is ? I pulled the latest for all submodules on 'develop'.

2 4

Parallel Sorting Algorithms
by Melkowski, Kevin M. (MU-Student) 17 Jul '14

17 Jul '14

I noticed on the google summer of code page that multi-threading and sorting algorithms such as the Radix Sort was a big interest right now. I’ve been developing an open-sourced parallel Radix Sort for a while now and wanted to submit it to a library. This algorithm sorts positive and negative values for each standard data type. The code I have can be found here: https://github.com/Kevincav/Radix-Sort. When running tests for this, on my laptop I managed to sort 1 billion uniformly distributed floats in about 45 seconds. When I tested std::sort with the same test it never finished, it sorted 100 million floats finished around that time though. This is optimized for both C and C++ programs, the documentation isn’t done yet so that’s one thing I still need to finish. This is my first post and I tried to follow the guidelines, hopefully it wasn’t a bad first post. Thanks for reading, Kevin

1 0

[detail] Disabling Warnings in Jamfile
by Axel Ismirlian 17 Jul '14

17 Jul '14

I am trying to build and compile the detail tests on AIX 6.1 with gcc, but there is one small problem on the very last test: gcc.compile.c+ + ../bin.v2/libs/detail/test/container_fwd/container_fwd_debug.test/gcc-4.8.1/debug/container_fwd_test.o In file included from /opt/freeware/lib/gcc/powerpc-ibm-aix6.1.0.0/4.8.1/include/c+ +/cstddef:41:0, from ../boost/config/select_stdlib_config.hpp:18, from ../boost/config.hpp:44, from ../boost/detail/container_fwd.hpp:16, from ../libs/detail/test/container_fwd/container_fwd_test.cpp:6: /opt/freeware/lib/gcc/powerpc-ibm-aix6.1.0.0/4.8.1/include/c+ +/powerpc-ibm-aix6.1.0.0/bits/c++config.h:277:4: error: #warning currently using inlined namespace mode which may fail without inlining due to lack of weak symbols [-Werror=cpp] # warning currently using inlined namespace mode which may fail \ ^ cc1plus: all warnings being treated as errors "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -pedantic -Werror -g -fPIC -fpermissive -g -ftemplate-depth-300 -pedantic -Wstrict-aliasing -fstrict-aliasing -Wextra -Wsign-promo -Wunused-parameter -Wconversion -DBOOST_ALL_NO_LIB=1 -D_GLIBCXX_DEBUG -D_STLP_DEBUG -I".." -c -o "../bin.v2/libs/detail/test/container_fwd/container_fwd_debug.test/gcc-4.8.1/debug/container_fwd_test.o" "../libs/detail/test/container_fwd/container_fwd_test.cpp" If I disable warnings being treated as errors through the Jamfile, the test functions correctly, but how do I customize the Jamfile file for AIX? Is it ok for me to simply ignore this warning? Also I was having a difficult time fully understanding what an inlined namespace is.

1 0

merging the super-project
by Eric Niebler 17 Jul '14

17 Jul '14

I recently made a tweak to the .gitignore of the super-project on the develop branch. How do I merge that to master? The two branches have different histories, so a regular git merge balks. And when I checkout master (thinking I'll just cherry-pick), I end up with a slew of local changes (which I haven't made). Befuddled, Eric

4 5

1.56.0 beta release candidate 2 available for testing
by Marshall Clow 16 Jul '14

16 Jul '14

The second release candidate files for 1.56.0 beta are available at http://boost.cowic.de/rc/ 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. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: MD5 (boost-1_56_0_b1_rc2.7z) = cd6267325a8dadbb82b384c4776ee450 MD5 (boost-1_56_0_b1_rc2.tar.bz2) = b74cd72043b6b2fa16c6690633acb422 MD5 (boost-1_56_0_b1_rc2.tar.gz) = b51810be6737e73a4deee70e84895ca7 MD5 (boost-1_56_0_b1_rc2.zip) = f4ceb73492ae7d9b1843d841498850e5 Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively. Besides bug fixes the TypeIndex library has been included, and I think that the problems that mjklaim(a)gmail.com was seeing have been fixed. I would like to post this to SourceForge Thursday night/Friday morning, if possible. Thank you. --The release managers

7 12

[pool] block_ptr
by Phil Bouchard 16 Jul '14

16 Jul '14

Hi Boost... long time, In my memory manager: https://svn.boost.org/svn/boost/sandbox/block_ptr/boost/detail/block_base.h… You will see the usage of: boost::singleton_pool<pool, sizeof(char)> because of a required is_from() function call. But I just came to realize there is a pool::is_from() function: http://www.boost.org/doc/libs/1_49_0/libs/pool/doc/html/boost_pool/pool/int… Is that function new or in 2011 I overlooked it? If so I will make the change ASAP as this is a nice class. Regards, -Phil www.finitetheory.com

1 0

[core] Breaking change to boost::ref in 1.56
by Eric Niebler 16 Jul '14

16 Jul '14

(Repost in a new thread) While investigating a failure[^1] in proto, I discovered the following change to boost::ref: https://github.com/boostorg/core/commit/af629ffa59094048c335609f285afe342fd… This failure was caused by the following change to boost::ref by Agustín Bergé (K-ballo): https://github.com/boostorg/core/commit/af629ffa59094048c335609f285afe342fd… I didn't see any discussion about this change. (Was there one?) I can guess why it was made: to make boost::ref behave like std::ref, which does "reference collapsing" with reference_wrapper (which IMO is broken, and I unsuccessfully argued that in the committee when this was voted in). The problem is, it's a breaking interface change to one of the oldest, most heavily used, and stable pieces of Boost. It pretty massively breaks a major part of Boost.Proto's interface (proto::make_expr). I've hacked around the problem in Proto's tests, but this is going to break end-user code, and I don't know what I'm going to tell people. I don't like differences between boost and std. But I also don't like breaking code. What do we want here? Eric [^1]: http://www.boost.org/development/tests/develop/developer/output/teeks99-03j…

6 29

[chrono] Stopwatches
by Daniel James 15 Jul '14

15 Jul '14

Hi, What's the status for stopwatches? Because it's in chrono's metadata file, it's in the list at: http://www.boost.org/doc/libs/master/ Which will also put it in the release documentation list. But there's no documentation to link to, the headers don't get linked by 'b2 headers', and the tests don't seem to be running. Daniel

2 3

Re: [boost] 1.56.0 beta 1 release candidates available for testing
by Klaim - Joël Lamotte 15 Jul '14

15 Jul '14

Once again with previously attached log available there: https://www.dropbox.com/s/8x7727pxqcs9shg/20140715-0053-build_boost_github_… On Tue, Jul 15, 2014 at 1:22 AM, Klaim - Joël Lamotte <mjklaim(a)gmail.com> wrote: > > Hi, > > I just tried to compile the last master > ( a87533ad69d761536cd395501e09719349fc9173 ) which I suppose is equivalent > to the incoming second beta? > I compiled it with with VS2013 Update 2 in 32 and 64 bits, using the > following script: > > pushd .\boost_github > call bootstrap.bat > call b2 --prefix=../boost --buid-type=complete toolset=msvc-12.0 > architecture=x86 install > call b2 --prefix=../boost --buid-type=complete > --libdir=../boost/lib/x64 toolset=msvc-12.0 architecture=x86 > address-model=64 install > popd > > I found a fatal error: > > .\boost/preprocessor/iteration/detail/iter/forward1.hpp(47) : fatal > error C1083: Cannot open include file: > 'boost/utility/detail/result_of_iterate.hpp': No such file or directory > > It's preventing the thread and coroutine libraries to be compiled but only > in non-debug 32 bit (if I understand the logs correctly). > I attached the full log to this email, in case it helps. > > >

1 1

[git] Releases tags
by Adam Wulkiewicz 14 Jul '14

14 Jul '14

Hi, Is there a global policy regarding the way how/when/by whoom tags are created for releases and release candidates? In each submodule there are tags corresponding to the releases (e.g. boost-1.54.0-beta1, boost-1.55.0, etc.). Are they created somehow globally? When a tag is created for the main module is it automatically a tag of the submodule? Or must tags be created manually/separately in each submodule? Of course not counting some private tags. If the former is true, I'm guessing that private tags should have the names reserved for the releases tags? If the latter is true, are they created by the maintenance team or should the authors handle it themselves? Regards, Adam

2 1