[release] 1.67.0 mostly closed for release candidate - Boost - lists.stage.boost.cppalliance.org

newer
Reducing dependencies

[release] 1.67.0 mostly closed for release candidate

older
mkmakefile

Daniel James

4 Apr 2018 4 Apr '18

10:11 p.m.

The master branch is now closed for all changes except by permission for the release candidate. We're expecting potential fixes for build, context and a documentation update for ptr_container. Please let us know if there are any other fixes that you want to include in the release. Thanks, -- The Boost Release Team

Reply

Sign in to reply online Use email software

Show replies by date

jblaszcz

5 Apr 5 Apr

6:48 a.m.

Maybe it's too late for the fix but building of Boost 1.67.0 Beta 1 with Visual Studio 2017 15.6.4 and Intel Compiler 18.0.2 doesn't work properly: C:\nask\boost_1_67_0_b1_rc2.comp>b2 address-model=64 architecture=x86 --build-dir=C:\windir\boost167intel.comp --stagedir=C:\windir\boost167intel.comp --build-type=complete --with-iostreams -s BZIP2_SOURCE=C:\nask\bzip2-1.0.6 -s ZLIB_SOURCE=C:\nask\zlib-1.2.8 variant=release link=shared link=static threading=multi runtime-link=shared runtime-link=static --toolset=intel-18.0-vc14.1 cflags="/QaxCORE-AVX512,CORE-AVX2,AVX,SSE4.2,SSE4.1 /Qfma -O3 /Qip /Qopt-zmm-usage=high /fp:precise /fp:source /Qimf-arch-consistency:true /Qpc80 -wd10120" cxxflags="/QaxCORE-AVX512,CORE-AVX2,AVX,SSE4.2,SSE4.1 /Qfma -O3 /Qip /Qopt-zmm-usage=high /fp:precise /fp:source /Qimf-arch-consistency:true /Qpc80 /Qstd=c++14 -wd10120" -j4 --hash C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel-win.jam:237: in configure-really ERROR: rule "msvc.maybe-rewrite-setup" unknown in module "intel-win". C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel-win.jam:99: in configure C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel-win.jam:46: in intel-win.init C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/build\toolset.jam:44: in toolset.using C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel.jam:32: in intel.init C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/build\toolset.jam:44: in toolset.using C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src\build-system.jam:543: in process-explicit-toolset-requests C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src\build-system.jam:610: in load C:\nask\boost_1_67_0_b1_rc2.comp\tools\build\src/kernel\modules.jam:295: in import C:\nask\boost_1_67_0_b1_rc2.comp\tools\build\src/kernel/bootstrap.jam:139: in boost-build C:\nask\boost_1_67_0_b1_rc2.comp\boost-build.jam:17: in module scope It seems that /intel-win.jam/ file is outdated in Boost 1.67.0 Beta 1 since the /maybe-rewrite-setup/ rule has been removed from the /msvc.jam/ file. Best Regards, Jacek -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

Reply

Sign in to reply online Use email software

Robert

6 Apr 6 Apr

1:44 p.m.

New subject: [SPAM] Re: [release] 1.67.0 mostly closed for release candidate

On 4/5/2018 1:48 AM, jblaszcz via Boost wrote:

Maybe it's too late for the fix but building of Boost 1.67.0 Beta 1 with Visual Studio 2017 15.6.4 and Intel Compiler 18.0.2 doesn't work properly:

