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

Modules directory can't be opened

dajum
Novice
827 Views

Hi,

I have a project that builds fine in the Release mode. But it won't in Debug mode. I think the settings are identical ( except for directory names etc.). We are using 10.0.027 in VS2005. There are a lot of modules in the project. If we do a clean and build. The first pass gets a bunch of errors that it couldn't find some modules, mostly because of the order it compiles the sources. All of the modules have been created after the first build. A second build then gets 1 error and an abort and it says 2 errors. The error is "Error in opening directory for generated module interfaces: procesproces___Win32_Debug"

It is interesting to note that the directory we have listed is actually ....procesproces___Win32_Debug. which it has no trouble putting the .mod files in during the first build. Note that the release build has the same .... in the directory used for intermediate and output files. Why the error doesn't list the .... is puzzling. Any help on how we can get a release build to work would be appreciated.

Thanks,

Dave

0 Kudos
6 Replies
Steven_L_Intel1
Employee
827 Views
There's not enough information here to help you. I suggest that you submit a support request to Intel Premier Support and attach a ZIP of your project so that we can take a look.
0 Kudos
dajum
Novice
827 Views

Unfortunately I don't think we can send out the source code for this project. Can you comment on why the error message doesn't include the complete relative path name specified? I find that part most disturbing. Also why would not be able to open a directory?

Thanks,

Dave

0 Kudos
Steven_L_Intel1
Employee
827 Views
How about this. On the project property page, go to Fortran > Command Line. Copy the "All Options" text listed for the Debug configuration and post it here. Repeat for the Release configuration.

I am also puzzled by your comment that it did not build things in the right order. My experience is that this is usually caused by circular dependencies among the source files.
0 Kudos
dajum
Novice
827 Views

Here is the requested info. Thanks for your help.

Debug:
/nologo /Zi /Od /gen-interfaces /free /warn:interfaces /iface:cref /iface:mixed_str_len_arg /module:"....procesproces___Win32_Debug" /object:"....procesproces___Win32_Debug" /traceback /check:bounds /libs:static /threads /dbglibs /c

Release:
/nologo /O3 /free /iface:cref /iface:mixed_str_len_arg /module:"....procesproces___Win32_Release" /object:"....procesproces___Win32_Release" /traceback /libs:static /threads /c


plus additional Options (for both):
/names:lowercase

0 Kudos
Steven_L_Intel1
Employee
827 Views
In general, I don't like to direct the module/object output of one project into the intermediate folder of another project, as those files will get wiped out when the other project is rebuilt. This may be part of what you are seeing. I notice that there is no /include specification to also include this other folder - perhap you can try that?

This appears to be related to the gemerated interface checking. You can turn that off in the Debug configuration under Diagnostics. There are two settings, one for generating interfaces and the other for checking them. Set them both to No.
0 Kudos
dajum
Novice
827 Views

Setting both generating interfaces and checking them to No seems to have fixed the problem.

Thanks for your help!

0 Kudos
Reply