- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
I do the compilation with ifort like this: ifort file1.f90 file2.F90 file3.f90 /exe:program.exe
Output:
Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 15.0.7.287 Build 2016051
File2.F90(793): remark #8291: Recommended relationship between field width 'W' and the number of fractional digits 'D' in this edit descriptor is 'W>=D+7'.
No error during compilation, the .obj files are created, but the exe file is not created, probably due to an error during link
The problem: the link is done in a new shell window that closes immediately after, so it is not possible to see the messages. I just can see a command window blinking but it is too quick to read something.
I also tried to launch a link command beginning by start: start Link xx.obj
Or finishing by /K: Link xx.obj /K
But without success
Any idea to know what is wrong ?
Thank you
Remark: Compilation with visual studio is OK:
1>------ Rebuild All started: Project: Verifications, Configuration: Debug Win32 ------
1>Deleting intermediate files and output files for project 'Verifications', configuration 'Debug|Win32'.
1>Compiling with Intel(R) Visual Fortran Compiler XE 15.0.7.287 [IA-32]...
1>file2.F90(793): remark #8291: Recommended relationship between field width 'W' and the number of fractional digits 'D' in this edit descriptor is 'W>=D+7'.
1>Linking...
1>Embedding manifest...
1>Build log written to file://c:\user\visual studio 2015\projects\verifications\Verifications\Debug\BuildLog.htm
1>Verifications - 0 error(s), 0 warning(s)
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One thing - /VERBOSE is a linker option, not an ifort option. If you want to use it on the ifort command line, put it at the end and precede it with /link. For example:
ifort example.f90 /link /verbose
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Steve
I tried “ifort example.f90 /link /verbose” , it gives a lot of information but it is not possible to read it or redirect to a file, always for the same reason.
When I do do the link /? Command, there is no version indicated, here is what I get , and the last ENTER closes the window so I don’t see the /verbose option
usage: LINK [options] [files] [@commandfile]
options:
/ALIGN:#
/ALLOWBIND[:NO]
/ALLOWISOLATION[:NO]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Clutching at straws here: check the "Layout" setting of CMD.EXE. Some of the symptoms that you described suggested to me that, perhaps, the "height" property of the screen buffer size under "Layout" may have been set to a rather low value. I usually set that value to about 1000.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
"for full path to link.exe , i will try". Did you? what happened the same?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have tried the full path to link.exe , it is the same.
Mecej4 (check the "Layout" setting of CMD.EXE) : I don’t know how to do that.
- 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
Well if your get the same result from a full path run then that rules out many things. You are only left with windows settings, environment and registry settings influencing the run. But I have no clue as to the actual cause.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
I found someone who had the same problem in 2012.
On my side the problem was solved by a complete re-installation of the compiler.
Pierre

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »