Previous declaration error

[Stephen_Painchaud]

I get the following compile time error:

1>Compiling with Intel Visual Fortran 11.0.074 [IA-32]...
1>asbne.f90
1>D:\Documents and Settings\PAINSTEV\My Documents\Visual Studio 2005\Projects\mpr_apr3d\asbne.f90(2): error #5508: Declaration of routine 'IUSVUOAKNB' conflicts with a previous declaration


If I serch for the subroutine name I get only 2 references.

Find all "IUSVUOAKNB", Subfolders, Keep modified files open, Find Results 1, "Entire Solution"
D:\Documents and Settings\PAINSTEV\My Documents\Visual Studio 2005\Projects\mpr_apr3d\asbne.f90(2):SUBROUTINE iusvuoaknb(inpStyle, debug, pauseflag)
D:\Documents and Settings\PAINSTEV\My Documents\Visual Studio 2005\Projects\mpr_apr3d\prmod3d.f(167): CALL iusvuoaknb(inpStyle, debug, pauseflag)
Matching lines: 2 Matching files: 2 Total files searched: 45


I have checked the arguments, they are the same in the calling routine and the subroutine.

CHARACTER*10 inpStyle
LOGICAL debug
LOGICAL pauseflag


I don't understand how I can have a previous declaration. I have been using this subroutine for over a year in this solution. As you can see from the strange name it has, I randomly changed the original name so it could not conflict with anything in my solution. This is one of two subroutines that is giving me this error message. I have been using the 2nd routine for over a year also.

If I remove the file from the solution I get an unresolved external symbol when linking. If I add a few letter to just the subroutine name I get the same error:

Compiling with Intel Visual Fortran 11.0.074 [IA-32]...
asbne.f90
D:\Documents and Settings\PAINSTEV\My Documents\Visual Studio 2005\Projects\mpr_apr3d\asbne.f90(1): error #5508: Declaration of routine 'IUSVUOAKNBXSGAGA' conflicts with a previous declaration
compilation aborted for D:\Documents and Settings\PAINSTEV\My Documents\Visual Studio 2005\Projects\mpr_apr3d\asbne.f90 (code 1)

I don't think I have a previous declaration. Any ideas on what the real source of the error might be? I am using VS2005 with IVF11.

[Steven_L_Intel1 · Accepted solution]

This is a bug in 11.0.074 (only). You can revert back to 11.0.072 or turn off "Check Routine Interfaces" under Fortran > Diagnostics.

[muppets]

Hi,

is it possible that this bug isn't yetfixed in 11.1.054?

Many greetings

Eberhard

[Steven_L_Intel1]

That bug is fixed in 11.1.054. If you have an example that shows this error message, please post or attach it so we can take a look.

[muppets]

Dear Steve,

please have a look at this program:

program test

implicit none

double precision x, y, z

x = 1d0
y = 2d0 * x
z = 2d0 * y

call sub(x, y, z)

end program test

subroutine sub(a, b, c)

implicit none

double precision a, b
integer c

a = b + c

end subroutine

You will receive the error message "error #6633: The type of the actual argument differs from the type of the dummy argument. O:\TWPr\bf11054\main.f90 11" . This is of course absolutely correct.

You will correct:

program test

implicit none

double precision x, y, z

x = 1d0
y = 2d0 * x
z = 2d0 * y

call sub(x, y, z)

end program test

subroutine sub(a, b, c)

implicit none

double precision a, b, c

a = b + c

end subroutine

There should be no error message any more, but we receive:
"error #7001: Error in creating the compiled module file. [SUB__genmod] O:\TWPr\bf11054\main.f90 15"

Switching off "Generate Interface Blocks" fixes the problem (after a restart of Visual Studio), but switching off this option also switches off interface checking unfortunately.

Best regards

Eberhard

[Steven_L_Intel1]

Well, this is a very different problem than the one this thread was started for. That said, I can't reproduce the problem with the current compiler (11.1.065, Update 6). The problem you have here seems to be one that is environment-related. I suggest deleting all of the __genmod.* files and trying again.

[muppets]

Steve, you are totally right.

Meanwhile I know a little bit more. The mentioned behaviour occurs only if the project is stored on a net drive of a novell network. Storing it locally or storing it on a net drive of a windows network it works fine.

I will report.

Thank you very much

Eberhard