Fatal error u1077 link

Fixes a problem in which you receive a "Fatal error U1077" error message when you use Platform Builder to create a Windows Embedded Compact 7 image that includes clone modules.

Symptoms

Consider the following scenario:

  • You have a Windows Embedded Compact 7-based OS design that includes clone modules.

  • You build the OS design in Platform Builder.


In this scenario, the build is broken. Additionally, you receive the following error message:

Unhandled Exception: System.InvalidOperationException: The environment block used to start a process cannot be longer than 65535 bytes. Your environment block is <’nnn’> bytes long. Remove some environment variables and try again. 
at System.Diagnostics.EnvironmentBlock.ToByteArray(StringDictionary sd, Boolean unicode)
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Microsoft.PlatformBuilder.MainClass.Main(String[] args)
NMAKE : fatal error U1077: C:WINCE700publiccommonoakbini386SysgenMake.EXE: return code ‘0xe0434f4d’

Cause

When you include clone modules in an OS design, SysgenMake.exe checks the environment block size for all modules. This process occurs when the NMAKE/RES2RES process is called during the OS design build. For some modules, such as the Coredllhs.dll module, the environment block size increases beyond the maximum allowed size (less than 64 KB). This causes the build to break, and then the «fatal error U1077» error message is generated.

Resolution

Software update information

A supported software update that is named «Windows Embedded Compact 7 Monthly Update March 2012» is now available from Microsoft. In the «File information» section, the package file name contains the processor type.

Note This Windows Embedded Compact 7 Monthly Update is available for download from the Microsoft Download Center:

Windows Embedded Compact 7 Updates

Prerequisites

This update is supported only if all previously issued updates for this product have also been installed.

Restart requirement

After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:

  • On the Build menu, click Clean Solution, and then click Build Solution.

  • On the Build menu, click Rebuild Solution.

You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Files that are included in this update package

File name

File size

Date

Time

Path

Sysgenmake.exe

16,240

22-Mar-2012

06:18

PublicCommonOakBinI386

References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Need more help?

I am trying to compile Qt 4.7.4, but I always get this error:

mt.exe: general error c101008d: Failed to write the updated manifest to the resource of file "releasetutorial5.exe". The system cannot find the file specified. 
NMAKE : fatal error U1077: '"C:Program Files(x86)Microsoft SDKsWindowsv7.0Abinmt.exe"' : return code '0x1f'
Stop.
NMAKE : fatal error U1077: '"C:Program Files(x86)Microsoft Visual Studio 10.0VCBINnmake.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.

Using the Visual Studio Command prompt I executed these commands:

configure -debug-and-release -opensource -platform win32-msvc2010
nmake

What can I do to resolve this error?

asked Apr 27, 2012 at 18:47

Pedro's user avatar

PedroPedro

4,07010 gold badges56 silver badges96 bronze badges

1

So apparently tutorial5.exe is failing to build properly, or completely, and the exe never gets created. Mt.exe is a windows post-build tool used for generating signed files and catalogs. It returns an error because it can’t find the file.

The solution to your issue involves excluding the demos and tutorials from your build, or finding the bug in the source code for tutorial 5 so that it builds properly. Or you could even put a dummy version of tutorial5.exe there just to see if that is the only error that comes up.

Chances are that the bug in the source code has something to do with the difference between the default compiler tool for Qt in Windows (MingW) and the msvs2010 compiler and the way they are trying to handle some windows specific code.

How to Exclude the Examples When Building Qt

Other people online with similar projects have excluded the examples from the nmake build call using the flag «sub-src».

  • Error nmaking 4.7.2 with msvs2010

  • How to build Qt 4.3.4 without examples and demos

What is tutorial5.exe

Here is the location in the default build of Qt for release/tutorial5.exe:

C:QtSDKExamples4.7qtestlibtutorial5

and here it is in the documentation: Qt 4.8: Chapter 5: Writing a Benchmark

You probably should submit a ticket describing the problem to the Qt project: bugreports.qt.io

Good luck.

MBach's user avatar

MBach

1,63616 silver badges30 bronze badges

answered May 18, 2012 at 0:05

phyatt's user avatar

phyattphyatt

18.2k5 gold badges60 silver badges79 bronze badges

Similar error with a Qt console application with Qt 4.8.1, Creator 2.7.1, MSVC2010 Express on Windows 7 64 bit:

