[release] 1.64.0 closed for Beta
The master branch is now closed for all changes except by permission for the Beta release. Also, remember to add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_64_0.qb...
Thanks, -- The Boost Release Team -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Thu, Mar 9, 2017 at 4:25 AM, Rene Rivera via Boost <boost@lists.boost.org
wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Now VS2017 *is* officially released. Is 1.64.0 going to ship w/o built-in support for it? (given the other recent thread) Thanks, --DD
On Thu, Mar 9, 2017 at 2:48 AM, Dominique Devienne via Boost < boost@lists.boost.org> wrote:
On Thu, Mar 9, 2017 at 4:25 AM, Rene Rivera via Boost < boost@lists.boost.org
wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Now VS2017 *is* officially released.
Is 1.64.0 going to ship w/o built-in support for it? (given the other recent thread)
It's not out of the question yet to support it on this release. After the beta there will be some time to push fixes. And I'm working to verify the build support. Which is slowed at the moment from having to install VS through slow hotel wifi. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: < https://dl.bintray.com/boostorg/master/>. Note that the Bintray packages also have signature files (*.asc) which can be checked with the general Bintray key at < https://bintray.com/user/downloadSubjectPublicKey?username=bintray>. And there are also sha256 hashes for the archives in machine readable JSON files. -- The Boost Release Team -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
2017-03-09 20:57 GMT+01:00 Rene Rivera via Boost <boost@lists.boost.org>:
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
boost.fiber requires a fix for the unit-tests (Windows) - do I get permission to merge the fix to master
On Fri, Mar 10, 2017 at 6:54 AM, Oliver Kowalke via Boost < boost@lists.boost.org> wrote:
2017-03-09 20:57 GMT+01:00 Rene Rivera via Boost <boost@lists.boost.org>:
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
boost.fiber requires a fix for the unit-tests (Windows) - do I get permission to merge the fix to master
Please provide a link to the changes? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Thu, Mar 9, 2017 at 2:57 PM, Rene Rivera via Boost <boost@lists.boost.org
wrote:
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: < https://dl.bintray.com/boostorg/master/>. Note that the Bintray packages also have signature files (*.asc) which can be checked with the general Bintray key at < https://bintray.com/user/downloadSubjectPublicKey?username=bintray>. And there are also sha256 hashes for the archives in machine readable JSON files.
A build using VC++ 14.0 on a Win 10 machine looks good. ...updated 1122 targets... The Boost C++ Libraries were successfully built! --Beman
nul
I just built the current snapshot against visual studio 8.0 through 14.0, 32 and 64 bit. Mostly fine, just one error. The fiber library has a link issue with msvc-14.0 (same error in 32 and 64 bit): ...updating 9 targets... msvc.link.dll bin.v2\libs\fiber\build\msvc-14.0\debug\address-model-64\threading-multi\boost_fiber-vc140-mt-gd-1_64.dll Creating library bin.v2\libs\fiber\build\msvc-14.0\debug\address-model-64\threading-multi\boost_fiber-vc140-mt-gd-1_64.lib and object bin.v2\libs\fiber\build\msvc-14.0\debug\address-model-64\threading-multi\boost_fiber-vc140-mt-gd-1_64.exp scheduler.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl boost::context::continuation::continuation(struct boost::context::detail::transfer_t)" (__imp_??0continuation@context@boost@ @AEAA@Utransfer_t@detail@12@@Z) barrier.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl boost::context::continuation::continuation(struct boost::context::detail::transfer_t)" (__imp_??0continuation@context@boost@ @AEAA@Utransfer_t@detail@12@@Z) <snip> bin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi\boost_fiber-vc140-mt-1_64.dll : fatal error LNK1120: 7 unresolved externals call "C:\Users\tomkent\AppData\Local\Temp\2\b2_msvc_14.0_vcvarsall_amd64.cmd" link /NOLOGO /INCREMENTAL:NO /DLL /MACHINE:X64 /MANIFEST /subsystem:console /out:"bin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi\boost_fiber-vc140-mt-1_64.dll" /IMPLIB:"bin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi\boost_fiber-vc140-mt-1_64.lib" @"bin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi\boost_fiber-vc140-mt-1_64.dll.rsp" if %ERRORLEVEL% NEQ 0 EXIT %ERRORLEVEL% ...failed msvc.link.dll bin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi\boost_fiber-vc140-mt-1_64.dll bin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi\boost_fiber-vc140-mt-1_64.lib... ...removing bin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi\boost_fiber-vc140-mt-1_64.lib ...skipped <plib64-msvc-14.0>boost_fiber-vc140-mt-1_64.dll for lack of <pbin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi>boost_fiber-vc140-mt-1_64.dll... ...skipped <plib64-msvc-14.0>boost_fiber-vc140-mt-1_64.lib for lack of <pbin.v2\libs\fiber\build\msvc-14.0\release\address-model-64\threading-multi>boost_fiber-vc140-mt-1_64.lib... ...skipped <plib64-msvc-14.0>boost_fiber-vc140-mt-gd-1_64.dll for lack of <pbin.v2\libs\fiber\build\msvc-14.0\debug\address-model-64\threading-multi>boost_fiber-vc140-mt-gd-1_64.dll... ...failed updating 5 targets... ...skipped 4 targets... The full build output is at: https://gist.github.com/teeks99/8f97486c88cceb0e34a44a9c97af184b#file-boost_... Tom On Thu, Mar 9, 2017 at 1:57 PM, Rene Rivera via Boost <boost@lists.boost.org
wrote:
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: < https://dl.bintray.com/boostorg/master/>. Note that the Bintray packages also have signature files (*.asc) which can be checked with the general Bintray key at < https://bintray.com/user/downloadSubjectPublicKey?username=bintray>. And there are also sha256 hashes for the archives in machine readable JSON files.
-- The Boost Release Team
-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/ mailman/listinfo.cgi/boost
On Thu, Mar 9, 2017 at 8:57 PM, Rene Rivera via Boost <boost@lists.boost.org> wrote:
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: <
VS2017 / W7
.\bootstrap.bat
<OK>
./b2
...patience... ...found 11087 targets... ...updating 718 targets... compile-c-c++ bin.v2\libs\program_options\build\msvc\release\link-static\threading-multi\cmdline.obj 'cl' is not recognized as an internal or external command, operable program or batch file. -- Olaf
On Sat, Mar 11, 2017 at 4:20 PM, Olaf van der Spek <ml@vdspek.org> wrote:
On Thu, Mar 9, 2017 at 8:57 PM, Rene Rivera via Boost <boost@lists.boost.org> wrote:
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: <
VS2017 / W7
.\bootstrap.bat
<OK>
./b2
...patience... ...found 11087 targets... ...updating 718 targets... compile-c-c++ bin.v2\libs\program_options\build\msvc\release\link-static\threading-multi\cmdline.obj 'cl' is not recognized as an internal or external command, operable program or batch file.
When done via the dev prompt: C:/VC/boost_1_64_0/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_1_64_0/tools/build/src/tools\msvc.jam:746:see definition of rule 'ma ybe-rewrite-setup' being called C:/VC/boost_1_64_0/tools/build/src/tools\msvc.jam:1076: in configure-really C:/VC/boost_1_64_0/tools/build/src/tools\msvc.jam:201: in configure C:/VC/boost_1_64_0/tools/build/src/tools\msvc.jam:153: in msvc.init C:/VC/boost_1_64_0/tools/build/src/build\toolset.jam:43: in toolset.using C:/VC/boost_1_64_0/tools/build/src/build\project.jam:1052: in using project-config.jam:3: in modules.load C:/VC/boost_1_64_0/tools/build/src\build-system.jam:249: in load-config C:/VC/boost_1_64_0/tools/build/src\build-system.jam:412: in load-configuration-f iles C:/VC/boost_1_64_0/tools/build/src\build-system.jam:524: in load C:\VC\boost_1_64_0\tools\build\src/kernel\modules.jam:295: in import C:\VC\boost_1_64_0\tools\build\src/kernel/bootstrap.jam:139: in boost-build C:\VC\boost_1_64_0\boost-build.jam:17: in module scope -- Olaf
in order to fix the link issues in boost.fiber - I need permission to merge to master
Can we see the commit you want to merge? On Sat, Mar 11, 2017 at 10:55 AM, Oliver Kowalke via Boost < boost@lists.boost.org> wrote:
in order to fix the link issues in boost.fiber - I need permission to merge to master
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/ mailman/listinfo.cgi/boost
-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Sat, Mar 11, 2017 at 9:20 AM, Olaf van der Spek <ml@vdspek.org> wrote:
On Thu, Mar 9, 2017 at 8:57 PM, Rene Rivera via Boost <boost@lists.boost.org> wrote:
On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: <
VS2017 / W7
.\bootstrap.bat
<OK>
./b2
...patience... ...found 11087 targets... ...updating 718 targets... compile-c-c++ bin.v2\libs\program_options\build\msvc\release\link- static\threading-multi\cmdline.obj 'cl' is not recognized as an internal or external command, operable program or batch file.
We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
Hi Rene, Am Samstag, 11. März 2017, 17:43:53 CET schrieb Rene Rivera via Boost:
We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017.
If you approve the current patch, I can merge the PR to develop and then master. As far as I can see, the last patch from https://github.com/boostorg/ build/issues/157 ( b2260a9 ) works fine. I've tested it with 2017 Enterprise with both Boost develop branch and my own software. 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 Sun, Mar 12, 2017 at 6:22 AM, Jürgen Hunold via Boost < boost@lists.boost.org> wrote:
Hi Rene,
Am Samstag, 11. März 2017, 17:43:53 CET schrieb Rene Rivera via Boost:
We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017.
If you approve the current patch, I can merge the PR to develop and then master. As far as I can see, the last patch from https://github.com/boostorg/ build/issues/157 ( b2260a9 ) works fine. I've tested it with 2017 Enterprise with both Boost develop branch and my own software.
Why not do the merge to develop right way, then post a mention to this thread so others can start testing on develop. I'd rather wait for Rene to give the OK for the merge to master. I've got a P/R in for boost.config to update the MSVC 2017 version numbers for RTW. Thanks, --Beman
On Sun, Mar 12, 2017 at 5:22 AM, Jürgen Hunold via Boost < boost@lists.boost.org> wrote:
Hi Rene,
Am Samstag, 11. März 2017, 17:43:53 CET schrieb Rene Rivera via Boost:
We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017.
If you approve the current patch, I can merge the PR to develop and then master. As far as I can see, the last patch from https://github.com/boostorg/ build/issues/157 <https://github.com/boostorg/build/issues/157> ( b2260a9 ) works fine. I've tested it with 2017 Enterprise with both Boost develop branch and my own software.
Looks like the patch went in, I just setup a temporary Azure VM running VS2017 to give library developers some feedback before the beta goes out this week. There are two runners: teeks99-07-n (develop) and teeks99-07-o (master). It looks like it is running a run about every 4 hours. I've also added that config to my normal runners, so they will start showing up there soon, but only every few days. Hopefully I'll get a chance to build a snapshot tonight and see how that goes. Is there any schedule for when we will start with RCs for the beta? Tom
On Mon, Mar 13, 2017 at 4:06 PM, Tom Kent <lists@teeks99.com> wrote:
On Sun, Mar 12, 2017 at 5:22 AM, Jürgen Hunold via Boost < boost@lists.boost.org> wrote:
Hi Rene,
Am Samstag, 11. März 2017, 17:43:53 CET schrieb Rene Rivera via Boost:
We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017.
If you approve the current patch, I can merge the PR to develop and then master. As far as I can see, the last patch from https://github.com/boostorg/ build/issues/157 <https://github.com/boostorg/build/issues/157> ( b2260a9 ) works fine. I've tested it with 2017 Enterprise with both Boost develop branch and my own software.
Looks like the patch went in, I just setup a temporary Azure VM running VS2017 to give library developers some feedback before the beta goes out this week. There are two runners: teeks99-07-n (develop) and teeks99-07-o (master). It looks like it is running a run about every 4 hours. I've also added that config to my normal runners, so they will start showing up there soon, but only every few days.
Hopefully I'll get a chance to build a snapshot tonight and see how that goes. Is there any schedule for when we will start with RCs for the beta?
I tried building the latest snapshot from bintray, but it doesn't find any compiler when running `bootstrap.bat`. However running `boootstrap.bat vc14.0` works, so something in bootstrap's lookup logic? Tom
On Tue, Mar 14, 2017 at 6:09 PM, Tom Kent via Boost <boost@lists.boost.org> wrote:
I tried building the latest snapshot from bintray, but it doesn't find any compiler when running `bootstrap.bat`. However running `boootstrap.bat vc14.0` works, so something in bootstrap's lookup logic?
Which VSs did you have installed when you tried that? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
participants (7)
-
Beman Dawes -
Dominique Devienne -
Jürgen Hunold -
Olaf van der Spek -
Oliver Kowalke -
Rene Rivera -
Tom Kent