Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
29302 Discussions

Declaration conflicts with previous declaration on first line

DavidWhite
Valued Contributor II
962 Views
How can I get a declaration conflicts with previous declaration on the first line of code? ...


Build Log
Build started: Project: TestBayer, Configuration: Debug|Win32

Output
Deleting intermediate files and output files for project 'TestBayer', configuration 'Debug|Win32'.
Compiling with Intel Visual Fortran 11.0.074 [IA-32]...
ifort /nologo /debug:full /Od /gen-interfaces /debug-parameters:used /warn:truncated_source /warn:noalignments /warn:nouncalled /warn:interfaces /Qauto /Qzero /Qfp-stack-check /module:"..\modules" /object:"..\intermed/" /traceback /check:bounds /check:uninit /check:arg_temp_created /libs:static /threads /dbglibs /c /Qvc8 /Qlocation,link,"C:\Program Files\Microsoft Visual Studio 8\VC\bin" "C:\Dev\TestBayer\testdll.for"
C:\Dev\TestBayer\testdll.for(1): error #5508: Declaration of routine 'TESTDLL' conflicts with a previous declaration
PROGRAM TESTDLL
--------------^
compilation aborted for C:\Dev\TestBayer\testdll.for (code 1)


TestBayer - 2 error(s), 0 warning(s)


0 Kudos
4 Replies
anthonyrichards
New Contributor III
962 Views
Do you have a function or subroutine called TESTDLL somewhere? (...which will clash with the Program TESTDLL name)

0 Kudos
rreis
New Contributor I
962 Views
If I'm not mistaken, a label should be unique... So having "PROGRAM TESTDLL" and "subroutine testdll" will cause a conflict (testdll is repeated).
0 Kudos
Steven_L_Intel1
Employee
962 Views
This is a bug in 11.0.074 specifically. It will be fixed in the next update. As a workaround, turn off Diagnostics > Check Routine Interfaces
0 Kudos
DavidWhite
Valued Contributor II
962 Views
This is a bug in 11.0.074 specifically. It will be fixed in the next update. As a workaround, turn off Diagnostics > Check Routine Interfaces

Gald (!) to see that I'm not losing my Fortran marbles.
0 Kudos
Reply