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

problems converting multi lang proj from CVF to IVF 91.

Malcolm_C_
Beginner
472 Views
I'm converting a large multilanguage (fortran, C, C++)project from CVF 6.6 to IVF 9.1. I've managed to successfully compile all modules and source filesin the project, without warnings,and am now experiencing a bunch of link problems.

In the solution specification the following properties are set:

Fortran:
External Procedures:
Calling Convention: Default
Name Case Interpretation: Default
String Length Argument Passing: After All Arguments
Append Underscore to External Names: No
Generate Inerface Blocks: No.

Linker:
Additional Dendencies::
ws2_32.lib kernel32.lib user32.lib gdi32.lib comdlg32.lib lz32.lib comctl32.lib advapi32.lib winmm.lib
... a bunch of project specific static libs...

Ignore All Default Libraries: NO
Ignore specifi Library: LIBC;LIBCD;LIBCMT

I'm using modules IFCOM, IFAUTO, IFLOGM in many of the fortran components of the project.

In spite of compiling withoutfortran or C/C++ errors or warnings I get the following link error:


error LNK2001: unresolved external symbol <<>>

for calls to everyCOM AUTO of DLG functions/sbr's. Note that an underbar '_' is prepended to all unresolved external symbol names in the LINK2001 msg.

Can someonesuggestlikely screwups inmy project/solution spec?

Thanks

0 Kudos
2 Replies
Malcolm_C_
Beginner
472 Views
Quoting - capel@anl.gov
I'm converting a large multilanguage (fortran, C, C++)project from CVF 6.6 to IVF 9.1. I've managed to successfully compile all modules and source filesin the project, without warnings,and am now experiencing a bunch of link problems.

In the solution specification the following properties are set:

Fortran:
External Procedures:
Calling Convention: Default
Name Case Interpretation: Default
String Length Argument Passing: After All Arguments
Append Underscore to External Names: No
Generate Inerface Blocks: No.

Linker:
Additional Dendencies::
ws2_32.lib kernel32.lib user32.lib gdi32.lib comdlg32.lib lz32.lib comctl32.lib advapi32.lib winmm.lib
... a bunch of project specific static libs...

Ignore All Default Libraries: NO
Ignore specifi Library: LIBC;LIBCD;LIBCMT

I'm using modules IFCOM, IFAUTO, IFLOGM in many of the fortran components of the project.

In spite of compiling withoutfortran or C/C++ errors or warnings I get the following link error:


error LNK2001: unresolved external symbol <<>>

for calls to everyCOM AUTO of DLG functions/sbr's. Note that an underbar '_' is prepended to all unresolved external symbol names in the LINK2001 msg.

Can someonesuggestlikely screwups inmy project/solution spec?

Thanks


I forgot to mention that I'm using .net 2003 (spk 1) and MSC 7 for the C/C++ side.

0 Kudos
Malcolm_C_
Beginner
472 Views
Quoting - capel@anl.gov
I'm converting a large multilanguage (fortran, C, C++)project from CVF 6.6 to IVF 9.1. I've managed to successfully compile all modules and source filesin the project, without warnings,and am now experiencing a bunch of link problems.

In the solution specification the following properties are set:

Fortran:
External Procedures:
Calling Convention: Default
Name Case Interpretation: Default
String Length Argument Passing: After All Arguments
Append Underscore to External Names: No
Generate Inerface Blocks: No.

Linker:
Additional Dendencies::
ws2_32.lib kernel32.lib user32.lib gdi32.lib comdlg32.lib lz32.lib comctl32.lib advapi32.lib winmm.lib
... a bunch of project specific static libs...

Ignore All Default Libraries: NO
Ignore specifi Library: LIBC;LIBCD;LIBCMT

I'm using modules IFCOM, IFAUTO, IFLOGM in many of the fortran components of the project.

In spite of compiling withoutfortran or C/C++ errors or warnings I get the following link error:


error LNK2001: unresolved external symbol <<>>

for calls to everyCOM AUTO of DLG functions/sbr's. Note that an underbar '_' is prepended to all unresolved external symbol names in the LINK2001 msg.

Can someonesuggestlikely screwups inmy project/solution spec?

Thanks


Once again, I'm answering my on post. The above mentioned problems were all due to my misuse of a generic interface to AUTOSetProperty. Once I corrected this error all link errors were resolved.
0 Kudos
Reply