Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unresolved external symbol

Status
Not open for further replies.

ESMAEIL790

Technical User
Mar 17, 2010
3
CA

Hi everyone:
I have a huge code written in Fortran 77, and I am trying to build it by PVF (either 77 or 95) compilers. However, It complains that:
Error 1 unresolved external symbol _RUNRCGN@120 referenced in function _CALMATSCAT@68 ctscan.obj
I have already had same problems with this code, but whenever I was adding the unresolved subroutines to the source files, it would be resolved. However,this time it does not work either when I am leaving the subroutine "RUNRCGN" and its associated subroutines in the main program or separate files among source files. The RUNRCGN and all its associated subroutines and functions are available. I am wondering if there is someone with any idea to know how to deal with it. Thanks so much.
 
I don't know anything about PVF so I'm just guessing.

1) Are the routines in a separate file or in the same file?
2) Do you have the right number of parameters in the calls (RUNRCGN has 30, CALMATSCAT has 17 according to your error message)

If the routines are in separate files, have they been added to the link.
 
Sorry, you did say they were in separate files. Are you integrated with Visual Studio or does PVF have its own GUI. If you are integrated with Visual Studio, are they in the project and do they have "exclude from build" ticked?
 
xwb:

Regarding the first Q, subroutines were both available to be feed into the main program as separate files and subroutines included within the main program. However, none of them worked.
Q2. I do have the right number of parameters in call and subroutines.
In fact I recived some comments from another forum that I am to share here: In my case, since the code was written in Fortran 77 working with Unix, I had to say my developer to call them in the platform of Unix. I changed the calling convention from properties of the project from default to Unix in the PVF. then it worked.

PVF is a developer which is working with visual studio.

Thanks for your comments BTW.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top