Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vcbuild.bat fails with "input line too long" #13765

Closed
tniessen opened this issue Jun 18, 2017 · 3 comments · Fixed by #13806
Closed

vcbuild.bat fails with "input line too long" #13765

tniessen opened this issue Jun 18, 2017 · 3 comments · Fixed by #13806
Labels
build Issues and PRs related to build files or the CI. windows Issues and PRs related to the Windows platform.

Comments

@tniessen
Copy link
Member

tniessen commented Jun 18, 2017

  • Version: master
  • Platform: Windows x64 with Visual Studio 2015
  • Subsystem: vcbuild

Running vcbuild.bat appends data to the PATH environment variable. After several runs, the value of the variable becomes so long that VC batch files crash with an error message saying "Input line is too long", which is not really surprising considering the relatively small limit of about 8k for command lines on Windows.

This line calls a number of batch scripts which configure the environment to use the VS2015 toolchain:

call "%VS140COMNTOOLS%\..\..\vc\vcvarsall.bat"

This answer might offer a solution to the problem:

if not defined DevEnvDir (
    call vcvarsall.bat
)

However, I am not too familiar with VC-internal batch files and have no idea about side-effects or alternatives, so any insights would be useful here.

@seishun was able to reproduce this on VS2015, but not on VS2017.

@tniessen tniessen added build Issues and PRs related to build files or the CI. windows Issues and PRs related to the Windows platform. labels Jun 18, 2017
@tniessen
Copy link
Member Author

/cc @nodejs/platform-windows

@seishun
Copy link
Contributor

seishun commented Jun 18, 2017

cc @refack

@refack
Copy link
Contributor

refack commented Jun 20, 2017

This is a regression introduced in 780acc2.
A fix PR is coming.

refack added a commit to refack/node that referenced this issue Jul 9, 2017
PR-URL: nodejs#13806
Fixes: nodejs#13765
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Kunal Pathak <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Jul 11, 2017
PR-URL: #13806
Fixes: #13765
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Kunal Pathak <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
addaleax pushed a commit that referenced this issue Jul 18, 2017
PR-URL: #13806
Fixes: #13765
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Kunal Pathak <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Fishrock123 pushed a commit that referenced this issue Jul 19, 2017
PR-URL: #13806
Fixes: #13765
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Kunal Pathak <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants