I am building a project with cmake using ms visual studio. I am getting this error from MS visual studio (2010):
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets(146,5): error MSB6006: "CL.exe" exited with code -1073740777
I have not been able to find anything about this error (obv I've googled it), but I can't find a description! I also tried the error lookup tool and it didn't bring anything up.
Any idea what this error means?
I moved the project generation to a different dir (much smaller path) and the error went away, and everything compiled fine. It appears this has to do with the path length and length of the CL command.
This Link was helpful in diagnosing the problem.
Since my original question was "what is this error?" Here is the answer courtesy of #WhozCraig
0xC0000417, equivalent to STATUS_INVALID_CRUNTIME_PARAMETER.
Related
I am getting this error when compiling c++ code in the visual studio command window. The command cl /EHsc main.cpp works except for the error stated in the title. I have been trying suggestions for hours and none of them have worked. I have tried repairing, modifying, and reinstalling visual studio. Last time I used this software (about 6 months ago), I never had this issue. I had a different computer but still was using windows 10 and visual studio. Also, sometimes it doesn't give me this error and builds the .exe file, but then says "Access denied". I programmed c++ in VS a lot before and never had this issue.
I am trying to compile a new c++ project in Visual Studio 2015.
I can compile perfectly in 32 bit configuration but when I change the configuration to 64 bit, compilation crashes with a dialogue box showing message "Microsoft c/c++ Compiler Driver has stopped working"
This is the error showing in the logs
Error MSB6006 "CL.exe" exited with code -1073741701.
I tried repairing and reinstalling VS several times but did no good to me.
This the behaviour of any file I am trying to compile. Projects which were working on Visual Studio 2013 are now not compilable.
Please help. I am stuck in this issue for weeks
EDIT: I found that the compiler used in 64 is x86_amd64\cl.exe, if this means anything to you
EDIT: I tried to compile using x86_amd64\cl.exe through command line and it succeeded there
I'm using Microsoft Visual Studio 2010. It was going fine until this morning when I try to build my code. It gave me this weird error:
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms
\Win32\Microsoft.Cpp.Win32.Targets(147,5)
:error` MSB6006: "CL.exe" exited with code 1073741855.
I have no idea why this error is occuring. I need help please.
I am using Window 7.
1073741855 is 0x0x4000001f, and 0x1f is decimal 31, and 31 is ERROR_GEN_FAILURE. In other words, something is hosed and VS isn't going to tell you what it is.
Go to Control Panel/Programs and Features, right click, Uninstall/Change, Repair/Reinstall. If that doesn't fix the problem, I would uninstall VS completely and reinstall.
For those of you looking to avoid the (timely) process of uninstalling and reinstalling Visual Studio, a simple restart worked for me. I have noticed this happens more often when I have multiple Visual Studio windows open.
I am using VS2008. (C++ code). I am getting the error when compiling:
error PRJ0002 : Error result -1073741515 returned from 'C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\cl.exe'
I tried all the options available in net including one of the stackoverflow link
Visual Studio error confusion + help please
Tried shortening the path of my source solution by placing directly inside C drive.
Tried Removing any VS plugins. Tools -> Addin Manager.
My codebase is fine because the same solution is compiling fine on other machines. When I copied the solution to a particular m/c I am getting this error.
It has custom build steps, post build steps. But they are all correct because its working on other computers.
0xC0000135 (hex -1073741515) can be found in NtStatus.h
Its meaning is STATUS_DLL_NOT_FOUND. Try to look on your cl.exe with Depends
Have you tried resetting your settings of Visual Studio? It is available in Tools->Import and Export Settings. Setting it to Visual C++ Development Settings might do the trick. I know it have helped others with the same problem.
I fixed it by adding this path to the environment PATH variable:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE
some of the dependencies of the cl.exe are lying in this directory, which were unresolved.
Possibly related to my last question (note: different error code):
Why might the "fatal error C1075" error occur intermittently when using msbuild?
On our nightly 64-bit build, we see this error appear intermittently:
Generating Code...
c:\program files\microsoft visual studio 9.0\vc\include\xtree(944) : fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c[0x51120030:0x000E00AB]', line 182)
To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
Internal Compiler Error in c:\Program Files\Microsoft Visual Studio 9.0\VC\bin\x86_amd64\cl.exe. You will be prompted to send an error report to Microsoft later.
Build log was saved at "file://c:\Buildbot\synergy\1.4-win64\build\bin\synergy.dir\Release\BuildLog.htm"
See full log output.
I get the feeling that this error will be much harder to solve (if this is even possible) than the error from my last question, since it could be a bug in the compiler (but I'm hoping this isn't the case).
Is there anything that can be done to work around this problem? Maybe there's a hotfix that I can't find? Perhaps I should just contact Microsoft through connect?
Replacing the RAM fixed this (as with my other question with the different error code).
I get this error too (sometimes/rarely on all my systems x86 and x64). Just rebuild and if that doesn't work restart Visual Studio and it probably it's gone. (Nothing too serious ,at least not with my systems)