Nmake Fatal Error U1077 Cl.exe 0x2
Contents |
1984-1998. All rights reserved. NMAKE : fatal error U1077: 'cl.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: '"c:\Program nmake fatal error u1077 cd return code 0x2 Files\Microsoft Visual Studio\VC98\bin\NMAKE.EXE"' : return code '0x2' Stop. NMAKE : nmake fatal error u1077 return code '0x1' fatal error U1077: '"c:\Program Files\Microsoft Visual Studio\VC98\bin\nmake.exe"' : return code '0x2' Stop. Compilation Failed Reason nmake fatal error u1077 return code '0xc0000135' Agent Compiler requires the environment variables of VC++ to be set appropriately before starting it. This is because, the "nmake" utility is used to compile nmake fatal error u1077 return code '0x460' the generated source files. If you are using MS VC++, you can do this by running "vcvars32.bat" present in the "Bin" directory of your VC++ installation. For example, make the following entry in you AgentCompiler.bat file or Agent Toolkit.bat (which ever you are using to start the Agent Compiler):
Nmake : Fatal Error U1077: 'cd' : Return Code '0x1'
call "
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the
Cl.exe Return Code
company Business Learn more about hiring developers or posting ads with us Stack Overflow nmake fatal error u1077 nmake exe return code 0x2 Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 u1077 0x2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Fatal error when compiling Qt in Windows up vote 1 down vote favorite I tried to build Qt 5.0.1 with https://www.webnms.com/cagent/help/troubleshoot/c_ts_agc_compile_errmsg.html MSVS2010 in Windows 7. These are my steps: Extract source code into C:\Qt\5.0.1 Start VS2010 command prompt Type configure (this step took approximately 45 minute) Type nmake After an hour I get the following error: "C:\Program Files (x86)\Microsoft DirectX SDKUtilities\bin\x86\fxc.exe" /nologo /E standardvs /T vs_2_0 /Fh shaders\standardvs.h ..\..\..\3rdparty\angle \src\libGLESv2\shaders\Blit.vs 'C:\Program' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft DirectX http://stackoverflow.com/questions/14861718/fatal-error-when-compiling-qt-in-windows SDKUtiliti es\bin\x86\fxc.exe' : return code '0x1' Stop. NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 10.0 \VC\bin\nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. I searched online, and saw many solutions, but none of them solved my problem. I even re-installed Windows and repeated those steps but I got the same error again. visual-studio-2010 qt qt5 share|improve this question edited Oct 25 '13 at 7:01 codeling 7,16411847 asked Feb 13 '13 at 19:45 Nicole 1421515 which path was it that you needed to change? I have exactly the same problem in Windows 8 with VS2013... –codeling Oct 24 '13 at 13:59 ...and changed all environment variables to not contain spaces anymore, ran configure again, but didn't help :( –codeling Oct 25 '13 at 6:55 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted You have spaces and parenthesis in your env paths. Try to use short path, you can get them
SQL Server 2014 Express resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired content We’re sorry. https://social.msdn.microsoft.com/Forums/en-US/325b5459-c469-40d0-bf6d-e3356a2f14cd/nmake-fatal-error-u1077-pathclexe-return-code-0xc0000135?forum=Vsexpressvc The content you requested has been removed. You’ll be auto redirected in 1 second. Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: NMAKE : fatal error U1077: '"path\cl.exe"' : return code '0xc0000135' Archived Forums V > Visual C++ Express Edition Question 0 Sign in to vote I am trying to compile a .c function that gets hooked fatal error to a CFD program. When the makefile generated by the CFD program invokes "NMAKE" to compile the function I get the following error: NMAKE : fatal error U1077: '"path\cl.exe"' : return code '0xc0000135' The source code of the function appears sound. It is a very simple function. My best guess is something is wrong in my environment setup or something is wrong with the Visual installation. Can anyone shed some light fatal error u1077 on what might be the cause of that fatal error? Any suggestions/help would be much appreciated. Tuesday, September 26, 2006 10:58 PM Answers 0 Sign in to vote It looks like the makefile does not have the path to where your compiler is installed. You might want to review the generated makefile and see what kind of environment variables or other parameters it expects to have set or customized so it can find the command-line compiler, the linker, and other programming-system utilities that may be needed. You can get general help about nmake from the MSDN Help in VC++ and on-line. For what the CFD program generates and how to setup an environment that is expected in the generated makefile, you'll need to consult with CFD experts, on-line sources and any documentation. Good luck, - Dennis Wednesday, September 27, 2006 5:16 AM All replies 0 Sign in to vote It looks like the makefile does not have the path to where your compiler is installed. You might want to review the generated makefile and see what kind of environment variables or other parameters it expects to have set or customized so it can find the command-line compiler, the linker, and other programming-system utilities that may be needed. You can get general help about nmake fro