- Boost - lists.preview.boost.org

Test results marked as failure without errors
by Abel Sinkovics 28 Feb '16

28 Feb '16

Hi, Some of the Metaparse tests are marked as failures, however I see no errors in the output. Here are two examples (one for gcc and one for msvc) http://www.boost.org/development/tests/develop/developer/output/igaztanaga-… http://www.boost.org/development/tests/develop/developer/output/igaztanaga-… Both the compile and link steps succeed and there is nothing about the execution of the compiled code. Does someone know why these are marked as failures? Thanks, Ábel

4 5

[Container] Inner Smart Pointers
by Phil Bouchard 28 Feb '16

28 Feb '16

I have to admit MSVC 2015 got a clean STL... block_ptr_test2.cpp doesn't crash but some assertions are wrong (in my block_ptr tests). Is there any plans from Boost to make the Boost.Container work with inner smart pointers? I don't think there is any other alternative if people want to plugin memory management. Thanks, -Phil

4 16

Re: [boost] [Boost-users] [Fit] upcoming formal review for Boost.Fit
by Vicente J. Botet Escriba 27 Feb '16

27 Feb '16

Le 27/02/2016 20:18, Edward Diener a écrit : > On 2/27/2016 11:16 AM, Vicente J. Botet Escriba wrote: >> Dear Boost community, >> >> The formal review of Paul Fultz II's Fit library starts on Wednesday, >> 2nd March and ends on 13th March. > > What is the branch of Fit we are going to be reviewing ? The boost branch. The link https://github.com/pfultz2/Fit/tree/boost points directly to the repository that will be reviewed. Vicente

1 0

Maintainer of bimap
by Sebastien Loriot 27 Feb '16

27 Feb '16

Hi, Is there still somebody in charge of the bimap package? There are 2 trivial pull requests lying around since last summer. It would be nice to see them integrated. Thanks, Sebastien.

2 1

[config] config.requires and simple_run
by Steven Watanabe 27 Feb '16

27 Feb '16

AMDG I've just been trying to get MinGW working without requiring the compiler's bin directory to be in the PATH. It mostly works now, but unfortunately I ran into problems with simple_run_action. The problem essentially is that this rule ignores RUN_PATH, which may be set by some toolsets (a quick grep shows borland, cw, gcc, and intel) to indicate additional paths that must be added to PATH when running the executable. In addition, I'm wondering how this is supposed to work with a cross-compiler. We really shouldn't be requiring cross-compilers to have access to the target system for ordinary builds. In Christ, Steven Watanabe

2 4

Can't build in status?
by John Maddock 27 Feb '16

27 Feb '16

I can't seem to get building anything in the status directory working, I'm using: bjam --dump-tests msvc-14.0 -n But any combination of arguments seems to fail, the failures are: M:/data/boost/boost/tools/build/src/build\property.jam:743: in class(a)property-map.find from module object(property-map)@236 error: Ambiguous key M:/data/boost/boost/tools/build/src/build\type.jam:333: in generated-target-ps from module type M:/data/boost/boost/tools/build/src/build\type.jam:270: in type.generated-target-suffix from module type M:/data/boost/boost/tools/build/src/build\virtual-target.jam:509: in virtual-target.add-prefix-and-suffix from module virtual-target M:/data/boost/boost/tools/build/src/build\virtual-target.jam:468: in _adjust-name from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/build\virtual-target.jam:253: in abstract-file-target.__init__ from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/build\virtual-target.jam:561: in class(a)file-target.__init__ from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/kernel\class.jam:90: in class.new from module class M:/data/boost/boost/tools/build/src/build\generators.jam:558: in generator.generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\builtin.jam:886: in linking-generator.generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\unix.jam:67: in generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:459: in construct-result from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:412: in run-really from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:386: in generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\builtin.jam:801: in linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\unix.jam:41: in unix-linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\gcc.jam:692: in class(a)gcc-linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in generators.construct from module generators M:/data/boost/boost/tools/build/src/tools\python.jam:1160: in class(a)python-test-generator.run from module object(python-test-generator)@244 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in construct from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1069: in generators.construct-types from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:609: in convert-to-consumable-types from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:405: in run-really from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:386: in class(a)generator.run from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in generators.construct from module generators M:/data/boost/boost/tools/build/src/build\targets.jam:1553: in construct from module object(typed-target)@19839 M:/data/boost/boost/tools/build/src/build\targets.jam:1353: in class(a)basic-target.generate from module object(typed-target)@19839 M:/data/boost/boost/tools/build/src/build\targets.jam:774: in generate-really from module object(main-target)@148055 M:/data/boost/boost/tools/build/src/build\targets.jam:746: in class(a)main-target.generate from module object(main-target)@148055 M:/data/boost/boost/tools/build/src/build\targets.jam:895: in targets.generate-from-reference from module targets M:/data/boost/boost/tools/build/src/build\targets.jam:1266: in generate-dependencies from module object(alias-target-class)@19840 M:/data/boost/boost/tools/build/src/build\targets.jam:1323: in class(a)basic-target.generate from module object(alias-target-class)@19840 M:/data/boost/boost/tools/build/src/build\targets.jam:774: in generate-really from module object(main-target)@148056 M:/data/boost/boost/tools/build/src/build\targets.jam:746: in class(a)main-target.generate from module object(main-target)@148056 M:/data/boost/boost/tools/build/src/build\targets.jam:272: in class(a)project-target.generate from module object(project-target)@19754 M:/data/boost/boost/tools/build/src/build\targets.jam:272: in class(a)project-target.generate from module object(project-target)@2060 M:/data/boost/boost/tools/build/src\build-system.jam:710: in load from module build-system M:\data\boost\boost\tools\build\src/kernel\modules.jam:295: in import from module modules M:\data\boost\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build from module M:\data\boost\boost\boost-build.jam:17: in module scope from module Anyone any ideas? Thanks, John.

