Re: [boost] [release] 1.64.0 please test master snapshot
On Tue, Mar 21, 2017 at 12:36 PM, Tom Kent
It looks like the boostorg/boost:master commit this snapshot was based off doesn't have the latest boostorg/config:master submodule commit. I think updating this is a manual process at this point in the release cycle? (Thus the autolink file is still looking for vc150).
Grr.. Forgot to do that for config. I did it for build though :-) It's done now.. Just need to wait again for the new archives.
As an aside, I had a difficult time figuring out what the snapshot I downloaded referred to. I was able to use the boost_1_64_0_snapshot.tar.bz2.json file to determine that I had the correct boost_1_64_0_snapshot.tar.bz2, but bintray doesn't make it super clear what git commit this snapshot download refers to.
Would it be possible to add a file to snapshots/releases that contains the git commit hash?
Can't promise I'll do it right this second... But I'll add the commit hash to the json data for the archives. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
OK Lets try this again.. New master snapshots are up. Please check them ASAP and report problems and successes. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Tue, Mar 21, 2017 at 7:23 PM, Rene Rivera via Boost
OK Lets try this again..
New master snapshots are up. Please check them ASAP and report problems and successes.
Hmm Cmd: C:\VC\boost_1_64_0>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. Dev Prompt: Bootstrapping is done. To build, run: ... compile-c-c++ bin.v2\libs\log\build\msvc\release\link-static\threading-multi\attribute_name.obj '"C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/vcvarsall.bat"' is not recognized as an internal or extern al command, operable program or batch file. -- Olaf
Hi, just tested this on develop... Am Dienstag, 21. März 2017, 19:44:25 CET schrieb Olaf van der Spek via Boost:
'"C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/vcvarsall.bat"' is not recognized as an internal or extern al command, operable program or batch file.
The compiler autodetection from a plain cmd shell is broken. That is line 715
of msvc.jam, current
local shell_ret = [ SHELL "$(cl_path) 14.10 -PathToCompiler" ] ;
Manually calling the helper script "cl_path.cmd" results in:
cl_path.cmd 14.10 -PathToCompiler
Join-Path : Das Argument kann nicht an den Parameter "Path" gebunden werden,
da es NULL ist.
...
Full output attached, unfortunately in a German shell.
git bisect on this command gives:
00c23580afdd519fa716ee32d6dba500e6b1e991 is the first bad commit
which is
commit 00c23580afdd519fa716ee32d6dba500e6b1e991
Author: Arkadiy Shapkin
On Tue, Mar 21, 2017 at 2:32 PM, Jürgen Hunold via Boost < boost@lists.boost.org> wrote:
Hi,
just tested this on develop...
Am Dienstag, 21. März 2017, 19:44:25 CET schrieb Olaf van der Spek via Boost:
'"C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/ HostX86/vcvarsall.bat"' is not recognized as an internal or extern al command, operable program or batch file.
The compiler autodetection from a plain cmd shell is broken. That is line 715 of msvc.jam, current local shell_ret = [ SHELL "$(cl_path) 14.10 -PathToCompiler" ] ;
Manually calling the helper script "cl_path.cmd" results in:
cl_path.cmd 14.10 -PathToCompiler Join-Path : Das Argument kann nicht an den Parameter "Path" gebunden werden, da es NULL ist.
Works for me: === C:\DevRoots\Boost\master\tools\build\src\tools\vc141helper>cl_path.cmd 14.10 -PathToCompiler C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x86\cl.exe === Although giving it an "invalid" version confuses it: === C:\DevRoots\Boost\master\tools\build\src\tools\vc141helper>cl_path.cmd 14.1 -PathToCompiler Cannot index into a null array. At C:\DevRoots\Boost\master\tools\build\src\tools\vc141helper\GetCLPath.ps1:30 char:9 + Write-Output $cls[0].FullName + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : NullArray ECHO is off. === Is that what you are doing? -- -- 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 Dienstag, 21. März 2017, 22:37:32 CET schrieb Rene Rivera via Boost:
On Tue, Mar 21, 2017 at 2:32 PM, Jürgen Hunold via Boost <
Manually calling the helper script "cl_path.cmd" results in:
cl_path.cmd 14.10 -PathToCompiler
^^ please note the correct invocation.
Works for me:
=== C:\DevRoots\Boost\master\tools\build\src\tools\vc141helper>cl_path.cmd 14.10 -PathToCompiler
Although giving it an "invalid" version confuses it: [...] Is that what you are doing?
No, I took care to do exactly as msvc.jam does. I've checked my build server at work and the auto-detection fails there as well. I've got failures on Windows 7 64bit Windows Server 2008 R2 Service Pack 1 64 bit Both system running a German windows version with an English language pack only Visual Studio 2017 Enterprise installation. Compiling from a "Visual Studio Command Prompt for VS2017" works because the compiler is already in the PATH. Compiling from a vanilla cmd prompt does not work because the helper script errors out as described earlier. 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
Hi Rene, Am Mittwoch, 22. März 2017, 10:11:28 CET schrieb Jürgen Hunold via Boost:
Windows 7 64bit Windows Server 2008 R2 Service Pack 1 64 bit
After some digging around, I found that the PowerShell Version on the machines is ...\boost\tools\build\src\tools\vc141helper>powershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten. PS ..\boost\tools\build\src\tools\vc141helper> $Host.Version Major Minor Build Revision ----- ----- ----- -------- 2 0 -1 -1 whereas the $PSScriptRoot Variable used in GetCLPath.ps1 is available from PowerShell 3+ (see http://stackoverflow.com/questions/3667238/how-can-i-get-the-file-system-loc...) for possible solutions. But even if I hack if(!$PSScriptRoot){ $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path - Parent } into the script, it then later bails out with more PS3 specific problems. TLDR; Auto-Detection is broken with PowerShell 2 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 Wed, Mar 22, 2017 at 12:08 PM, Jürgen Hunold via Boost < boost@lists.boost.org> wrote:
Hi Rene,
Am Mittwoch, 22. März 2017, 10:11:28 CET schrieb Jürgen Hunold via Boost:
Windows 7 64bit Windows Server 2008 R2 Service Pack 1 64 bit
After some digging around, I found that the PowerShell Version on the machines is ...\boost\tools\build\src\tools\vc141helper>powershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
PS ..\boost\tools\build\src\tools\vc141helper> $Host.Version
Major Minor Build Revision ----- ----- ----- -------- 2 0 -1 -1
whereas the $PSScriptRoot Variable used in GetCLPath.ps1 is available from PowerShell 3+ (see http://stackoverflow.com/questions/3667238/how-can-i- get-the-file-system-location-of-a-powershell-script) for possible solutions. But even if I hack
if(!$PSScriptRoot){ $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path - Parent }
into the script, it then later bails out with more PS3 specific problems.
TLDR; Auto-Detection is broken with PowerShell 2
Oh how I hate what Microsoft has brought onto the programming world.. We'll work on fixing it after beta. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Tue, Mar 21, 2017 at 1:23 PM, Rene Rivera via Boost < boost@lists.boost.org> wrote:
OK Lets try this again..
New master snapshots are up. Please check them ASAP and report problems and successes.
Good build and good link test on msvc 8.0 through 14.1, 32 and 64 bit. :-) Tom
On Tue, Mar 21, 2017 at 8:37 PM, Peter Dimov via Boost < boost@lists.boost.org> wrote:
Rene Rivera wrote:
New master snapshots are up. Please check them ASAP and report problems
and successes.
Works for me with toolset=msvc-14.1. Without that, builds with 14.0.
And that was another small oversight on my part. With latest archives it should behave as expected (at least it did for me with 2017, 2015, 2013, and 2012 installed). Please 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
Rene Rivera wrote:
Works for me with toolset=msvc-14.1. Without that, builds with 14.0.
And that was another small oversight on my part. With latest archives it should behave as expected (at least it did for me with 2017, 2015, 2013, and 2012 installed). Please try again.
Confirmed, builds with 14.1 now. We should probably tell people in our message Bootstrapping is done. To build, run: .\b2 about the -j option.
On 22 March 2017 at 11:24, Peter Dimov via Boost
Rene Rivera wrote:
Works for me with toolset=msvc-14.1. Without that, builds with 14.0.
And that was another small oversight on my part. With latest archives it should behave as expected (at least it did for me with 2017, 2015, 2013, and 2012 installed). Please try again.
Confirmed, builds with 14.1 now.
We should probably tell people in our message
Bootstrapping is done. To build, run:
.\b2
about the -j option.
I also checked the snapshot and all builds for me w/ VS2017: .\b2 -j 16 Thanks to all involved! Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Mateusz Loskot via Boost Sent: 22 March 2017 14:32 To: boost@lists.boost.org Cc: Mateusz Loskot Subject: Re: [boost] [release] 1.64.0 please test master snapshot
<snip>
about the -j option. .\b2 -j 16
Please - this is Boost - not Boast ;-) Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
On 22 March 2017 at 17:08, Paul A. Bristow via Boost
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Mateusz Loskot via Boost Sent: 22 March 2017 14:32 To: boost@lists.boost.org Cc: Mateusz Loskot Subject: Re: [boost] [release] 1.64.0 please test master snapshot
<snip>
about the -j option. .\b2 -j 16
Please - this is Boost - not Boast ;-)
It's -j'ust a random number from 1 to 48 ;-) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
participants (7)
-
Jürgen Hunold -
Mateusz Loskot -
Olaf van der Spek -
Paul A. Bristow -
Peter Dimov -
Rene Rivera -
Tom Kent