For example, if you try to link an object file compiled with /clr and an object file compiled with /clr:pure (machine From the MSDN document we know that the object files specified as input were compiled for different types.
If you have any question, please feelĪbout the error message. You can refer to the link’s solution to solve it. It removed the lib-圆4 library file from the VC++ directories library. The solution is that uses the /verbose switch to linker to see everything it links with. You may have old artifacts lying around.Fatal error LNK1112: module machine type '圆4' conflicts with target machine type 'X86'. If you have the correct command prompt open, then perform a clean or distclean. If you want to build for 圆4, then be sure to configure with VC-WIN64A, and be sure to open a 圆4 developer command prompt.
If you plan on building for x86 and you configure for VC-WIN32, then be sure you open the x86 command prompt, and not the 圆4 one. The Developer Command Prompt for Visual Studio automatically sets the environment variables that enable you to easily use. ĭeveloper Command Prompt for Visual Studio You can find them through Start -> Programs -> Visual Studio NNNN -> Developer Tools. It sounds like the wrong Developer Tools Command Prompt was opened. NMAKE : fatal error U1077: 'link' : return code '0x1' Link /nologo /debug /dll /implib:libcrypto.lib /out:libcrypto-1_1-圆4.dll /def:libcrypto-1_1-圆4.def || (DEL /Q libcrypto.* libcrypto-1_1-圆4.* & EXIT 1)Ĭrypto\aes\aes_cfb.obj : fatal error LNK1112: module machine type 'X86' conflicts with target machine type '圆4' IF EXIST libcrypto-1_1-圆4.dll.manifest DEL /F /Q libcrypto-1_1-圆4.dll.manifest I opened a "VS2015 圆4 Native Tools" window as opposed to a "VS2015 圆4 x86 Cross Tools" and everything worked amazingly with no issues.įrom: openssl-users on behalf of Jeffrey Walton
0 kommentar(er)