"mt.exe : general error c101008d: Failed to write the updated manifest to the resource of file ... " 

And then something along

The process cannot access the file because it is being used by another process.

However, the application is built and then can be «Run» from within Creator.
The error also occurs with «Build» i.e. not «Run».
I initally thought this might be a timing problem, e.g. creator is starting the shell to run the program too soon.
It works allright (no error) after the file has been deleted.

Maybe my GIT (or TortoiseGIT) is accessing the file although I cannot see those processes.

Edit: it could also be a virus scanner checking the file being written..
Edit2: confirmed: temporarily disabling the scanner resolves the problem

answered Jul 4, 2013 at 10:04

handle's user avatar

handlehandle

6,1793 gold badges51 silver badges80 bronze badges

1

Try running the Microsoft visual studio command prompt as admin. When you go to the charm panel and search for MSVS prompt, right click and run as admin.

David Waters's user avatar

David Waters

11.9k7 gold badges41 silver badges76 bronze badges

answered Jan 20, 2015 at 3:54

zamani's user avatar

  • Remove From My Forums
  • Question

  • I’m getting this error: C:WINCE500build.log(1) : error SYSGEN0000: error(s) in sysgen phase, when I opened by build build.txt.

    coredll.def : error LNK2001: unresolved external symbol DeregisterBluetoothCOMPort
    coredll.def : error LNK2001: unresolved external symbol RegisterBluetoothCOMPort
    coredll.def : error LNK2001: unresolved external symbol RequestBluetoothNotifications
    coredll.def : error LNK2001: unresolved external symbol StopBluetoothNotifications

    NMAKE : fatal error U1077: ‘link’ : return code ‘0x460’
    Stop.
    NMAKE : fatal error U1077: ‘C:WINCE600sdkbini386nmake.exe’ : return code ‘0x2’
    Stop.
    NMAKE : fatal error U1077: ‘C:WINCE600sdkbini386nmake.exe’ : return code ‘0x2’
    Stop.

    It looks like BSP is not finding the implementation for those four function,  could anybody tell me how to resolve this those linker error? I will appreciate your help

