Possible INCLUDE/USE bug in IVF-11?

[longden_loo]

In building a solution for legacy code that worked properly under IVF-10, IVF-11 is complaining about a missing module file for a USE statement. It appears that 3 files are involved in the bug:

alpha.f90 contains an INCLUDE for beta.fi, which in turn has a USE for gamma.f90

Under IVF-10, I observed that gamma.f90 was compiled early in the build process, whereas in IVF-11, I don't see it compiling before the error occurs...

beta.fi(28): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [GAMMA]

All the files involved are in the same project folder, so I can't use project dependency. Although I know I can move them into different projects to get it working, the fact that it worked correctly in IVF-10 seems to imply that a single project structure isn't the problem.

My current workaround is:
1) Clean Solution
2) compile gamma.f90 by itself (rt click, compile)
3) Build Solution

... but I'd like to do it the way it used to work in IVF-10.

Is this a known bug, or is there something new I have to do in IVF-11 to make this work?

Thx, Longden

[Steven_L_Intel1]

It sounds as if the dependency analyzer in our Visual Studio integration is getting this wrong. Can you attach a ZIP of the project after a Build > Clean? If you don't want to do it here, submit it to Intel Premier Support.

[longden_loo]

Quoting - Steve Lionel (Intel)

It sounds as if the dependency analyzer in our Visual Studio integration is getting this wrong. Can you attach a ZIP of the project after a Build > Clean? If you don't want to do it here, submit it to Intel Premier Support.

I'll have to create a sanitized version, so it'll have to wait till I have some more time.

I guess I was fishing for the proverbial low hanging fruit, and hoping someone already had a solution.

Thx.

[Steven_L_Intel1]

Check to make sure you don't have a circular dependency in your USEs.