- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What would cause USE IFPORT to cause an error
astap.for(3780): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [IFPORT]
USE IFPORT
------------^
ifport.mod is in
C:\Program Files (x86)\Intel\Compiler\11.0\074\fortran\include\ia32
and
C:\Program Files (x86)\Intel\Compiler\11.0\074\fortran\include\intel64
which is where it's supposed to be, I think.
Is there some setting or environment variable that didn't get set properly on install?
astap.for(3780): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [IFPORT]
USE IFPORT
------------^
ifport.mod is in
C:\Program Files (x86)\Intel\Compiler\11.0\074\fortran\include\ia32
and
C:\Program Files (x86)\Intel\Compiler\11.0\074\fortran\include\intel64
which is where it's supposed to be, I think.
Is there some setting or environment variable that didn't get set properly on install?
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In what environment are you doing the compile? Command line? If so, did you use the Build Environment shortcut to start the command prompt session? You should not have to do anything special to make this work, other than be in the right environment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Removing the /INCREMENTAL:NO switch from the compile and link command gets rid error finding the IFPORT module. But I don't understand how they are related. Can you explain this fixes the error and what effect it might have on getting tracebacks from a run-time error?
Thanks,
Dave
Removing the /INCREMENTAL:NO switch from the compile and link command gets rid error finding the IFPORT module. But I don't understand how they are related. Can you explain this fixes the error and what effect it might have on getting tracebacks from a run-time error?
Thanks,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
/INCREMENTAL is a linker option - it is ignored by the compiler (with a warning message.) I cannot imagine how it could have an effect on the USE. It will have an effect on traceback, when used as a linker option, since traceback does not work when an executable is linked incrementally.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah, I keep forgetting that many switches are case-sensitive. /I is a way to specify the INCLUDE path, so what you did was specify a path of "NCREMENTAL:NO". Because this is not valid syntax for a file path, the compiler gets confused and gives an error. Perhaps it would be better if it continued with other folders in the INCLUDE path.
If you want to specify linker options, precede them with /link - that will tell ifort to pass everything after /link to the linker.
If you want to specify linker options, precede them with /link - that will tell ifort to pass everything after /link to the linker.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page