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

MSBuild error MSB6006: "cmd.exe" exited with code 1 #1655

Closed
DragonOsman opened this issue Jan 2, 2019 · 9 comments
Closed

MSBuild error MSB6006: "cmd.exe" exited with code 1 #1655

DragonOsman opened this issue Jan 2, 2019 · 9 comments
Labels

Comments

@DragonOsman
Copy link

I have this error when trying to build rename_node_bin_win.vcxproj:

node.vcxproj -> C:\node-v11.6.0\Release\\node-win.exe
  rename_node_bin_win
  'mv' is not recognized as an internal or external command,
  operable program or batch file.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(209,
5): error MSB6006: "cmd.exe" exited with code 1. [C:\node-v11.6.0\rename_node_bin_win.vcxproj]

The command for moving files and folders in Windows is move, people. Not mv. That might be the reason for that MSBuild error too.

So how do I fix this error? Anyone have any idea?

@bzoz
Copy link

bzoz commented Jan 2, 2019

Fixed in nodejs/node#25166

@DragonOsman
Copy link
Author

DragonOsman commented Jan 2, 2019

I wanted to build the latest stable release. What version is the issue fixed in, and how do I download it?

@bzoz
Copy link

bzoz commented Jan 3, 2019

It just landed, it will take some time to get released. You can always apply the patch yourself, it is very simple: https://github.com/nodejs/node/pull/25166/files

@DragonOsman
Copy link
Author

DragonOsman commented Jan 3, 2019

I cloned the repository and built it, but ended up with the pre-release version (version 12.0.0). I think I'll downgrade to the latest stable release and apply that patch then.

Anyway, there's this warning that comes up that I think you guys need to fix:

c:\node\deps\gtest\include\gtest\gtest-printers.h(778): warning C4996: 'std::tr1': warning STL4002: The non-Standard st
d::tr1 namespace and TR1-only machinery are deprecated and will be REMOVED. You can define _SILENCE_TR1_NAMESPACE_DEPRE
CATION_WARNING to acknowledge that you have received this warning. (compiling source file src\gtest.cc) [C:\node\deps\g
test\gtest.vcxproj]

std::tr1 stuff is deprecated and will be removed in a later standard update. I suggest you find alternatives for it. I also have warnings about the Windows-defined macros MIN and MAX, so I want to ask: how can I add preprocessor definitions to the command line when using vcbuld.bat? I want to add the one that removes the defines for MIN and MAX.

Anyway, I just add the patch by editing the node.gyp file?

And another question: the --prefix command I added to the configuration didn't work; how do I get Node.js installed to the C:\Program Files directory? I did add quotes around the directory name since it has spaces (plus having done it like this: --prefix="C:\\Program Files\\nodejs), and I even ran vcbuild in an elevated Developer Command Prompt.

@bzoz
Copy link

bzoz commented Jan 3, 2019

You should direct those questions to https://github.com/nodejs/help

@DragonOsman
Copy link
Author

DragonOsman commented Jan 3, 2019

I'll ask there, then. Though I get the feeling I should ask about the --prefix setting here since it's related to building Node.js.

I have the patch covered, I think. I'll ask about the rest of the stuff.

@DragonOsman
Copy link
Author

@bzoz I got npm in the Node.js distribution, but I don't know how to build it. I don't want to get the MSI just for npm. Please help.

@DragonOsman
Copy link
Author

I provided "msi" when building Node.js, but although it was all built, there's no MSI installer. When I did it before, it built the installer as well. Why didn't it this time?

@refack
Copy link
Contributor

refack commented Jan 14, 2019

FTR: Git 4 Windows and the MSYS2 toolchain are currently prerequisites for building node.

@DragonOsman for further usage assistance please open as issue in https://github.com/nodejs/help

I'm closing this as non-actionable for this repo. If you have any further issues that are related to the scope of this repo, please comment and this issue could be reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants