Fortran 10.0.027 _ia64 install problems with vs2005 and vista (64 bit)

Ian_Chivers · ‎09-20-2007

I am moving over to a 64 bit environment and have installed vs2005 and applied sp1 and sp1 for vista.

This system runs windows vista home premium 64 bit.

I then tried installing w_fc_c_10.0.027_intel64.exe

Trying to start the compiler from a dos prompt i get

Intel Fortran Compiler for applications running on Intel 64, Version 10.0.
027
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.

The specified configuration type is missing. The tools for the
configuration might not be installed.
C:Windowssystem32>

when trying from vs i get an error message about ifort not found. i've uninstalled all intel entries and reinstalled and get the same messages. i had seen a post about selecting options at install time. i did not see get these options.

any thoughts?

ian chivers

a simple c++ program (classic hello world) needless to say compiles and runs from within vs2005.

TimP · ‎09-20-2007

In addition to installing vs2005, you must install the 64-bit MSVC SDK optional component. If you can run 64-bit Microsoft C++, you have the necessary Microsoft support components for combined 64-bit C and Fortran. As an alternative, when you don't install vs2005, you can install ifort 10 with self-contained support, with no C/C++ capability.
By the way, I started to answer about Itanium, since you put ia64 in the title. I've seen plenty of questions "why doesn't Itanium compiler work on AMD?" Maybe if enough customers tell Intel marketing that meaningful terminology for x86-64 platforms would be OK, the confusion might be reduced.

Steven_L_Intel1 · ‎09-20-2007

You do not need to install the SDK optional component. You do need to make sure that Visual Studio has 64-bit compiler and tools option installed, as this is not the default for Visual Studio Professional. There is, however, a bug in version 10 that the command line support believes that you must have the PSDK.you can fix this by editing ifort.cfg to call the Visual Studio setup batch file instead. This will be fixed in a future update.