NMAKE : Fatal error U1077, return code '0x1'
-
Hello,
I have downloaded this version of QT (4.8.6) and I configured it as followed:
configure.exe -release -opensource -confirm-license -platform win32-msvc2013 -qt-zlib -system-sqlite -qt-sql-sqlite -ltcg -fast -shared -D SQLITE_ENABLE_FTS3 -D SQLITE_ENABLE_FTS3_PARENTHESIS -no-phonon -no-multimedia -no-qt3support -no-dsp -no-vcproj -nomake demos -nomake examples -nomake tests
That ran successfully indicating that I was ready to run
nmake
, so that's what I did, and after 20 minutes of compiling it gives a fatal error, this is the output:Microsoft (R) Program Maintenance Utility Version 14.00.23026.0 Copyright (C) Microsoft Corporation. All rights reserved. "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe" -f Makefile.Release Microsoft (R) Program Maintenance Utility Version 14.00.23026.0 Copyright (C) Microsoft Corporation. All rights reserved. C:\Software\Qt\4.8.6\bin\moc.exe -DQT_SHARED -DQT_THREAD_SUPPORT -DUNICODE -DWIN32 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DJSC=QTJSC -Djscyyparse=qtjscyyparse -Djscyylex=qtjscyylex -Djscyyerror=qtjscyyerror -DWTF=QTWTF -DQT_BUILD_SCRIPT_LIB -DQT_NO_USING_NAMESPACE -DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -D_USE_MATH_DEFINES -DBUILDING_QT__=1 -DWTF_USE_ACCELERATED_COMPOSITING -D USE_SYSTEM_MALLOC -DNDEBUG -DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF -DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DNDEBUG -DJS_NO_EXPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 @tmp\moc\release_shared/mocinclude.tmp -D_MSC_VER=1800 -DWIN32 ..\3rdparty\javascriptcore\JavaScriptCore\wtf\qt\MainThreadQt.cpp -o tmp\moc\release_shared\MainThreadQt.moc C:\Software\Qt\4.8.6\bin\moc.exe -DQT_SHARED -DQT_THREAD_SUPPORT -DUNICODE -DWIN32 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DJSC=QTJSC -Djscyyparse=qtjscyyparse -Djscyylex=qtjscyylex -Djscyyerror=qtjscyyerror -DWTF=QTWTF -DQT_BUILD_SCRIPT_LIB -DQT_NO_USING_NAMESPACE -DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -D_USE_MATH_DEFINES -DBUILDING_QT__=1 -DWTF_USE_ACCELERATED_COMPOSITING -D USE_SYSTEM_MALLOC -DNDEBUG -DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF -DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DNDEBUG -DJS_NO_EXPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 @tmp\moc\release_shared/mocinclude.tmp -D_MSC_VER=1800 -DWIN32 ..\3rdparty\javascriptcore\JavaScriptCore\wtf\qt\ThreadingQt.cpp -o tmp\moc\release_shared\ThreadingQt.moc C:\Software\Qt\4.8.6\bin\moc.exe -DQT_SHARED -DQT_THREAD_SUPPORT -DUNICODE -DWIN32 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DJSC=QTJSC -Djscyyparse=qtjscyyparse -Djscyylex=qtjscyylex -Djscyyerror=qtjscyyerror -DWTF=QTWTF -DQT_BUILD_SCRIPT_LIB -DQT_NO_USING_NAMESPACE -DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -D_USE_MATH_DEFINES -DBUILDING_QT__=1 -DWTF_USE_ACCELERATED_COMPOSITING -D USE_SYSTEM_MALLOC -DNDEBUG -DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF -DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DNDEBUG -DJS_NO_EXPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 @tmp\moc\release_shared/mocinclude.tmp -D_MSC_VER=1800 -DWIN32 api\qscriptengine.h -o tmp\moc\release_shared\moc_qscriptengine.cpp C:\Software\Qt\4.8.6\bin\moc.exe -DQT_SHARED -DQT_THREAD_SUPPORT -DUNICODE -DWIN32 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DJSC=QTJSC -Djscyyparse=qtjscyyparse -Djscyylex=qtjscyylex -Djscyyerror=qtjscyyerror -DWTF=QTWTF -DQT_BUILD_SCRIPT_LIB -DQT_NO_USING_NAMESPACE -DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -D_USE_MATH_DEFINES -DBUILDING_QT__=1 -DWTF_USE_ACCELERATED_COMPOSITING -D USE_SYSTEM_MALLOC -DNDEBUG -DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF -DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DNDEBUG -DJS_NO_EXPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 @tmp\moc\release_shared/mocinclude.tmp -D_MSC_VER=1800 -DWIN32 bridge\qscriptqobject_p.h -o tmp\moc\release_shared\moc_qscriptqobject_p.cpp C:\Software\Qt\4.8.6\bin\moc.exe -DQT_SHARED -DQT_THREAD_SUPPORT -DUNICODE -DWIN32 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DJSC=QTJSC -Djscyyparse=qtjscyyparse -Djscyylex=qtjscyylex -Djscyyerror=qtjscyyerror -DWTF=QTWTF -DQT_BUILD_SCRIPT_LIB -DQT_NO_USING_NAMESPACE -DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -D_USE_MATH_DEFINES -DBUILDING_QT__=1 -DWTF_USE_ACCELERATED_COMPOSITING -D USE_SYSTEM_MALLOC -DNDEBUG -DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF -DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DNDEBUG -DJS_NO_EXPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 @tmp\moc\release_shared/mocinclude.tmp -D_MSC_VER=1800 -DWIN32 api\qscriptextensionplugin.h -o tmp\moc\release_shared\moc_qscriptextensionplugin.cpp api\qscriptextensionplugin.h(43): Error: Undefined interface NMAKE : fatal error U1077: 'C:\Software\Qt\4.8.6\bin\moc.exe' : return code '0x1' Stop. NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: '""C:\Program' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: '""C:\Program' : return code '0x2' Stop. c:\Software\Qt\4.8.6>
I have one environment variable set up in my path
C:\Software\Qt\4.8.6\bin
and I'm running Windows 7 x64.
After having tried for several days now I have no clue what could be wrong. Any help would be greatly appreciated!!Thanks.
-
Hi and welcome to devnet,
AFAIK, Visual Studio 14 is MSVC2015 not 2013. You should rather go with Qt 4.8.7 since its the latest (and last) version of the Qt 4 series.
-
Thanks SGaist!
I now downloaded the source files of Qt version 4.8.7 and tried again, but now I did
configure
with the-platform
flag set towin32-msvc2015
instead ofwin32-msvc2013
, which gave me another error right at the beginning:Qt is now configured for building. Just run nmake. To reconfigure, run nmake confclean and configure. c:\Software\Qt\4.8.7>nmake Microsoft (R) Program Maintenance Utility Version 14.00.23026.0 Copyright (C) Microsoft Corporation. All rights reserved. C:\Software\Qt\4.8.7\bin\qmake C:/Software/Qt/4.8.7/\projects.pro -o Makefile -spec win32-msvc2015 Could not find mkspecs for your QMAKESPEC(win32-msvc2015) after trying: c:\Software\Qt\4.8.6\msvc2015\mkspecs Error processing project file: C:/Software/Qt/4.8.7//projects.pro NMAKE : fatal error U1077: 'C:\Software\Qt\4.8.7\bin\qmake.EXE' : return code '0x3' Stop.
I also tried without setting the
-platform
flag at all, but that gives the same error. Any idea of what could be wrong?Thanks!
-
There's something unclean on your system, it's looking for the mkspec in your Qt 4.8.6 folder.
You should rather run your configuration from a new command line instance. Also, I'd recommend making out of source builds, that way you can just nuke the build directory if you need to start from scratch.
-
There was indeed something wrong with in the 4.8.7 folder. I just removed the old folder one and unpacked a clean version. It's now compiling and so far no errors :)
Also, I'd recommend making out of source builds, that way you can just nuke the build directory if you need to start from scratch.
Could you be a little more specific? I don't quite get what you mean by making out of source builds.
Edit
And I have an error, again..
Any clue on what could be wrong? I have to admit I am losing hope :'(... C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(47): error C2039: 'int_fast16_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(47): error C2873: 'int_fast16_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(48): error C2039: 'int_fast32_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(48): error C2873: 'int_fast32_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(48): error C2039: 'int_fast64_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(48): error C2873: 'int_fast64_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(49): error C2039: 'uint_fast8_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(49): error C2873: 'uint_fast8_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(49): error C2039: 'uint_fast16_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(49): error C2873: 'uint_fast16_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(50): error C2039: 'uint_fast32_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(50): error C2873: 'uint_fast32_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(50): error C2039: 'uint_fast64_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(50): error C2873: 'uint_fast64_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(52): error C2039: 'intmax_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(52): error C2873: 'intmax_t': symbol cannot be used in a using-declaration C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(53): error C2039: 'uintmax_t': is not a member of '`global namespace'' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(53): error C2873: 'uintmax_t': symbol cannot be used in a using-declaration NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64_x86\cl.EXE"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64\nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: '""C:\Program' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: '""C:\Program' : return code '0x2' Stop.
-
I mean: don't build in the source tree but in another folder. i.e.:
cd C:\Software\Qt mkdir build_4.8.7 cd build_4.8.7 ..\4.8.7\configure with arguments
Then you can call nmake or jom as you wish.
-
@Tomasito665 - hi, any luck with this? I'm having the same issue/errors whilst running 4.8.6 on Windows 10.
I believe i'm doing everything correctly but am thinking that there may be a dis-connection in the cstdint call somewhere...or I've mixed x86 and am64 compiles up somewhere...
anyway, i'm keen to hear what you've done to resolve this.
(I should add, there is/was a patch for running v2013 using MS2015 - hasn't resolved my issue though...)
-
Ok, so I was able to resolve my issue after a lot of messing about. The short of it was that my Makefile.release file wasn't including the cstdint header file. I'm not sure where in the configuration it went wrong (configure.exe) but I had to add to the Makefile.release file the following information:
INCPATH= -I"c:<msvc path>\VC\include"
INCPATH is already there. You need to add the rest BEFORE the rest of the path information being included. It didn't work when placed afterwards.
This worked until I came across another problem with the StringsExtras.h file, which was another issue (had to comment out the 'endif' statements on lines 79 and 91).
Anyway, if that helps someone - great!