error #5508: "This is in conflict with a previous declaration."

[WSinc]

When I installed it, I got an error I have never seen before in this project.

I didn't change ANY code.
It gives me an error #5508:
"This is in conflict with a previous declaration."

This was the only declaration.
A clean and rebuild does NOT work.

Now I can't compile my project at all.

[Ron_Green]

bug report is DPD200120387

I'll keep everyone posted on progress.

ron

[Robinson__Donald]

I have an MS Visual studio 2005 solution with one Fortran and one C project. I can clean and build Debug and Release versions with Version 11.0.061, with these statements (/flags shown in UI) in the vfproj file:

Interfaces="true" (/gen-interfaces)
WarnInterfaces="true" (/warn:interfaces)

When I perform a clean and build with Version 11.0.074 with the same 2 interface options, I obtain the following error:

2>F:Visual Studio 2005FVSECbasesrcstats.for(1): error #5508: Declaration of routine 'STATS' conflicts with a previous declaration

The error can occur with different routines (not just 'STATS').

[Ron_Green]

Yes, the same bug. The name of the subroutine (symbol) can be anything.

We have 2 simple reproducers in our bug report and have raised this to the highest criticality.

ron

[Ron_Green]

All,

I've taken the liberty to change the thread title to make it easier for others to discover (I think we'll see more users with this issue).

thanks

ron

[davenport-nswcpc]

I applied this fix and the error has gone away......... I suppose until something else goes wrong. Thank you brian for posting that.

Really, if this forum wasn't soooooooooo slooooooow I'd come here more often and not just when something bad happens.

ardavenport



Quoting - bmchenry

turn off the 'Generate Interface Blocks' option of

Project menu->"your project" Properties->Fortran->Diagnostic->Generate Interface Blocks

i was experiencing similar errors and eliminated them by this simple change.

brian

[onkelhotte]

When will Intel releasean update on 11.0.072? My license expires this month and it would be unfortunate to miss the fix on this issue...

Markus

[Steven_L_Intel1]

The next update will be 11.1, out later this month, and it will include the fix for this. If your support expires in June, you'll be able to install the initial 11.1.

[Ron_Green]

Quoting - donrobinson

I have an MS Visual studio 2005 solution with one Fortran and one C project. I can clean and build Debug and Release versions with Version 11.0.061, with these statements (/flags shown in UI) in the vfproj file:

Interfaces="true" (/gen-interfaces)
WarnInterfaces="true" (/warn:interfaces)

When I perform a clean and build with Version 11.0.074 with the same 2 interface options, I obtain the following error:

2>F:Visual Studio 2005FVSECbasesrcstats.for(1): error #5508: Declaration of routine 'STATS' conflicts with a previous declaration

The error can occur with different routines (not just 'STATS').

Just to close this out - this bug was fixed in the 11.1 compilers and in the most current 11.0 compilers (download from https://registrationcenter.intel.com

ron

[Stuart_M_]

Quoting - onkelhotte

When will Intel releasean update on 11.0.072? My license expires this month and it would be unfortunate to miss the fix on this issue...

Markus

Hi Steve

I have hit this bug but my license expired in April. Do I have to buy a new license in order to download the fix, even though the version I have downloaded came with the bug? Seems to be, but all seems to be a bit unfair, so just wanted to check with someone a little more in-the-know.

Thanks man

[Steven_L_Intel1]

Yes, or you could back down to an earlier 11.0 version that didn't have the bug (I think it was only in that one version.)

[onkelhotte]

Quoting - stubaan

Hi Steve

I have hit this bug but my license expired in April. Do I have to buy a new license in order to download the fix, even though the version I have downloaded came with the bug? Seems to be, but all seems to be a bit unfair, so just wanted to check with someone a little more in-the-know.

Thanks man

Steve, had Intel thought about releasing the compiler and the VS Integration seperatly? For example, the compilerneeds a valid license (just like now) and the integration comes for free?

I know, that this bug is compiler related, but there were (and maybe are and will be)Integration bugsand buying a new license only for editing reasons when you dont need the new compiler features is not fair (just my $0.02).

Markus

[Steven_L_Intel1]

No, we haven't considered that and probably won't. Our packaging and testing is complex enough as it is.