Issue using fortran compiler for Arch-type Intel 64

[Bastien_T_]

Hi everyone,

We acquiered recently Parallel Studio XE 2015, in order to be able to compile user subroutine for mechanical simulation software. I think installation of the product went alright until I tried making use of it.

Issue is, when I want to build my subroutine, I need to set the Arch-type for the compiler to Intel-64 (running on Intel Xeon, Win7). So I modified of command-prompt's target to :

C:\Windows\SysWOW64\cmd.exe /k "E:\App\Intel\Composer XE 2015\bin\ipsxe-comp-vars.bat" ARCHTYPE"

When ARCHTYPE is defined to IA32, it works fine, despite not building to the right architecture and thus getting error during linking. When ARCHTYPE is defined toIntel64, I got the message the configuration file is missing (though Intel64 sources are present in the install directory). It is compiling though, but LINK is not defined.

Has anyone had the same situation or have any tips to help me out ?

Thank you,

Bastien

PS. I have experience in programing in c++ back few year, yet is was on linux plateform.

[Kevin_D_Intel]

It is not necessary to “roll one’s own” command-prompt unless you wish. Our product installs a set of command-prompt shortcuts that pre-initialize the command-prompt environment accordingly for the Intel compiler and associated Visual Studio environment. Have a look under: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Intel Parallel Studio XE 2015\Compiler and Performance Libraries\Command Prompt with Intel Compiler XE v15.0

The missing LINK setting I bet relates to your target setting not including the Visual Studio argument to the ipsxe-comp-vars.bat script.

To “roll one’s own” command-prompt it is probably easiest to just copy the Target field for the shortcut corresponding to your version of Visual Studio from the directory that I mentioned above.

Hope that helps.

[mecej4]

Two items that I would think of checking in a similar situation:

• The Start Menu shortcuts to the command line windows for IFort-32 and IFort-64 do not point to the same version of CMD.EXE. The former uses C:\Windows\SysWOW64\cmd.exe whereas the latter uses C:\Windows\System32\cmd.exe. The two cmd.exe files are not the same; the first one is a 32 bit PE exe, whereas the second is a 64-bit PE+ exe. Therefore, if you start with the former and simplify modify the arguments to cmd.exe, you may run into problems.
• Did you install the 64-bit C/C++ package when you installed Visual Studio? That package would be what pulls in the 64-bit SDK tools such as the linker.