[release] Boost 1.63.0 Beta 1
The first beta packages for 1.63.0 beta 1 are now available: https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/ The SHA256 checksums are as follows: 3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. Thanks! -- The release managers
On Mon, Nov 21, 2016 at 5:02 AM, Marshall Clow
The first beta packages for 1.63.0 beta 1 are now available:
Hi Marshall, Has support for VS2017RC still not been merged into b2? IIRC this part was ready even before 1.62. C:\VC\boost>bootstrap.bat Building Boost.Build engine 'cl' is not recognized as an internal or external command, operable program or batch file. Failed to build Boost.Build engine. Please consult bootstrap.log for further diagnostics. You can try to obtain a prebuilt binary from http://sf.net/project/showfiles.php?group_id=7586&package_id=72941 Also, you can file an issue at http://svn.boost.org Please attach bootstrap.log in that case. C:\VC\boost> -- Olaf
On Mon, Nov 21, 2016 at 8:29 AM, Olaf van der Spek
On Mon, Nov 21, 2016 at 5:02 AM, Marshall Clow
wrote: The first beta packages for 1.63.0 beta 1 are now available:
Hi Marshall,
Has support for VS2017RC still not been merged into b2? IIRC this part was ready even before 1.62.
C:\VC\boost>bootstrap.bat Building Boost.Build engine 'cl' is not recognized as an internal or external command, operable program or batch file.
Failed to build Boost.Build engine. Please consult bootstrap.log for further diagnostics.
You can try to obtain a prebuilt binary from
http://sf.net/project/showfiles.php?group_id=7586&package_id=72941
Also, you can file an issue at http://svn.boost.org Please attach bootstrap.log in that case.
C:\VC\boost>
With cl in the path: C:\VC\boost>bootstrap.bat Building Boost.Build engine Bootstrapping is done. To build, run: .\b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: .\b2 --help - Getting started guide: http://boost.org/more/getting_started/windows.html - Boost.Build documentation: http://www.boost.org/build/doc/html/index.html C:\VC\boost>b2 C:/VC/boost/tools/build/src/tools\msvc.jam:834: in generate-setup-cmd *** argument error * rule maybe-rewrite-setup ( toolset : setup-script : setup-options : version : rewrite-setup ? ) * called with: ( msvc : : : default : ) * missing argument setup-script C:/VC/boost/tools/build/src/tools\msvc.jam:746:see definition of rule 'maybe-rew rite-setup' being called C:/VC/boost/tools/build/src/tools\msvc.jam:1076: in configure-really C:/VC/boost/tools/build/src/tools\msvc.jam:201: in configure C:/VC/boost/tools/build/src/tools\msvc.jam:153: in msvc.init C:/VC/boost/tools/build/src/build\toolset.jam:43: in toolset.using C:/VC/boost/tools/build/src/build\project.jam:1052: in using project-config.jam:3: in modules.load C:/VC/boost/tools/build/src\build-system.jam:249: in load-config C:/VC/boost/tools/build/src\build-system.jam:412: in load-configuration-files C:/VC/boost/tools/build/src\build-system.jam:524: in load C:\VC\boost\tools\build\src/kernel\modules.jam:295: in import C:\VC\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build C:\VC\boost\boost-build.jam:17: in module scope C:\VC\boost> -- Olaf
Hi Olaf Am Montag, 21. November 2016, 08:38:31 CET schrieb Olaf van der Spek:
On Mon, Nov 21, 2016 at 8:29 AM, Olaf van der Spek
wrote: Has support for VS2017RC still not been merged into b2? IIRC this part was ready even before 1.62.
Yes, until MS changed the install path's of Visual Studio with Preview 5. And again with the RC. So we need to adopt Boost.Build again in the hope the current directory layout is kept for the final.
With cl in the path:
C:/VC/boost/tools/build/src/tools\msvc.jam:834: in generate-setup-cmd *** argument error * rule maybe-rewrite-setup ( toolset : setup-script : setup-options : version : rewrite-setup ? ) * called with: ( msvc : : : default : )
The internal detection logic is broken. I've taken a cursory look at it, but found no quick solution. Patches welcome. An unreleased compiler still is no release blocker. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany
On Mon, Nov 21, 2016 at 10:50 AM, Jürgen Hunold
Hi Olaf
Am Montag, 21. November 2016, 08:38:31 CET schrieb Olaf van der Spek:
On Mon, Nov 21, 2016 at 8:29 AM, Olaf van der Spek
wrote: Has support for VS2017RC still not been merged into b2? IIRC this part was ready even before 1.62.
Yes, until MS changed the install path's of Visual Studio with Preview 5. And again with the RC. So we need to adopt Boost.Build again in the hope the current directory layout is kept for the final.
The path issue is a minor issue.
With cl in the path:
C:/VC/boost/tools/build/src/tools\msvc.jam:834: in generate-setup-cmd *** argument error * rule maybe-rewrite-setup ( toolset : setup-script : setup-options : version : rewrite-setup ? ) * called with: ( msvc : : : default : )
The internal detection logic is broken. I've taken a cursory look at it, but found no quick solution. Patches welcome.
I think 1.62 used to be buildable with the preview.. Who's the resident Boost Build expert? IMO it'd be very nice to have VS2017 working. -- Olaf
Olaf van der Spek-3 wrote
I think 1.62 used to be buildable with the preview.. Who's the resident Boost Build expert? IMO it'd be very nice to have VS2017 working.
1.62 was buildable with VS15 installed because it used VS14 by default. Maybe this commit [1] could just be reverted for now so that the default build works again when VS15 is installed, suing VS14 as before? Building Boost with VS14 and using it from a VS15 project works fine. [1] https://github.com/boostorg/build/commit/ae5e63a1315493dfb2fc60c4d537674fa63... -- View this message in context: http://boost.2283326.n4.nabble.com/release-Boost-1-63-0-Beta-1-tp4690032p469... Sent from the Boost - Dev mailing list archive at Nabble.com.
Hi Olaf, Am Montag, 21. November 2016, 13:19:57 CET schrieb Olaf van der Spek:
On Mon, Nov 21, 2016 at 10:50 AM, Jürgen Hunold
wrote: Yes, until MS changed the install path's of Visual Studio with Preview 5. And again with the RC. So we need to adopt Boost.Build again in the hope the current directory layout is kept for the final.
The path issue is a minor issue.
"path" includes registry entries. And both are evaluated. And yes, that is a major issue, as you see below.
I think 1.62 used to be buildable with the preview..
That is what I said. I think I merged the relevant PR and to master. Thus Preview 4 works, Preview 5 changed paths and registry entries, RC again.
Who's the resident Boost Build expert? IMO it'd be very nice to have VS2017 working.
Too late for the release, I suspect. And it is still a preview compiler with a lot of issues to be fixed in develop anyway. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany
On Mon, Nov 21, 2016 at 1:49 PM, Jürgen Hunold
Hi Olaf,
Am Montag, 21. November 2016, 13:19:57 CET schrieb Olaf van der Spek:
On Mon, Nov 21, 2016 at 10:50 AM, Jürgen Hunold
wrote: Yes, until MS changed the install path's of Visual Studio with Preview 5. And again with the RC. So we need to adopt Boost.Build again in the hope the current directory layout is kept for the final.
The path issue is a minor issue.
"path" includes registry entries. And both are evaluated. And yes, that is a major issue, as you see below.
I think 1.62 used to be buildable with the preview..
That is what I said. I think I merged the relevant PR and to master. Thus Preview 4 works, Preview 5 changed paths and registry entries, RC again.
So bootstraps can't automatically find cl.. that's minor IMO. But if cl is in the path, there's another issue..
Who's the resident Boost Build expert? IMO it'd be very nice to have VS2017 working.
Too late for the release, I suspect. And it is still a preview compiler with a lot of issues to be fixed in develop anyway.
Sure, but I think VS gets released before Boost 1.64.. -- Olaf
On Mon, Nov 21, 2016 at 9:41 AM, Olaf van der Spek
On Mon, Nov 21, 2016 at 1:49 PM, Jürgen Hunold
wrote: Hi Olaf,
Am Montag, 21. November 2016, 13:19:57 CET schrieb Olaf van der Spek:
On Mon, Nov 21, 2016 at 10:50 AM, Jürgen Hunold
wrote: Yes, until MS changed the install path's of Visual Studio with Preview 5. And again with the RC. So we need to adopt Boost.Build again in the hope the current directory layout is kept for the final.
The path issue is a minor issue.
"path" includes registry entries. And both are evaluated. And yes, that is a major issue, as you see below.
I think 1.62 used to be buildable with the preview..
That is what I said. I think I merged the relevant PR and to master. Thus Preview 4 works, Preview 5 changed paths and registry entries, RC again.
So bootstraps can't automatically find cl.. that's minor IMO.
But if cl is in the path, there's another issue..
Who's the resident Boost Build expert? IMO it'd be very nice to have VS2017 working.
Too late for the release, I suspect. And it is still a preview compiler with a lot of issues to be fixed in develop anyway.
Sure, but I think VS gets released before Boost 1.64.
+1 VS2017 is a major step forward for VC++ users, so the faster Boost Build works OK with it the better. But that said, we need to get on with 1.63. --Beman
On Sun, Nov 20, 2016 at 8:02 PM, Marshall Clow
The first beta packages for 1.63.0 beta 1 are now available:
https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/
The SHA256 checksums are as follows:
3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip
D'oh! I named the files wrong. I have renamed them; they're the content. 3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0_b1.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0_b1.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0_b1.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0_b1.zip
As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Building with Apple's clang and libc++ Apple LLVM version 8.0.0 (clang-800.0.42.1) Target: x86_64-apple-darwin15.6.0 Thread model: posix _LIBCPP_VERSION: 3700 - C++03 - passed - C++11 - failed ./boost/context/detail/apply.hpp:42:23: error: no member named 'invoke' in namespace 'std' -> decltype( std::invoke( std::forward< Fn >( fn), std::get< I >( std::forward< Tpl >( tpl) ) ... ) ) - C++14 - failed ./boost/context/detail/apply.hpp:42:23: error: no member named 'invoke' in namespace 'std' -> decltype( std::invoke( std::forward< Fn >( fn), std::get< I >( std::forward< Tpl >( tpl) ) ... ) ) - C++1z - passed I suspect that something like the following would work in "boost/config/stdlib/libcpp.hpp" #if (_LIBCPP_VERSION < 3700) || (__cplusplus <= 201402L) # define BOOST_NO_CXX17_STD_INVOKE #endif With this change, the C++11 and C++14 builds complete w/o errors. -- Marshall
I was forced to push several bugfixes today - do you plan to create a Beta 2 or will those fixes at least be included in the 1.63 release?
Hi, What is the preferred reporting method ? AFAIK python/numpy lib does not build on my platform: intel-linux.compile.c++ bin.v2/libs/python/build/intel-linux/release/link-static/threading-multi/numpy/dtype.o libs/python/src/numpy/dtype.cpp(61): error: identifier "NPY_FLOAT16" is undefined BUILTIN_FLOAT_DTYPE(16); [alainm@gurney boost_1_63_0]$ icpc -v icpc version 15.0.2 (gcc version 4.4.7 compatibility) [alainm@gurney boost_1_63_0]$ python --version Python 2.6.6 [alainm@gurney boost_1_63_0]$ Thanks Alain On 21/11/2016 05:02, Marshall Clow wrote:
The first beta packages for 1.63.0 beta 1 are now available:
https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/
The SHA256 checksums are as follows:
3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip
As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Thanks!
-- The release managers
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Alain Miniussi Pole Génie Logiciel Scientifique Observatoire de la Côte d'Azur Blv de l'Observatoire, Nice
And boost MPI test is failing:
boost::mpi::packed_iarchive&, std::vector
The first beta packages for 1.63.0 beta 1 are now available:
https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/
The SHA256 checksums are as follows:
3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip
As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Thanks!
-- The release managers
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Alain Miniussi Pole Génie Logiciel Scientifique Observatoire de la Côte d'Azur Blv de l'Observatoire, Nice
On 11/21/16 07:02, Marshall Clow wrote:
The first beta packages for 1.63.0 beta 1 are now available:
https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/
The SHA256 checksums are as follows:
3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip
As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Is master now open for bugfixes?
Looks good on windows.
toolset arch compile Link Execute
msvc-8.0 32 X X X
msvc-8.0 64 X X X
msvc-9.0 32 X X X
msvc-9.0 64 X X X
msvc-10.0 32 X X X
msvc-10.0 64 X X X
msvc-11.0 32 X X X
msvc-11.0 64 X X X
msvc-12.0 32 X X X
msvc-12.0 64 X X X
msvc-14.0 32 X X X
msvc-14.0 64 X X X
Compile means that the b2 command completed without errors
Install means that the installers for the respective version were generated
Link means that visual studio was able to link a sample executable to a
library (libboost_thread-vcXXX-
mt[-gd]-1_XX.lib) generated
Execute means that the linked program executed without errors.
The full build logs can be found at:
https://gist.github.com/teeks99/5f550fd6c2d86f14a59d24d7d79f252d
Tom
On Sun, Nov 20, 2016 at 10:02 PM, Marshall Clow
The first beta packages for 1.63.0 beta 1 are now available:
https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/
The SHA256 checksums are as follows:
3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip
As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Thanks!
-- The release managers
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/ mailman/listinfo.cgi/boost
Marshall Clow-2 wrote
As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Seems to work fine with Visual Studio 2013 and 2015, 32 and 64 bit. I compiled all libraries and some actual projects using Boost. Marcel -- View this message in context: http://boost.2283326.n4.nabble.com/release-Boost-1-63-0-Beta-1-tp4690032p469... Sent from the Boost - Dev mailing list archive at Nabble.com.
Hi,
The first beta packages for 1.63.0 beta 1 are now available:
The Boost Build shipped with the beta fails to build on VC11 (Visual Studio 2012). It seems to be problem with the newly introduced PROFILE_* macros (build-log at [1]). Using the Boost Build binary of 1.62 fails too, because of python-numpy. Overwriting the "src/engine/function.c" with the one from 1.62 (without these macros) works (and then leads to a successful build of Boost too). Regards, Stefan [1] https://gist.github.com/anonymous/9f4b06cf0f0ce273f17a893e55f47fa5
On Mon, Nov 28, 2016 at 11:28 AM, Stefan Floeren
Hi,
The first beta packages for 1.63.0 beta 1 are now available:
The Boost Build shipped with the beta fails to build on VC11 (Visual Studio 2012).
It seems to be problem with the newly introduced PROFILE_* macros (build-log at [1]).
Using the Boost Build binary of 1.62 fails too, because of python-numpy.
Overwriting the "src/engine/function.c" with the one from 1.62 (without these macros) works (and then leads to a successful build of Boost too).
Regards, Stefan
[1] https://gist.github.com/anonymous/9f4b06cf0f0ce273f17a893e55f47fa5
Thanks for finding that.. Could you try applying this change locally to see if it fixes it (and doesn't break others)? https://github.com/boostorg/build/pull/150 -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
Hi,
Thanks for finding that.. Could you try applying this change locally to see if it fixes it (and doesn't break others)?
It fixes the warning regarding redefinition, but the build fails nonetheless. Actually it's very strange: Have a look at function_run (line 3772): the build fails, if there is anything (except white space) between the { after the if (#3785) and BUILTIN_FUNCTION. As the macro expands to nothing, only the semicolon remains and the build fails. Replacing the macro with a singular semicolon has the same effect ([1] for preprocessor results). I have no idea what's the actual cause for this... Regards, Stefan [1] Preprocessed file: https://gist.github.com/anonymous/634f8ab803c9318dbfd036bf8d1a9293 Line 335727
On Tue, Nov 29, 2016 at 2:53 AM, Stefan Floeren
Hi,
Thanks for finding that.. Could you try applying this change locally to see if it fixes it (and doesn't break others)?
It fixes the warning regarding redefinition, but the build fails nonetheless.
Actually it's very strange: Have a look at function_run (line 3772): the build fails, if there is anything (except white space) between the { after the if (#3785) and BUILTIN_FUNCTION. As the macro expands to nothing, only the semicolon remains and the build fails. Replacing the macro with a singular semicolon has the same effect ([1] for preprocessor results).
I have no idea what's the actual cause for this...
I can see one possibility for the error.. I've made one more tweak to the above change. Can you try again? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
participants (12)
-
alainm
-
Andrey Semashev
-
Beman Dawes
-
Daniel James
-
Jürgen Hunold
-
Marcel Raad
-
Marshall Clow
-
Olaf van der Spek
-
Oliver Kowalke
-
Rene Rivera
-
Stefan Floeren
-
Tom Kent