I have never tried building Boost with Intel within Visual Studio. I instead configure the matching architecture command prompt. I use the Intel web page, "Building Boost with Intel C++ Compiler 16.0," as a guide (e.g. https://software.intel.com/en-us/articles/building-boost-with-intel-c-compil...). I also update the intel-win.jam file to reflect the new Visual Studio version number and/or Intel version number. For example, when the Intel 19.0 beta is released, I first have to review and modify intel-win.jam, and then build all Boost. During the process, I manually edit the user-config.jam to correctly build with the matching Python architecture. In the past, I have never been successful configuring zlib through user-config.jam. That may be resolved now. I am going to test zlib via user-config.jam with 1.67. --Robert

C:\nask\boost_1_67_0_b1_rc2.comp>b2 address-model=64 architecture=x86 --build-dir=C:\windir\boost167intel.comp --stagedir=C:\windir\boost167intel.comp --build-type=complete --with-iostreams -s BZIP2_SOURCE=C:\nask\bzip2-1.0.6 -s ZLIB_SOURCE=C:\nask\zlib-1.2.8 variant=release link=shared link=static threading=multi runtime-link=shared runtime-link=static --toolset=intel-18.0-vc14.1 cflags="/QaxCORE-AVX512,CORE-AVX2,AVX,SSE4.2,SSE4.1 /Qfma -O3 /Qip /Qopt-zmm-usage=high /fp:precise /fp:source /Qimf-arch-consistency:true /Qpc80 -wd10120" cxxflags="/QaxCORE-AVX512,CORE-AVX2,AVX,SSE4.2,SSE4.1 /Qfma -O3 /Qip /Qopt-zmm-usage=high /fp:precise /fp:source /Qimf-arch-consistency:true /Qpc80 /Qstd=c++14 -wd10120" -j4 --hash C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel-win.jam:237: in configure-really ERROR: rule "msvc.maybe-rewrite-setup" unknown in module "intel-win". C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel-win.jam:99: in configure C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel-win.jam:46: in intel-win.init C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/build\toolset.jam:44: in toolset.using C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/tools\intel.jam:32: in intel.init C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src/build\toolset.jam:44: in toolset.using C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src\build-system.jam:543: in process-explicit-toolset-requests C:/nask/boost_1_67_0_b1_rc2.comp/tools/build/src\build-system.jam:610: in load C:\nask\boost_1_67_0_b1_rc2.comp\tools\build\src/kernel\modules.jam:295: in import C:\nask\boost_1_67_0_b1_rc2.comp\tools\build\src/kernel/bootstrap.jam:139: in boost-build C:\nask\boost_1_67_0_b1_rc2.comp\boost-build.jam:17: in module scope

It seems that /intel-win.jam/ file is outdated in Boost 1.67.0 Beta 1 since the /maybe-rewrite-setup/ rule has been removed from the /msvc.jam/ file.

Best Regards, Jacek

-- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply

Sign in to reply online Use email software

jblaszcz

8:19 p.m.

New subject: [SPAM] Re: [release] 1.67.0 mostly closed for release candidate

I forgot to mention that I am using the following patch for the intel-win.jam file: diff -Nru boost_1_67_0_b1_rc1.orig/tools/build/src/tools/intel-win.jam boost_1_67_0_b1_rc1/tools/build/src/tools/intel-win.jam --- boost_1_67_0_b1_rc1.orig/tools/build/src/tools/intel-win.jam 2018-03-08 14:07:09.000000000 +0100 +++ boost_1_67_0_b1_rc1/tools/build/src/tools/intel-win.jam 2018-03-12 14:46:07.484225270 +0100 @@ -468,14 +468,14 @@ <architecture>/<address-model>64 <architecture>x86/<address-model>64 ; -.intel-autodetect-versions = 14.0 13.0 12.0 ; +.intel-autodetect-versions = 14.1 14.0 13.0 12.0 ; .iclvars-12.0-supported-vcs = "10.0 9.0 8.0" ; .iclvars-12.1-supported-vcs = "10.0 9.0 8.0" ; .iclvars-13.0-supported-vcs = "11.0 10.0 9.0" ; .iclvars-14.0-supported-vcs = "12.0 11.0 10.0 9.0" ; .iclvars-15.0-supported-vcs = "12.0 11.0 10.0 9.0" ; .iclvars-16.0-supported-vcs = "14.0 12.0 11.0 10.0 9.0" ; -.iclvars-17.0-supported-vcs = "14.0 12.0 11.0 10.0" ; +.iclvars-17.0-supported-vcs = "14.1 14.0 12.0 11.0 10.0" ; .iclvars-18.0-supported-vcs = "14.1 14.0 12.0 11.0 10.0" ; .iclvars-version-alias-vc14.1 = vs2017 ; .iclvars-version-alias-vc14 = vs2015 ; My approach has been working well for all Boost 1.6x versions except the recent one (1.67 Beta) - probably because of the latest changes in the msvc.jam file. Before b2, I am executing bootstrap.bat command in the root Boost folder. -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

Reply

Sign in to reply online Use email software

Daniel James

7 Apr 7 Apr

9:51 a.m.

On 5 April 2018 at 07:48, jblaszcz via Boost wrote:

Maybe it's too late for the fix but building of Boost 1.67.0 Beta 1 with Visual Studio 2017 15.6.4 and Intel Compiler 18.0.2 doesn't work properly:

Unless the build people deal with it quickly, it's probably too late, but I created a ticket: https://github.com/boostorg/build/issues/296

Reply

Sign in to reply online Use email software

Steven Watanabe

3:18 p.m.

AMDG On 04/07/2018 03:51 AM, Daniel James via Boost wrote:

On 5 April 2018 at 07:48, jblaszcz via Boost wrote:

...
Maybe it's too late for the fix but building of Boost 1.67.0 Beta 1 with Visual Studio 2017 15.6.4 and Intel Compiler 18.0.2 doesn't work properly:

Unless the build people deal with it quickly, it's probably too late, but I created a ticket:

https://github.com/boostorg/build/issues/296

I have something to do this morning, so I won't get to it for a couple of hours. I'll fix it no later than 4 hours from now (1:30 PM UTC-0700) In Christ, Steven Watanabe

Reply

Sign in to reply online Use email software

Daniel James

3:28 p.m.

On 7 April 2018 at 16:18, Steven Watanabe via Boost wrote:

AMDG

On 04/07/2018 03:51 AM, Daniel James via Boost wrote:

...
On 5 April 2018 at 07:48, jblaszcz via Boost wrote:

...
Maybe it's too late for the fix but building of Boost 1.67.0 Beta 1 with Visual Studio 2017 15.6.4 and Intel Compiler 18.0.2 doesn't work properly:

Unless the build people deal with it quickly, it's probably too late, but I created a ticket:

https://github.com/boostorg/build/issues/296

I have something to do this morning, so I won't get to it for a couple of hours. I'll fix it no later than 4 hours from now (1:30 PM UTC-0700)

That's very quick. Thank you Steven.

Reply

Sign in to reply online Use email software

Ion Gaztañaga

6 Apr 6 Apr

8:10 p.m.

On 05/04/2018 0:11, Daniel James via Boost wrote:

The master branch is now closed for all changes except by permission for the release candidate. We're expecting potential fixes for build, context and a documentation update for ptr_container. Please let us know if there are any other fixes that you want to include in the release.

I have a nasty memory leak just fixed and just cycled in develop. If there is an opportunity, I'd like to merge it: https://github.com/boostorg/container/commit/b3eee90a81ce935918ae1c3c764ae16... Ion

Reply

Sign in to reply online Use email software

Daniel James

7 Apr 7 Apr

8:44 a.m.

On 6 April 2018 at 21:10, Ion Gaztañaga via Boost wrote:

On 05/04/2018 0:11, Daniel James via Boost wrote:

...
The master branch is now closed for all changes except by permission for the release candidate. We're expecting potential fixes for build, context and a documentation update for ptr_container. Please let us know if there are any other fixes that you want to include in the release.

I have a nasty memory leak just fixed and just cycled in develop. If there is an opportunity, I'd like to merge it:

https://github.com/boostorg/container/commit/b3eee90a81ce935918ae1c3c764ae16...

Yes, that's okay to merge today. Thanks.

Reply

Sign in to reply online Use email software

Ion Gaztañaga

1:52 p.m.

On 07/04/2018 10:44, Daniel James via Boost wrote:

...
I have a nasty memory leak just fixed and just cycled in develop. If there is an opportunity, I'd like to merge it:

https://github.com/boostorg/container/commit/b3eee90a81ce935918ae1c3c764ae16...

Yes, that's okay to merge today. Thanks.

Done. Thanks! Ion

Reply

Sign in to reply online Use email software

2425

Age (days ago)

2428

Last active (days ago)

Download

9 comments

5 participants

tags

participants (5)

Daniel James
Ion Gaztañaga
jblaszcz
Robert
Steven Watanabe