https://community.intel.com/t5/Intel-Fortran-Compiler/Link-problems-for-mixed-C-FORTRAN-32bit-builds-on-64bit-machine/m-p/912640#M83797 I've got a mix of C and FORTRAN that has a C mainline, which calls routines in a FORTRAN library, which in turn calls routines that exist in a C library. I am building on an XP64 machine using IFORT 10.1.021 in visual studio. <BR /><BR />Everything works fine when building a 64bit configuration, but I'm having problems linking a 32bit configuration. In particular, all of the external subroutines/functions defined in the C library are not being resolved when the FORTRAN library is linked into the C mainline. I get a "error LNK2019 : unresolved external symbol _CLIBMETHOD referenced from function _FLIBMETHOD" when the FORTRAN library is linked into the C mainline.<BR /><BR />A dumpbin of FORTRAN library shows external dependencies on _CLIBMETHOD. A dumpbin of the C library shows symbols like _CLIBMETHOD@0.<BR /><BR />I'd thought that there was some sort of lead uderscore problem, but now that I look at the C lib symbol, I can't help but wonder if its the extra @0 that's the source of my problems...<BR /><BR />Thanks in advance for any help/advice,<BR />Steve Wed, 13 Jan 2010 15:29:02 GMT steve_reussansys_com 2010-01-13T15:29:02Z https://community.intel.com/t5/Intel-Fortran-Compiler/Link-problems-for-mixed-C-FORTRAN-32bit-builds-on-64bit-machine/m-p/912640#M83797 I've got a mix of C and FORTRAN that has a C mainline, which calls routines in a FORTRAN library, which in turn calls routines that exist in a C library. I am building on an XP64 machine using IFORT 10.1.021 in visual studio. <BR /><BR />Everything works fine when building a 64bit configuration, but I'm having problems linking a 32bit configuration. In particular, all of the external subroutines/functions defined in the C library are not being resolved when the FORTRAN library is linked into the C mainline. I get a "error LNK2019 : unresolved external symbol _CLIBMETHOD referenced from function _FLIBMETHOD" when the FORTRAN library is linked into the C mainline.<BR /><BR />A dumpbin of FORTRAN library shows external dependencies on _CLIBMETHOD. A dumpbin of the C library shows symbols like _CLIBMETHOD@0.<BR /><BR />I'd thought that there was some sort of lead uderscore problem, but now that I look at the C lib symbol, I can't help but wonder if its the extra @0 that's the source of my problems...<BR /><BR />Thanks in advance for any help/advice,<BR />Steve Wed, 13 Jan 2010 15:29:02 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/Link-problems-for-mixed-C-FORTRAN-32bit-builds-on-64bit-machine/m-p/912640#M83797 steve_reussansys_com 2010-01-13T15:29:02Z https://community.intel.com/t5/Intel-Fortran-Compiler/Link-problems-for-mixed-C-FORTRAN-32bit-builds-on-64bit-machine/m-p/912641#M83798 <DIV style="margin:0px;"></DIV> <BR />Yes, the @0 indicates that the Fortran library is built using the STDCALL calling convention. Perhaps this was a CVF project converted to Intel Fortran? <BR /><BR />Right click on the Fortran project, select Properties. Expand the property tree Fortran &gt; External Procedures. Change Calling convention to Default. Change String Length Argument Passing to "After All Arguments". Rebuild.<BR /><BR />By the way, it is Fortran, not FORTRAN.<BR /> Wed, 13 Jan 2010 17:03:26 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/Link-problems-for-mixed-C-FORTRAN-32bit-builds-on-64bit-machine/m-p/912641#M83798 Steven_L_Intel1 2010-01-13T17:03:26Z