b2 tries to open .rsp files

[Timmmm]

If you have a custom user-config.jam containing e.g.

using msvc : : "C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe" ;

And you try to build Boost with

bootstrap
b2 --user-config=C:/path/to/user-config.jam

Then it works fine with Boost 1.69.0, but with 1.70.0 you get a load of dialog boxes saying windows doesn't know how to open .rsp files.

[Timmmm]

I have bisected this. The problem is introduced into the main repo by this commit. I bisected the tools/build subrepo too but had to skip a few commits because of some unrelated error. This is the range of interest (from newest to oldest):

• Clean up msvc initialization. - Bad
• Clear the error instead of not setting it. - Skipped
• If the vswhere lookup fails, keep searching for others - Skipped
• Don't accidentally detect msvc-14.1 as msvc-14.2. - Skipped
• Added support for actually building with msvc-14.2 - Skipped
• Future one is "UNK" - Good

The error for the skipped ones is:

C:/Users/me/boost/tools/build/src/tools\msvc.jam:1388: in configure-really
*** argument error
* rule generate-setup-cmd ( version : command : parent : options * : cpu : global-setup ? : default-global-setup-options : default-setup )
* called with: ( 14.16.27023 14.16.27023 : C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64 : C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\Hostx64 : <command>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe <command>C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe : i386 :  : x86 : vcvars32.bat )
* extra argument 14.16.27023
C:/Users/me/boost/tools/build/src/tools\msvc.jam:1003:see definition of rule 'generate-setup-cmd' being called
C:/Users/me/boost/tools/build/src/tools\msvc.jam:393: in configure
C:/Users/me/boost/tools/build/src/tools\msvc.jam:345: in msvc.init
C:/Users/me/boost/tools/build/src/build\toolset.jam:44: in toolset.using
C:/Users/me/boost/tools/build/src/build\project.jam:1104: in using
C:\Users\me\user-config.jam:1: in modules.load
C:/Users/me/boost/tools/build/src\build-system.jam:255: in load-config
C:/Users/me/boost/tools/build/src\build-system.jam:449: in load-configuration-files
C:/Users/me/boost/tools/build/src\build-system.jam:607: in load
C:\Users\me\boost\tools\build\src/kernel\modules.jam:295: in import
C:\Users\me\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build
C:\Users\me\boost\boost-build.jam:17: in module scope

[Timmmm]

Ok I'm pretty sure the problem is in Clean up msvc initialization.. I cherry-picked it onto Future one is "UNK" and still get the failure.

I don't know enough about b2 to go any further I'm afraid.

[sitsofe]

Are there any clues on this one @swatanabe?

[eldiener]

I have also seen this occur occassionally in the 'develop' branch of Build when I try to invoke an invalid toolset, for which I have no 'using...' definition, or a toolset whose command as specified is invalid in some way.

[stale[bot]]

Thank you for your contributions. Main development of B2 has moved to https://github.com/bfgroup/b2 This issue has been automatically marked as "transition" to indicate the potential for needing transition to the new B2 development project.