- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I am migrating my CVF project to IVF. When I complie the source codes I got the following error message:
Testproject error LNK2019: unresolved external symbol _deletemenuqq referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __QWINSetAboutString referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __f_getwindowconfig referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __f_setwindowconfig referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __wggetactiveunit referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __initializefonts referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __initializefonts
Testproject error LNK2019: unresolved external symbol __setcolor referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __setcolor
Testproject error LNK2019: unresolved external symbol __rectangle referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __rectangle
Testproject error LNK2019: unresolved external symbol __floodfill referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __floodfill
Testproject error LNK2019: unresolved external symbol __setviewport referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __setviewport
Testproject error LNK2019: unresolved external symbol __f_moveto referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __f_moveto
Testproject error LNK2019: unresolved external symbol __f_setmessageqq referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __wgsetactiveunit referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __ellipse referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __f_setfont referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __setgtextrotation referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __f_outgtext referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __QWINSetAboutString referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __f_getwindowconfig referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __f_setwindowconfig referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __wggetactiveunit referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __initializefonts referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __initializefonts
Testproject error LNK2019: unresolved external symbol __setcolor referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __setcolor
Testproject error LNK2019: unresolved external symbol __rectangle referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __rectangle
Testproject error LNK2019: unresolved external symbol __floodfill referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __floodfill
Testproject error LNK2019: unresolved external symbol __setviewport referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __setviewport
Testproject error LNK2019: unresolved external symbol __f_moveto referenced in function _MAIN__
Testproject error LNK2001: unresolved external symbol __f_moveto
Testproject error LNK2019: unresolved external symbol __f_setmessageqq referenced in function _MAIN__
Testproject error LNK2019: unresolved external symbol __wgsetactiveunit referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __ellipse referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __f_setfont referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __setgtextrotation referenced in function _SNSQ1
Testproject error LNK2019: unresolved external symbol __f_outgtext referenced in function _SNSQ1
I think the problem is I have set the following "project options" in my CVF project:
/check:bounds /compile_only /dbglibs /debug:full /libs:qwin /nologo /traceback /warn:argument_checking /warn:nofileopt /module:"Debug/" /object:"Debug/" /pdbfile:"Debug/DF60.PDB"
but don't know how to do the same thing in IVF.
On the other hand, if I change the runtime libraryfrom "single threaded" to "debug quickwin" in IVF,the project can be compiled without any problem. But when Istep throughthe followingline in the code in the debug mode,
write(*,*)'something'
I got a severe error as follows:
forrtl: severe (157): Program Exception - access violation
Any idea?
Thanks.
xxwxxw
Link Copied
9 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like you're not linking into the QuickWin library. If you're using the IDE, it's under "property pages => fortran => libraries", using the entry for "runtime library".
The command line option is, according to the compiler documentation,
/libs:qwin
And you need to include the USE IFQWIN statement.
The command line option is, according to the compiler documentation,
/libs:qwin
And you need to include the USE IFQWIN statement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi,emc
Thanks, after using theQuickWin library, the project can be compiled now. Butitstill has the problem, when Istep throughthe followingline in the code in the debug mode,
write(*,*)'something'
Asevere error as follows:
forrtl: severe (157): Program Exception - access violation
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please attach a test case (zip file of your project) to a problem report at Intel Premier Support. We'll take a look.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Steve
I can not log in the Intel Premier Support. I don't why. Is there any other place or email I can report the error? Thanks.
xxw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You need to have registered your serial number at the Intel Registration Center. This is where you'll get a logon ID for Intel Premier Support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think mixing console output and quickwin is a no-no.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's not what is happening here. In QuickWin, writes to units normally associated with the console are instead directed to the QuickWin window. That's one of the nice things about QuickWin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
I have reported the problem at Intel Premier Support. The issue number is 325064. Please help me to check that. Thanks a lot.
xiaowei
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for sending the project. I think that what you did was create a new project rather than use the "Extract Compaq Visual Fortran Project Items" wizard, and you initially selected a Console application when you wanted QuickWin instead.
In trying to correct this, you properly changed the run-time library type to QuickWin but missed that you also needed to change the Linker..System..Subsystem property from Console to Windows. When I do that with your project, the WRITE is ok.
In trying to correct this, you properly changed the run-time library type to QuickWin but missed that you also needed to change the Linker..System..Subsystem property from Console to Windows. When I do that with your project, the WRITE is ok.

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