January 2017 - Boost - lists.preview.boost.org

Moving away from SourceForge
by Louis Dionne 26 Jan '17

26 Jan '17

Hi, I know this has been discussed in the past, but I would like to revive the discussion about moving away from SourceForge as Boosts' release hosting provider. SourceForge has at least the following issues: - There is no way of controlling the format when downloading an archive of the latest release. This can break people that rely on this in their CI scripts. For example, Metabench's[1] CI was broken for a while when the archive changed from .bz2 to .zip. - SourceForge has been in the middle of some controversies[2]. - Their reliability has not been so great. In the past year, I've had quite a few of my Travis jobs fail due to SourceForge being unresponsive. There are most likely other concerns, but these are the ones that really bite me as a user right now. Am I the only one? If there's some push to do the move, the two main candidates I see would be - GitHub's native hosting - Bintray Thoughts? Louis [1]: https://github.com/ldionne/metabench [2]: https://en.wikipedia.org/wiki/SourceForge#Controversies -- View this message in context: http://boost.2283326.n4.nabble.com/Moving-away-from-SourceForge-tp4691184.h… Sent from the Boost - Dev mailing list archive at Nabble.com.

9 17

Boost.Endian - endian_buffer requirements
by Vicente J. Botet Escriba 26 Jan '17

26 Jan '17

Hi, I wanted to put an Int wrapper inside a endian_buffer and I have some compiler errors depending on whether it is aligned ort not. http://melpon.org/wandbox/permlink/k52wH2A7yagL2vMP I was expecting that the endian_buffer would make abstraction of the wrapped type and consider it just as a sequence of bytes, but it seems that it instead works only for some builtin integral. Am I missing something? Was this restriction intended? Could this restriction be removed and if yes, how? Best, Vicente

1 2

[program_options] implicit value and non-adjacent tokens
by Vladimir Prus 25 Jan '17

25 Jan '17

Hi, some time ago, program_options was modified so that options with implicit value would only take value from the same token. Previously, one could have: ./program -a foo -b # uses 'foo' as value for 'a' ./program -a -b # uses some default value for 'a' ./program -b # has no value for 'a' Now, the first syntax interprets 'foo' as positional option, and one has two write ./program -a=foo Ever since, I hear concerns from users about this behavior. Maybe not very loud, but quite consistent. Maybe, the new behavior is not very good, indeed, because it now mixes syntax matter (whether value is in the same token) with semantic matter (whether an option has implied value). I am considering reverting this change for next version of Boost. Does anybody have opinions either way? Thanks, Volodya

3 5

C++Now / BoostCon 2017 -- Call For Submissions
by Michael Caisse 23 Jan '17

23 Jan '17

This is a quick reminder that the C++Now 2017 Call For Submissions is *open*. All submissions must be made by February 3rd. For more information, see http://cppnow.org/

1 0

boost build with emscripten
by Emil Dotchevski 23 Jan '17

23 Jan '17

I see that there is now emscripten support in boost build but it doesn't seem to work for me. After installing emscripten on Windows, adding using emscripten ; in my site-config.jam, then running b2 from the emscripten command prompt, I get the output below. Any help greatly appreciated! Emil boost-build/src/build\property.jam:743: in class(a)property-map.find from module object(property-map)@26 error: Ambiguous key boost-build/src/build\type.jam:333: in generated-target-ps from module type boost-build/src/build\type.jam:270: in type.generated-target-suffix from module type boost-build/src/build\virtual-target.jam:509: in virtual-target.add-prefix-and-suffix from module virtual-target boost-build/src/build\virtual-target.jam:468: in _adjust-name from module object(file-target)@3764 boost-build/src/build\virtual-target.jam:253: in abstract-file-target.__init__ from module object(file-target)@3764 boost-build/src/build\virtual-target.jam:561: in class(a)file-target.__init__ from module object(file-target)@3764 boost-build/src/kernel\class.jam:90: in class.new from module class boost-build/src/build\generators.jam:558: in generated-targets from module object(C-compiling-generator)@138 boost-build/src/build\generators.jam:453: in construct-result from module object(C-compiling-generator)@138 boost-build/src/build\generators.jam:412: in run-really from module object(C-compiling-generator)@138 boost-build/src/build\generators.jam:386: in class(a)generator.run from module object(C-compiling-generator)@138 boost-build/src/build\generators.jam:994: in try-one-generator-really from module generators boost-build/src/build\generators.jam:1056: in try-one-generator from module generators boost-build/src/build\generators.jam:1294: in construct-really from module generators boost-build/src/build\generators.jam:1378: in generators.construct from module generators boost-build/src/build\targets.jam:1553: in construct from module object(typed-target)@3554 boost-build/src/build\targets.jam:1353: in class(a)basic-target.generate from module object(typed-target)@3554 boost-build/src/build\targets.jam:774: in generate-really from module object(main-target)@3735 boost-build/src/build\targets.jam:746: in class(a)main-target.generate from module object(main-target)@3735 boost-build/src/build\targets.jam:895: in targets.generate-from-reference from module targets boost-build/src/build\targets.jam:1266: in generate-dependencies from module object(typed-target)@2173 boost-build/src/build\targets.jam:1323: in class(a)basic-target.generate from module object(typed-target)@2173 boost-build/src/build\targets.jam:774: in generate-really from module object(main-target)@2988 boost-build/src/build\targets.jam:746: in class(a)main-target.generate from module object(main-target)@2988 boost-build/src\build-system.jam:714: in load from module build-system NT\..\..\munch\boost-build\src\kernel\modules.jam:295: in import from module modules NT\..\..\munch\boost-build\src\kernel\bootstrap.jam:139: in boost-build from module NT\..\..\munch\boost-build.jam:6: in module scope from module