Answers

  • Verify the Sysgen variable related to Bluetooth are set in your build. If everything is fine try with clean sysgen.


    Jeslin Paul

    • Marked as answer by

      Friday, May 17, 2013 7:26 PM

  • A quick Google search for RequestBluetoothNotifications and I find the documentation (http://msdn.microsoft.com/en-us/library/aa916492.aspx) which clearly documents that the library is coredll.lib.

    Since you absolutly must have coredll.lib, this suggests that Jeslin was on the right path when he suggested checking your SYSGEN variables to ensure that you have included Bluetooth support.


    Bruce Eitman (eMVP)
    Senior Engineer
    Bruce.Eitman AT Eurotech DOT com
    My BLOG http://geekswithblogs.net/bruceeitman

    Eurotech Inc.
    www.Eurotech.com

    • Marked as answer by
      Liang1
      Friday, May 17, 2013 7:26 PM

I am trying to compile models into a .dll in order use for HIL simulation, but MATLAB shows en error when I attempt to build the file. I have the correct System Target File selected, the Solver is selected as Fixed-Step Discrete, and I ran the mex -setup to select the Microsoft Visual C++ 2010 Express compiler on my PC. Once I attempt to build, I get the following:

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved.

1 file(s) copied.

1 file(s) copied.

### Compiling the source Compile_Model_Example

cl -Od -DUSE_RTMODEL -DNI_ROOTMODEL_Compile_Model_Example -DMODEL=Compile_Model_Example -DRT -DNUMST=1 -DTID01EQ=0 -DNCSTATES=0 -DMT=0 -DHAVESTDIO -DNATIONAL_INSTRUMENTS_SIT -D_CRT_SECURE_NO_DEPRECATE -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS -D_X86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -DNTDDI_VERSION=0x05000000 -D_WIN32_IE=0x0500 -DWINVER=0x0500 /MT -DNI_VERISTAND_MAINMODELFILE Compile_Model_Example.c

Compile_Model_Example.c

### Compiling the model data file Compile_Model_Example_data

cl -Od -DUSE_RTMODEL -DNI_ROOTMODEL_Compile_Model_Example -DMODEL=Compile_Model_Example -DRT -DNUMST=1 -DTID01EQ=0 -DNCSTATES=0 -DMT=0 -DHAVESTDIO -DNATIONAL_INSTRUMENTS_SIT -D_CRT_SECURE_NO_DEPRECATE -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS -D_X86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -DNTDDI_VERSION=0x05000000 -D_WIN32_IE=0x0500 -DWINVER=0x0500 /MT -DNI_VERISTAND_MODELDATAFILE Compile_Model_Example_data.c

Compile_Model_Example_data.c

### Compiling rtGetInf.c

cl -Od -DUSE_RTMODEL -DNI_ROOTMODEL_Compile_Model_Example -DMODEL=Compile_Model_Example -DRT -DNUMST=1 -DTID01EQ=0 -DNCSTATES=0 -DMT=0 -DHAVESTDIO -DNATIONAL_INSTRUMENTS_SIT -D_CRT_SECURE_NO_DEPRECATE -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS -D_X86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -DNTDDI_VERSION=0x05000000 -D_WIN32_IE=0x0500 -DWINVER=0x0500 /MT rtGetInf.c

rtGetInf.c

### Compiling rtGetNaN.c

cl -Od -DUSE_RTMODEL -DNI_ROOTMODEL_Compile_Model_Example -DMODEL=Compile_Model_Example -DRT -DNUMST=1 -DTID01EQ=0 -DNCSTATES=0 -DMT=0 -DHAVESTDIO -DNATIONAL_INSTRUMENTS_SIT -D_CRT_SECURE_NO_DEPRECATE -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS -D_X86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -DNTDDI_VERSION=0x05000000 -D_WIN32_IE=0x0500 -DWINVER=0x0500 /MT rtGetNaN.c

rtGetNaN.c

### Compiling rt_nonfinite.c

cl -Od -DUSE_RTMODEL -DNI_ROOTMODEL_Compile_Model_Example -DMODEL=Compile_Model_Example -DRT -DNUMST=1 -DTID01EQ=0 -DNCSTATES=0 -DMT=0 -DHAVESTDIO -DNATIONAL_INSTRUMENTS_SIT -D_CRT_SECURE_NO_DEPRECATE -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS -D_X86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -DNTDDI_VERSION=0x05000000 -D_WIN32_IE=0x0500 -DWINVER=0x0500 /MT rt_nonfinite.c

rt_nonfinite.c

### Compiling NIVeriStand_main.c

cl -Od -DUSE_RTMODEL -DNI_ROOTMODEL_Compile_Model_Example -DMODEL=Compile_Model_Example -DRT -DNUMST=1 -DTID01EQ=0 -DNCSTATES=0 -DMT=0 -DHAVESTDIO -DNATIONAL_INSTRUMENTS_SIT -D_CRT_SECURE_NO_DEPRECATE -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS -D_X86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -DNTDDI_VERSION=0x05000000 -D_WIN32_IE=0x0500 -DWINVER=0x0500 /MT NIVeriStand_main.c

NIVeriStand_main.c

### Compiling Compile_Model_Example.rc

rc Compile_Model_Example.rc

Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385

Copyright (C) Microsoft Corporation. All rights reserved.

### Linking …

C:Program FilesMATLABR2011asysperlwin32binperl C:Program FilesMATLABR2011artwctoolsmkvc_lnk.pl Compile_Model_Example.lnk Compile_Model_Example.obj Compile_Model_Example_data.obj rtGetInf.obj rtGetNaN.obj rt_logging.obj rt_nonfinite.obj NIVeriStand_main.obj rt_sim.obj Compile_Model_Example.res

‘C:Program’ is not recognized as an internal or external command, operable program or batch file.

NMAKE : fatal error U1077: ‘C:Program’ : return code ‘0x1’

Stop.

The make command returned an error of 2

‘An_error_occurred_during_the_call_to_make’ is not recognized as an internal or external command, operable program or batch file. ### Build procedure for model: ‘Compile_Model_Example’ aborted due to an error.

—————————————————————

I also noticed I get a similar statement when running mex -setup:

>> mex -setup

‘C:Program’ is not recognized as an internal or external command, operable program or batch file.

Welcome to mex -setup. This utility will help you set up a default compiler.

Please choose your compiler for building MEX-files:

Would you like mex to locate installed compilers [y]/n?

What should I do next to fix this issue? Thanks

This topic has been deleted. Only users with topic management privileges can see it.

  • Hello,

    Below is my error. Could anyone give some hint how to overcome this? Thank you.
    _
    NMAKE : fatal error U1077: ‘»C:Program Files (x86)Microsoft Visual Studio 12.0VCBINamd64link.EXE»‘ : return code ‘0x458’
    Stop.
    NMAKE : fatal error U1077: ‘»C:Program Files (x86)Microsoft Visual Studio 12.0VCBINamd64nmake.exe»‘ : return code ‘0x2’
    Stop.
    The process «C:Program Files (x86)Microsoft Visual Studio 12.0VCBINamd64nmake.exe» exited with code 2.
    Error while building/deploying project ants2 (kit: Desktop Qt 5.7.0 MSVC2013 64bit)
    The kit Desktop Qt 5.7.0 MSVC2013 64bit has configuration issues which might be the root cause for this problem.
    When executing step «Make»«`
    //your code here

  • Hi
    Often just path problems.

    https://forum.qt.io/topic/56437/how-to-fix-error-while-building-deploying-project

    You should check your kits.

    http://doc.qt.io/qtcreator/creator-targets.html

    Im sorry I cant show how it shall look but I use only mingw on windows.

  • Hello mrjj.
    Many thanks for your quick reply.
    I tried Qt5.7 and Microsoft Visual C++ Compiler 12.0(x86_amd64) as in the example of your second link.
    I’m still getting a similar error:


    Generating Code…
    link /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /SUBSYSTEM:WINDOWS «/MANIFESTDEPENDENCY:type=’win32′ name=’Microsoft.Windows.Common-Controls’ version=’6.0.0.0′ publicKeyToken=’6595b64144ccf1df’ language=’‘ processorArchitecture=’‘» /MANIFEST:embed /OUT:releaseants2.exe @C:UsersjsmAppDataLocalTempnm15D5.tmp
    libCore.lib(libCore.dll) : fatal error LNK1112: module machine type ‘X86’ conflicts with target machine type ‘x64’
    NMAKE : fatal error U1077: ‘»C:Program Files (x86)Microsoft Visual Studio 12.0VCBINx86_amd64link.EXE»‘ : return code ‘0x458’
    Stop.
    NMAKE : fatal error U1077: ‘»C:Program Files (x86)Microsoft Visual Studio 12.0VCBINnmake.exe»‘ : return code ‘0x2’
    Stop.
    16:42:12: The process «C:Program Files (x86)Microsoft Visual Studio 12.0VCBINnmake.exe» exited with code 2.
    Error while building/deploying project ants2 (kit: Qt 5.7 MSVC2013_64bit MV C++ Comppiler 12.0 (x86_amd64))
    The kit Qt 5.7 MSVC2013_64bit MV C++ Comppiler 12.0 (x86_amd64) has configuration issues which might be the root cause for this problem.
    When executing step «Make»

  • Hi
    Have you tried to see if VS is happy?
    Open the Vs developer command prompt and
    see if
    link.EXE
    and
    nmake.exe
    can be found and respond. ( it lists options)

    Also,
    fatal error LNK1112: module machine type ‘X86’ conflicts with target machine type ‘x64’
    seems to be a mixup with 32 / 64 bit.

    Did you install Qt 64bit for VS2013 ?

    Also, you really need/want to use visual studio?
    Qt comes with mingw compiler which works flawlessly and have zero setup.
    However, for using external libs (non Qt) , VS is often better supported than mingw.

  • mrjj,

    I really appreciate your help.
    The link.exe have executed and showed me the parameters list.
    The nmake.exe launchs the executable from Microsoft but it gives an error:
    NMAKE : fatal error U1064: MAKEFILE not found and no target specified Stop.

    In Build&Run -> Qt versions Qt 64bit for VS2013 and VS2015 are auto-detected in these locations:
    C:Qt5.7msvc2013_64binqmake.exe
    C:Qt5.7msvc2015_64binqmake.exe

    In my project there some external libraries indeed.
    Thank you very much for your time.

  • Of course there is no makefile there… sorry

  • @jmarcos no no its fine
    Just checking that linker and make could be found.
    nmake has to say «no file» thing.

    I never saw it say
    «The kit Qt 5.7 MSVC2013_64bit MV C++ Comppiler 12.0 (x86_amd64) has configuration issues which might be the root cause for this problem.»

    so googling to see for any hints.

  • @mrjj, just to clarify: «Qt 5.7 MSVC2013_64bit MV C++ Comppiler 12.0 (x86_amd64) » was the name I gave to kit selecting MSCV2013_64bit and MV C++ compiler 12.0…

  • Oh, i forgot to ask.
    If you create a default GUI project in Creator and try to build, it still says this?
    Just to rule out its not make/project file related as such. (for the ant2 project)

  • Yes, I just tried a Qt quick application and it was built fine and run as well.

  • 17:38:39: Starting: «C:Program Files (x86)Microsoft Visual Studio 14.0VCBINamd64nmake.exe»
    «C:Program Files (x86)Microsoft Visual Studio 14.0VCBINamd64nmake.exe» -f Makefile.Release
    17:38:39: The process «C:Program Files (x86)Microsoft Visual Studio 14.0VCBINamd64nmake.exe» exited normally.
    17:38:39: Elapsed time: 00:00.

  • @jmarcos The previous was for the TestApp not ANTS2 Project!

  • Hi
    a C++ Qt quick application ?
    Could you try a
    «Qt widget application» default project?

    If that also works, then it must be that projects make file that is not ok?

  • The default «Qt widget application» was successfully built.

  • @jmarcos
    Ok, then the toolchain does work.
    It must be the project then ?
    Did you make the make file yourself or what is its origin?

  • The make file is made by the qmake.

    This is the header of the automatic created file:

    #############################################################################
    # Makefile for building: ants2
    # Generated by qmake (3.0) (Qt 5.7.0)
    # Project:  ..ANTS2ants2.pro
    # Template: app
    # Command: C:Qt5.7msvc2015_64binqmake.exe -spec win32-msvc2015 -o Makefile ..ANTS2ants2.pro
    #############################################################################
  • hmm
    so here it uses 2015 compiler

    I wonder if the default sample used vs2013 ?

    Did you install BOTH Qt 2015 and Qt 2013 binary packets?

    Also did u try with
    -spec win32-msvc2013

    ?

  • Yes, both are installed and also tried win32-msvc2013.
    mrjj, many thanks for your help. Let me discuss this problem tomorrow with the code developer. Today I updated Qt to Qt5.7and after that, when I tried to compile the Project I want to build and run (to use the application — a simulation software), I got the building error I reported here in the Forum. The Project was built before for Qt5.4 without problems.

  • @jmarcos
    Good plan.
    Its this public (the simulation software) ?
    I mean to try the project.

  • @jmarcos

    Hi
    Tomorrow could you
    Show compiler, debugger and kit screens from creator (with the set options)
    Then grab the qmake line from the Creator’s output pane and show here too ?

  • Problem

    Error: NMAKE : fatal error U1077: ‘cl’: return code ‘0x80’

    Symptom

    Attempts to build TagetRTS model may produce the error above.

    Cause

    This error indicates that Microsoft Visual Studio is not correctly installed, or that the paths to it are set incorrectly.

    Resolving The Problem

    SDL Suite and TAU Developer

    Problem:
    I am trying to build your example. However I end up with the following error:
    NMAKE : fatal error U1077: ‘cl’: return code ‘0x80’

    Answer:
    This error indicates that Microsoft Visual Studio is not correctly installed, or that the paths to it are set incorrectly. Either reinstall it, set the paths correctly or use another compiler.

    You can also try to launch the vsvars32.bat (located in e.g. C:Program FilesMicrosoft Visual Studio .NET 2003Common7Tools folder) from the command prompt and then launch Tau from the same command promt by running the «vcs.exe» command.

    Another option could be create a dos batch script to carry out the above and then create a shortcut to the batch script. The following is a simple batch script to illustrate this:

    ———- Start of Batch Script ———-

    :: tau.bat
    :: Sets up the .NET variables and then launches TAU G2.
    ::
    @echo off

    call «C:Program FilesMicrosoft Visual Studio .NET 2003Common7Toolsvsvars32.bat»

    @CLS

    @echo off

    C:TelelogicTAU_3.0binvcs.exe

    @EXIT

    ———- End of Batch Script ———-

    Tau DeveloperTG2-FAQ-10AnswerProduct versionPartner ContentInternal ContentCategoryReference ID

    [{«Product»:{«code»:»SSYQGX»,»label»:»Rational Tau»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»General Information»,»Platform»:[{«code»:»PF025″,»label»:»Platform Independent»}],»Version»:»Version Independent»,»Edition»:»»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]

    Содержание

    1. Nmake fatal error u1077 cl возвращенный код 0x2
    2. Answered by:
    3. Question
    4. nmake gives error on appslibapps.c(1818) : NMAKE : fatal error U1077 return code ‘0x2’ Stop. #10277
    5. Comments
    6. Ошибка при компиляции Qt: nmake фатальная ошибка U1077
    7. Как исключить примеры при построении Qt
    8. Что такое tutorial5.exe
    9. Why do I receive a «NMAKE : fatal error U1077: ‘cl’ : return code ‘0x2’ » error when I build my model in Real-Time Workshop 5.0.1 (R13)?
    10. Direct link to this question
    11. Direct link to this question
    12. Accepted Answer
    13. Direct link to this answer
    14. Direct link to this answer
    15. More Answers (0)
    16. See Also
    17. Categories
    18. Products
    19. Community Treasure Hunt
    20. How to Get Best Site Performance
    21. Americas
    22. Europe
    23. Asia Pacific
    24. FIX: «NMAKE : fatal error U1077» error message in the build log when you try to clone the Calibrui module for a Windows Embedded Compact 7-based image on a computer that is running Windows XP SP3
    25. Symptoms
    26. Resolution
    27. Software update information
    28. Prerequisites
    29. Restart requirement
    30. Update replacement information
    31. File information
    32. More Information
    33. References

    Nmake fatal error u1077 cl возвращенный код 0x2

    Answered by:

    Question

    I’m trying to follow this tutorial to install ruby/tk. http://www.tkdocs.com/tutorial/install.html
    Under the section for installing on windows they instruct to download Visual Studio 2010 (link provided on the webpage) to compile the source.

    When I run the configure batch file;
    win32configure.bat —prefix=c:ruby

    I get this error:
    NMAKE : fatal error U1077: ‘cl’ : return code ‘0x2’

    How can I fix this? Does this mean nmake can’t find cl.exe? They are in the same directory.

    My system is Win7 64 bit.

    Here’s the content of the configure.bat:

    @echo off
    . Don’t set environment variable in batch file other than autoexec.bat
    . to avoid «Out of environment space» problem on Windows 95/98.
    . set TMPMAKE=

    .mak conf = %0
    echo>>

    .mak @-$(MAKE) -l$(MAKEFLAGS) -f $(@D)/setup.mak
    :loop
    if «%1» == «» goto :end
    if «%1» == «—prefix» goto :prefix
    if «%1» == «—srcdir» goto :srcdir
    if «%1» == «srcdir» goto :srcdir
    if «%1» == «—target» goto :target
    if «%1» == «target» goto :target
    if «%1» == «—with-static-linked-ext» goto :extstatic
    if «%1» == «—with-winsock2» goto :winsock2
    if «%1» == «—program-suffix» goto :suffix
    if «%1» == «—program-name» goto :installname
    if «%1» == «—install-name» goto :installname
    if «%1» == «—so-name» goto :soname
    if «%1» == «—enable-install-doc» goto :enable-rdoc
    if «%1» == «—disable-install-doc» goto :disable-rdoc
    if «%1» == «—extout» goto :extout
    if «%1» == «-h» goto :help
    if «%1» == «—help» goto :help
    echo>>

    .mak «%1»
    shift
    goto :loop
    :srcdir
    echo>>

    .mak «srcdir=%2»
    shift
    shift
    goto :loop
    :prefix
    echo>>

    .mak «prefix=%2»
    shift
    shift
    goto :loop
    :suffix
    echo>>

    .mak «RUBY_SUFFIX=%2»
    shift
    shift
    goto :loop
    :installname
    echo>>

    .mak «RUBY_INSTALL_NAME=%2»
    shift
    shift
    goto :loop
    :soname
    echo>>

    .mak «RUBY_SO_NAME=%2»
    shift
    shift
    goto :loop
    :target
    echo>>

    .mak «%2»
    shift
    shift
    goto :loop
    :extstatic
    echo>>

    .mak «EXTSTATIC=static»
    shift
    goto :loop
    :winsock2
    echo>>

    .mak «USE_WINSOCK2=1»
    shift
    goto :loop
    :enable-rdoc
    echo>>

    .mak «RDOCTARGET=install-doc»
    shift
    goto :loop
    :disable-rdoc
    echo>>

    .mak «RDOCTARGET=install-nodoc»
    shift
    goto :loop

    Источник

    nmake gives error on appslibapps.c(1818) : NMAKE : fatal error U1077 return code ‘0x2’ Stop. #10277

    Hello, i’m trying to compile the latest soruces of openssl that i’ve downloaded from here.
    I have MS Visual Studio 2017, ActivePerl and NASM installed

    so i did commands as you instructed:

    and after command nmake compiling begins but stops with error:

    The text was updated successfully, but these errors were encountered:

    It is simply that /WX enables treating warnings as errors and stop compilation. Don’t know why the option is there when for x64 build on Windows, for instance, there are still a lot of compiler warnings of C4244 and C4267. If you just want to compile, remove /WX from the generated makefile.

    It is simply that /WX enables treating warnings as errors and stop compilation. Don’t know why the option is there when for x64 build on Windows, for instance, there are still a lot of compiler warnings of C4244 and C4267. If you just want to compile, remove /WX from the generated makefile.

    VC-WIN32 builds should be warning free so /WX should be ok there.

    @barmaley997 — I see this is the master version of OpenSSL, so my guess is some newly introduced warning is causing the problem.

    You are probably better off not using the master version and instead try OpenSSL 1.1.1

    We shouldn’t force /WX, just as we shouldn’t (and don’t) force -Werror

    We shouldn’t force /WX, just as we shouldn’t (and don’t) force -Werror

    Good point..although perhaps we should for dev builds? At least for VC-WIN32 which (should be) warning free. It would be a shame to lose that.

    So it should be possible to give /WX when configuring, is what you’re saying. I totally agree, and it is possible, like this:

    (with openssl 1.1.1 at least)

    So it should be possible to give /WX when configuring, is what you’re saying.

    Not, only should it be possible — but as developers we should do it. Certainly for AppVeyor builds. Remembering the particular incantation required for any particular platform isn’t ideal. Perhaps amend —strict-warnings to do the right thing?

    Источник

    Ошибка при компиляции Qt: nmake фатальная ошибка U1077

    Я пытаюсь скомпилировать Qt 4.7.4, но всегда получаю эту ошибку:

    С помощью командной строки Visual Studio я выполнил следующие команды:

    Что я могу сделать для устранения этой ошибки?

    Таким образом, очевидно, что tutorial5.exe не работает правильно или полностью, и exe никогда не создается. Mt.exe – это инструмент построения постсооружений Windows, который используется для создания подписанных файлов и каталогов. Он возвращает ошибку, потому что не может найти файл.

    Решение вашей проблемы включает исключение демонстраций и обучающих программ из вашей сборки или поиск ошибки в исходном коде для учебника 5, чтобы он правильно строился. Или вы даже можете поместить фиктивную версию tutorial5.exe, чтобы увидеть, является ли это единственной ошибкой.

    Скорее всего, ошибка в исходном коде имеет какое-то отношение к разнице между инструментом компилятора по умолчанию для Qt в Windows (MingW) и компилятором msvs2010 и тем, как они пытаются обрабатывать определенный код Windows.

    Как исключить примеры при построении Qt

    Другие люди в сети с аналогичными проектами исключили примеры из вызова сборки nmake, используя флаг “sub-src”.

    Что такое tutorial5.exe

    Вот расположение в построенной по умолчанию Qt для release/tutorial5.exe :

    Вероятно, вам следует отправить билет, описывающий проблему, в проект Qt: bugreports.qt.io

    Аналогичная ошибка с консольным приложением Qt с Qt 4.8.1, Creator 2.7.1, MSVC2010 Express в Windows 7 64 бит:

    А потом что-то вдоль

    Однако приложение построено, а затем может быть “Run” изнутри Creator.
    Ошибка также возникает при “Build”, то есть не “Run”.
    Я начал думать, что это может быть проблема синхронизации, например. создатель запускает оболочку для запуска программы слишком рано.
    Он работает полностью (без ошибок) после удаления файла.

    Может быть, мой GIT (или TortoiseGIT) обращается к файлу, хотя я не могу видеть эти процессы.

    Изменить: это может быть и антивирусный сканер, проверяющий записываемый файл.
    Edit2: подтверждено: временное отключение сканера устраняет проблему

    Попробуйте запустить командную строку Microsoft visual studio в качестве администратора. Когда вы переходите на панель шарма и ища приглашение MSVS, щелкните правой кнопкой мыши и запустите его как admin.

    Источник

    Why do I receive a «NMAKE : fatal error U1077: ‘cl’ : return code ‘0x2’ » error when I build my model in Real-Time Workshop 5.0.1 (R13)?

    Direct link to this question

    Direct link to this question

    Accepted Answer

    Direct link to this answer

    Direct link to this answer

    0 Comments

    More Answers (0)

    See Also

    Categories

    Products

    Find the treasures in MATLAB Central and discover how the community can help you!

    An Error Occurred

    Unable to complete the action because of changes made to the page. Reload the page to see its updated state.

    Select a Web Site

    Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .

    You can also select a web site from the following list:

    How to Get Best Site Performance

    Select the China site (in Chinese or English) for best site performance. Other MathWorks country sites are not optimized for visits from your location.

    Americas

    Europe

    • Belgium (English)
    • Denmark (English)
    • Deutschland (Deutsch)
    • España (Español)
    • Finland (English)
    • France (Français)
    • Ireland (English)
    • Italia (Italiano)
    • Luxembourg (English)
    • Netherlands (English)
    • Norway (English)
    • Österreich (Deutsch)
    • Portugal (English)
    • Sweden (English)
    • Switzerland
      • Deutsch
      • English
      • Français
    • United Kingdom (English)

    Asia Pacific

    • Australia (English)
    • India (English)
    • New Zealand (English)
    • 中国
      • 简体中文 Chinese
      • English
    • 日本 Japanese (日本語)
    • 한국 Korean (한국어)

    Accelerating the pace of engineering and science

    MathWorks is the leading developer of mathematical computing software for engineers and scientists.

    Источник

    FIX: «NMAKE : fatal error U1077» error message in the build log when you try to clone the Calibrui module for a Windows Embedded Compact 7-based image on a computer that is running Windows XP SP3

    Symptoms

    Consider the following scenario:

    You have Windows Embedded Compact 7 installed on a computer that is running Windows XP Service Pack 3 (SP3).

    You clone the Calibrui module for a Windows Embedded Compact 7-based image in Platform Builder.

    You build the image.

    In this scenario, you receive the following error message in the build log:

    NMAKE : fatal error U1077:
    ‘C:WINCE700publiccommonoakBini386SysgenMake.EXE’ : return code
    ‘0xc0150004’

    Note You may also receive a different error message when you try to build a Windows Embedded Compact 7 image by using platform builder. For more information about that error message, see the «More Information» section. Be aware that this update does not resolve that error message.

    Resolution

    Software update information

    A supported software update is now available from Microsoft as Windows Embedded Compact 7 Monthly Update May 2012. In the «File information» section, the package file name contains the processor type.

    Note This Windows Embedded Compact 7 monthly update is available for download from the following Microsoft Download Center website:

    Prerequisites

    This update is supported only if all previously issued updates for this product have also been installed.

    Restart requirement

    After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:

    On the Build menu, click Clean Solution, and then click Build Solution.

    On the Build menu, click Rebuild Solution.

    You do not have to restart the computer after you apply this software update.

    Update replacement information

    This update does not replace any other updates.

    File information

    The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

    Files that are included in this update package

    More Information

    When you try to build a Windows Embedded Compact 7 image by using platform builder, there is a very remote possibility that you may receive the following error message:

    The environment block used to start a process cannot be longer than 65535 bytes. Your environment block is 72706 bytes long. Remove some environment variables and try again.

    Note The actual environment block size (72706 in this case) is variable and depends on your specific computer and settings.

    To work around this problem, take one or more of the following actions:

    Reduce unwanted Sysgen variables from the project.

    Change folder names, solution names, and so on to reduce the directory path lengths that are used.

    Reduce unwanted locales from the project.

    These workarounds will in effect reduce the environment variable size and help you keep the environment variable block size under 65535 bytes.

    References

    For more information about how to clone the Calibrui module, go to the following Microsoft Developer Network (MSDN) website:

    Cloning the Calibrui ModuleFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

    824684 Description of the standard terminology that is used to describe Microsoft software updates

    Источник

    Понравилась статья? Поделить с друзьями:

    Читайте также:

  • Fatal error wchar h no such file or directory
  • Fatal error wasm code commit allocation failed process out of memory
  • Fatal error warn info debug trace
  • Fatal error warface
  • Fatal error war3

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии