https://community.intel.com/t5/Software-Archive/unresolved-externals/m-p/970527#M23802 Tom,<BR /><BR />You've been getting help from us via vf-support - it would be best if you continued that way.<BR /><BR />/nodefaultlib is almost always the wrong thing to use - unfortunately, the MS linker suggests that. Take out /nodefaultlib and if you still have problems, write us at vf-support.<BR /><BR />Steve Fri, 19 Oct 2001 04:42:40 GMT Steven_L_Intel1 2001-10-19T04:42:40Z https://community.intel.com/t5/Software-Archive/unresolved-externals/m-p/970526#M23801 After having battled MCLS and solved it with the nodefaultlib switch. I have come up with new errors. Incidentally, I had tried giving a full path to libc.lib and the nodefaultlib switch did not work. Only when I just used libc.lib did the nodefaultlib switch work. The new errors I now face are unresolved externals that did not show up before. They are: <BR /> <BR />Linking... <BR />libci.lib(filebuf.obj) : error LNK2001: unresolved external symbol ___pioinfo <BR />dfor.lib(intrin.obj) : error LNK2001: unresolved external symbol ___fastflag <BR />dfor.lib(intrini.obj) : error LNK2001: unresolved external symbol ___fastflag <BR />dfor.lib(for_m_qqs.obj) : error LNK2001: unresolved external symbol _errno <BR />dfor.lib(for_portlib.obj) : error LNK2001: unresolved external symbol _errno <BR />dfor.lib(for_diags.obj) : error LNK2001: unresolved external symbol __sys_nerr <BR />dfor.lib(for_io_util.obj) : error LNK2001: unresolved external symbol __pctype <BR />dfor.lib(for_init.obj) : error LNK2001: unresolved external symbol __pctype <BR />dfor.lib(for_io_util.obj) : error LNK2001: unresolved external symbol ___mb_cur_max <BR />dfor.lib(for_init.obj) : error LNK2001: unresolved external symbol ___mb_cur_max <BR />dfor.lib(for_init.obj) : error LNK2001: unresolved external symbol ___argv <BR />dfor.lib(for_init.obj) : error LNK2001: unresolved external symbol ___argc <BR />dfor.lib(for_init.obj) : error LNK2001: unresolved external symbol __pxcptinfoptrs <BR /> <BR />These look like c routines. Did I loose them by ignoring libc.lib? This is a mixed fortran/c program. Should I have ignored msvcrt.lib instead? <BR /> <BR />Tom Fri, 19 Oct 2001 01:49:45 GMT https://community.intel.com/t5/Software-Archive/unresolved-externals/m-p/970526#M23801 Intel_C_Intel 2001-10-19T01:49:45Z https://community.intel.com/t5/Software-Archive/unresolved-externals/m-p/970527#M23802 Tom,<BR /><BR />You've been getting help from us via vf-support - it would be best if you continued that way.<BR /><BR />/nodefaultlib is almost always the wrong thing to use - unfortunately, the MS linker suggests that. Take out /nodefaultlib and if you still have problems, write us at vf-support.<BR /><BR />Steve Fri, 19 Oct 2001 04:42:40 GMT https://community.intel.com/t5/Software-Archive/unresolved-externals/m-p/970527#M23802 Steven_L_Intel1 2001-10-19T04:42:40Z https://community.intel.com/t5/Software-Archive/unresolved-externals/m-p/970528#M23803 Hi, Tom: <BR /> <BR />I'm also using fortran/c program, and encoutered a huge problem. I'm wondering if I could get some advices from you since it seems you're more experienced in this area. <BR /> <BR />I use a Fortran main program(f_main) to call a c subroutine(c_sub). In the c subroutine, functions defined in a self-made user.lib are used. <BR /> <BR />The error is: Linking... f_main.obj: error LNK2001: unresolved external symbol _***(user.lib). <BR /> <BR />Any tips? <BR /> <BR />In addition, in the reply Steven posted, he mentioned vf-support. I wonder what's that mean, and how I can get help from it. <BR /> <BR />Many thanks! <BR /> <BR />Jenny Zhen Wed, 31 Oct 2001 07:34:47 GMT https://community.intel.com/t5/Software-Archive/unresolved-externals/m-p/970528#M23803 Intel_C_Intel 2001-10-31T07:34:47Z