2 11

[Experimental Boost.DI] [v1.0.0 released] [Looking for a Review Manager] Your C+14 Dependency Injection library with no overhead and compile time creation guarantee!
by Krzysztof Jusiak 27 Feb '16

27 Feb '16

Dear Boosters, I have just released version 1.0.0 of experimental Boost.DI library. Your C++14 header only Dependency Injection library with no dependencies. Library entered Boost Formal Review Queue some time ago and right now, IMHO, is ready to be reviewed. http://www.boost.org/community/review_schedule.html Therefore, I'm looking for a Review Manager, so if you think that Boost.DI is good enough to be reviewed and you would like to help with it, please let me know. Thank you! In the mean time check out the library yourself online! http://boost-experimental.github.io/di/examples/index.html Or read the interactive documentation... http://boost-experimental.github.io/di Or check out the source code... https://github.com/boost-experimental/di Why Boost.DI? * Boost.DI has none or minimal run-time overhead * Boost.DI compiles fast / Faster than Java-Dagger2! * Boost.DI gives short diagnostic messages * Boost.DI is non-intrusive * Boost.DI reduces boilerplate code * Boost.DI reduces testing effort * Boost.DI gives better control of what and how is created * Boost.DI gives better understanding about objects hierarchy Read more why here -> http://boost-experimental.github.io/di/index.html Any feedback is more than welcome! Cheers, Kris

9 34

GSOC-2016
by Abhimanyu Shekhawat 27 Feb '16

27 Feb '16

Hi there ! I am Abhimanyu Shekhawat, a sophomore perusing B.E(Hons)Computer Science, Birla Institute of Technology & Science, Pilani - Goa,India. I would like to take part in GSOC Programme 2016 with Boost Community. Actually I am very excited about contributing to open source projects and I already have experiences with some of the college based projects till now.I feel that being able to work in open source community will not only expose me to new learning avenues but will also give me a chance to contribute to the a much larger community. As far as my background is concerned,I have taken a course on Discreet Mathematics and currently perusing a rigorous Algorithm and Data structure course. Also I have got an intermediate level of skill set in C++,C,Java,Android and Mysql while a basic understanding of python. I hope that my skills and enthusiasm will prove an asset to the community.So I will be grateful if you can get me started Thank you :D

3 2

[hana] missing .gitattributes
by Steven Watanabe 26 Feb '16

26 Feb '16

AMDG I just noticed that all the files for hana had \n line endings in my working copy. To fix this I had to copy .gitattributes from the superproject. (Or am I just using git wrong) In Christ, Steven Watanabe

3 5

[log][thread][teeks][igaztanaga] Log & Thread tests failing on MSVC & MinGW
by Andrey Semashev 26 Feb '16

26 Feb '16

Hi, I can see lots of Boost.Log tests are failing on igaztanaga and teeks99-08 testers [1], while the error logs are non-descriptive (show a successful compilation). For some tests the links in the table refer to successful compilation of Boost.Thread, which I can see is failing on the same testers the same way [2]. What's interesting, teeks99-09 testers are green for both libraries. Is there a known problem with Boost.Thread on Windows? Or with these particular testers? If not, is it possible to see the actual failure logs? PS: Disregard the MSVC-7.1 and gcc 3.4 columns. These old compilers I don't expect to work. [1] http://www.boost.org/development/tests/develop/developer/log.html [2] http://www.boost.org/development/tests/develop/developer/thread.html

1 0