Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'IA64' NMAKE : fatal error U1077 : error code

tambe__prateek
Beginner
1,318 Views

 Hi,

I am getting the following errors on 

IA-32 :  fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'IA64' NMAKE : fatal error U1077 : error code

Intel64 : nmake is not recognized as an internal or external command.

Attached is the error screenshot for both.

0 Kudos
3 Replies
mecej4
Honored Contributor III
1,318 Views

You misquoted the first error message -- the mismatch is between X86 and X64 target architectures. You probably have a mix of X86 and X64 modules (and, perhaps, object files) from previous compilations. Simply delete all .OBJ and .MOD files and reissue the NMAKE command.

The second error is of a different type. The fact that NMAKE was found during the X86 build, but not in the X64 build, suggests that there is some problem with the batch file (ifortvars.bat) that was used to start up the X64 command window. You have to identify and fix those problems.

I note that you are using a decade old compiler.

0 Kudos
gib
New Contributor II
1,318 Views

For future reference, you can copy text from the console to a text file, making it much easier to read.

Right-click in the strip at the top of the console window, choose Edit > Mark to select the text (or Edit > Select All).  Right-click again then Edit > Copy to copy the selected text to the Clipboard.  Then you can open a text file and paste the selected text.

0 Kudos
jimdempseyatthecove
Honored Contributor III
1,318 Views

Machine type IA64 is for the old Itanium processor. x64 targets the Intel64 processor types. Somewhere you have specified IA64 for 64-bit programming.

nmake.exe is part of Microsoft Visual Studio ... VC\bin or VC\bin\amd64

The Intel64 configuration does not include the ...\amd64 folder in PATH (or that folder is missing, or nmake.exe is missing from that folder).

Jim Dempsey

0 Kudos
Reply