- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can I call a DLL created by IVF from a C DLL created by MS VC++ 2003 ? I am getting error messages like:
dii2vbas error LNK2019: unresolved external symbol _f_powdi referenced in function _DENSTY
dii2vbas error LNK2001: unresolved external symbol _for_write_seq_fmt
dii2vbas error LNK2001: unresolved external symbol _for_write_seq_fmt_xmit
dii2vbas error LNK2019: unresolved external symbol _for_write_int_fmt referenced in function _INITIALIZEENTHALPYBASE
Thanks,
Lynn
dii2vbas error LNK2019: unresolved external symbol _f_powdi referenced in function _DENSTY
dii2vbas error LNK2001: unresolved external symbol _for_write_seq_fmt
dii2vbas error LNK2001: unresolved external symbol _for_write_seq_fmt_xmit
dii2vbas error LNK2019: unresolved external symbol _for_write_int_fmt referenced in function _INITIALIZEENTHALPYBASE
Thanks,
Lynn
Link Copied
7 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Certainly you can, but from the messages you cite, it doesn't look as if that's what you're doing. Rather, it seems you're linking to an object or static library. If you want to do that, you need to add the path to the Intel Fortran LIB folder to the VC++ Directories list for libraries.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I added "C:Program FilesIntelFortrancompiler80IA32LIB" to the library directory list for C DLL project but this did not help at all.
Thanks,
Lynn
Thanks,
Lynn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Assuming that you are linking in a static .LIB and not a DLL, which is what it looks like - you need to rebuild your library with the following property changed.. Intel Fortran..Libraries..Disable OBJCOMMENT Lines..No.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am linking in a library for a fortran created DLL. I am not linking in a static library. This C based DLL calling the fortran based DLL only has one c source file in it.
That property was set to No already by the way. I do not remember doing it so it must be the default.
And, I am using the Multithread DLL runtime library.
I am beginning to think that IVF is not ready for large mixed code fortran and c programs. The problems that I have had are simply amazing.
Thanks,
Lynn McGuire
That property was set to No already by the way. I do not remember doing it so it must be the default.
And, I am using the Multithread DLL runtime library.
I am beginning to think that IVF is not ready for large mixed code fortran and c programs. The problems that I have had are simply amazing.
Thanks,
Lynn McGuire
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am sure it is something simple, but your description of the project does not match the symptoms you are seeing. If you were linking in an export library, you would not be seeing references to Fortran run-time routines.
At this point, I would ask that you create a ZIP archive of the project and attach it to a support request sent to Intel Premier Support - ask that it be assigned to Steve Lionel. I'll be glad to look at it further.
IVF works well with mixed-language applications.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Steve,
I wish I could zip up the whole thing and email it to you but our source code is extremely and highly proprietary.
I am going to try to reduce the number of source code modules before I give up. I suspect that I am having a problem creating the fortran DLL with 4,000 source code modules. I can reduce this down to a 100 source code modules and see if that works any better.
Thanks,
Lynn McGuire
I wish I could zip up the whole thing and email it to you but our source code is extremely and highly proprietary.
I am going to try to reduce the number of source code modules before I give up. I suspect that I am having a problem creating the fortran DLL with 4,000 source code modules. I can reduce this down to a 100 source code modules and see if that works any better.
Thanks,
Lynn McGuire
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How about this - can you send me the .vfproj and .sln files and the outputlog.txt from the Debug or Release folder? No source code (or object code) involved. Please do it through Premier Support.

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