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

fftpack5

cgerdb
Beginner
959 Views
I am having problems to compile fftpack5

http://people.sc.fsu.edu/~burkardt/f77_src/fftpack5/fftpack5.html

Visual Fortran give error #6633 when it used within Visual Studio 2003 in 32bit XP or 2008 in 64bit XP. It complains type mismatch between complex and real arrays in subroutine calls.

What I cannot understand is that the source can be compiled by command ifort in a console window!

Please help!
0 Kudos
1 Solution
Steven_L_Intel1
Employee
959 Views

There are a number of diagnostic options enabled by default in Visual Studio which are not on the command line. /warn:interface is one of these and this is what is triggering the error. It is finding a real error in the program but one that was deliberate, I am guessing, on the part of the developers.

In Visual Studio, go to the Fortran > Diagnostics property page and turn off "Check routine interfaces".

View solution in original post

0 Kudos
2 Replies
Steven_L_Intel1
Employee
960 Views

There are a number of diagnostic options enabled by default in Visual Studio which are not on the command line. /warn:interface is one of these and this is what is triggering the error. It is finding a real error in the program but one that was deliberate, I am guessing, on the part of the developers.

In Visual Studio, go to the Fortran > Diagnostics property page and turn off "Check routine interfaces".
0 Kudos
cgerdb
Beginner
959 Views

There are a number of diagnostic options enabled by default in Visual Studio which are not on the command line. /warn:interface is one of these and this is what is triggering the error. It is finding a real error in the program but one that was deliberate, I am guessing, on the part of the developers.

In Visual Studio, go to the Fortran > Diagnostics property page and turn off "Check routine interfaces".
Hi! Steve,

You answer with lighning speed. Your suggestion solved the problem.

Thanks!
0 Kudos
Reply