3 8

Re: [boost] [interprocess] Getting boot-up time is unreliable on Windows
by Ion Gaztañaga 23 Jan '17

23 Jan '17

On 22/12/2016 10:01, Thomas Dahms wrote: > Dear developers, dear Ion, > > We are experiencing issues on Windows where boost::interprocess relies > on a certain event in the system event log to get the system's boot-up > time. This has proven to be unreliable, because that event is not always > present in the log. In that case, initialization of boost::interprocess > fails. > Several bug reports exist for that issue, e.g. [1, 2]. > > Report [1] contains a proposed fix to use GetTickCount64() and there is > an open PR with an alternative fix to fall back to WMI mechanisms [3]. I > understand that the fix [1] would need some polishing, because > GetTickCount64() is not available in pre-Vista. > > Nevertheless, both proposed fixes have been uncommented and unconsidered > for a while now. Is there any chance that the maintainers could look > into this? Thanks for the ping. I don't think GetTickCount64 is very reliable, as other methods also have problems with time correction, hibernation, fast bootup, etc. In [1] one the last bootup log is lost new processes won't be able to communicate with others. The same happens with [3] In http://www.boost.org/doc/libs/1_63_0/doc/html/interprocess/acknowledgements… there are some instructions to give up on kernel persistence and define the directory at compile time or run-time. This is the best workaround so far. I've trying to find a solution with no luck. I tried: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters\BootId in modern Windows systems but hybrid shutdown (default since Windows 8) does not seem to update it as kernel is suspended. Searching for a unique bootup id in windows that does not suffer when hibernating or correcting the RTC is really complicated. Any suggestion welcomed. Best, Ion

2 1

[serialization][test] failures in serialization causing regressions
by Barend Gehrels 21 Jan '17

21 Jan '17

Hi, The regression matrix in develop of Boost.Geometry contains many new compilation failures due to: 1) : D:\t08\run\boost_root\boost/serialization/array.hpp(25) : error C2039: 'array' : is not a member of 'std' 2): ../boost/numeric/ublas/storage.hpp: In member function ???void boost::numeric::ublas::unbounded_array<T, ALLOC>::serialize(Archive&, unsigned int)???: ../boost/numeric/ublas/storage.hpp:331:18: error: ???make_array??? is not a member of ???boost::serialization??? ar & serialization::make_array(data_, s);and a The master is still OK. Can this be solved? Regards, Barend

6 9

Boost Cmake Modules
by Paul Fultz II 20 Jan '17

20 Jan '17

Hi All, So I would like to start work with adding support for cmake to boost libraries. To make the boilerplate needed to write some of the cmake, I wrote BCM(Boost Cmake Modules), here: https://boost-cmake.github.io/bcm/doc/html/ Of course, the documentation is still a WIP. The core part is bcm_boost_package. So to write cmake for a library, you would just write something like this: bcm_boost_package(core VERSION 1.0 DEPENDS config ) It also provides a mechanism to add tests as well. My goal at first would be to update libraries on per-module level(one PR at a time). So to use cmake, the user wold build and install each library individually with cmake. Later, we can update the cmake modules to support superproject building(which may be necessary for libraries that have circular dependencies). Right now, there are no modules for building documentation. This can be added later, as well. So does anyone have any feedback on this setup? If you had ideas, or would like to help update boost libraries, contributions are welcome. Thanks, Paul

6 13

Testing issues
by Belcourt, Kenneth 19 Jan '17

19 Jan '17

Hi, Tests seem to have stopped cycling, and I see this error in the nightly testing output: error: Cannot create link ../../../boost_root/boost/process.hpp to ../../../boost_root/libs/process/include/boost/process.hpp. error: Link previously defined to another file, ../../../boost_root/libs/proccess/include/boost/process.hpp. # Searching for "process_jam_log" in "/scratch/kbelco/boost_testing/boost_regression/stage/bin"... Traceback (most recent call last): File "run.py", line 71, in <module> runner(root) File "/scratch/kbelco/boost_testing/boost_regression_src/regression.py", line 287, in __init__ self.main() File "/scratch/kbelco/boost_testing/boost_regression_src/regression.py", line 624, in main getattr(self,action_m)() File "/scratch/kbelco/boost_testing/boost_regression_src/regression.py", line 581, in command_regression self.command_setup() File "/scratch/kbelco/boost_testing/boost_regression_src/regression.py", line 352, in command_setup self.build_if_needed(self.process_jam_log,self.pjl_toolset) File "/scratch/kbelco/boost_testing/boost_regression_src/regression.py", line 715, in build_if_needed tool[ 'build_path' ] = self.tool_path( tool ) File "/scratch/kbelco/boost_testing/boost_regression_src/regression.py", line 740, in tool_path , '\n'.join( [ name_or_spec[ 'path' ], build_dir ] ) Exception: Cannot find "process_jam_log" in any of the following locations: Does this problem look familiar to anyone? —- Noel

3 3

[asio] doc format changed?
by Vinnie Falco 19 Jan '17

19 Jan '17

Why did the formatting for Boost.Asio documentation change from 1.61 to 1.63? Compare: http://www.boost.org/doc/libs/1_61_0/doc/html/boost_asio.html http://www.boost.org/doc/libs/1_63_0/doc/html/boost_asio.html This looks like it was unintended, and its screwing up search engines (try searching for "Boost Asio 1.63.0 Reference" -- Follow me on Github: https://github.com/vinniefalco

4 9