Link Compaq Visual Fortran DLL with Intel Visual Fortran

[ekeom]

Dear All,

I have one dll compilke with Visual Compaq Fortran and would like to link it with Intel Fortran source code, but I got this errors :


1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _BINIQR referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _BININI referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _SYSIQR referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _BINSET referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _BINTFO referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _BINHED referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _INEXC4 referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _BINWRT8 referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_331_m.obj : error LNK2019: unresolved external symbol _BINCLO referenced in function _USRSUB_331_M_mp_USRSUB_331
1>usrsub_x02_m.obj : error LNK2019: unresolved external symbol _BINWRT referenced in function _USRSUB_X02_M_mp_USRSUB_X02
1>usrsub_x32_m.obj : error LNK2001: unresolved external symbol _BINWRT
1>Release\..\..\..\bin_win_32\init_xxx.exe : fatal error LNK1120: 10 unresolved externals

Note that using Visual Compaq Fortran it works normally.

Best regards,

Didace

[Jugoslav_Dujic · Accepted solution]

Quoting - ekeom

I have one dll compilke with Visual Compaq Fortran and would like to link it with Intel Fortran source code, but I got this errors :

Note that using Visual Compaq Fortran it works normally.

Different calling conventions.

There are several ways to fix it, and the fastest (if not the cleanest) is to build the VF exe with /iface:cvf. Check your documentation.

[ekeom]

Quoting - Jugoslav Dujic

Different calling conventions.

There are several ways to fix it, and the fastest (if not the cleanest) is to build the VF exe with /iface:cvf. Check your documentation.

Dear Jugoslav Dujic,

Thank you very much for your answer, it works!!!

Best regards,


Didace