Can not link - unresolved external _GETENVQQ

Wesley_G_ · ‎01-16-2006

I'm having trouble linking......

Have ported this over from CVF, it is a FORTRAN routine combined with C.

Here's a snipit......

Code:

      SUBROUTINE  INPUT_FILES                                               
      USE DFPORT,  ONLY: GETCWD, STAT
	USE DFLIB	!CEA USED FOR GETTING ENVIRONMENT VARIABLES
      USE IFPORT !CEA used for getenvqq to get hve environment setting.
      USE IFCORE

      IMPLICIT  NONE
      CHARACTER(80) HVESYS, CEA_FILE

      INTEGER(4) LENVAR		
      LENVAR = GETENVQQ('HVESYSFILES', HVESYS)

Linker saysunresolved external,_GETENVQQ.....

Any suggestions??

Thx,

W

Steven_L_Intel1 · ‎01-16-2006

Is this a Fortran library and a C executable project? In the Fortran project, change the property Fortran..Libraries..Disable default library search rules to No. In Tools..Options..Projects..VC++ Directories, add the Intel Fortran /lib folder to the list of library directories.

Wesley_G_ · ‎01-17-2006

That had no effect.

When I comment out the line for GETENVQQ, it links fine.....so I think its finding the libraries and such........but I tried what you said....no change though.

W

Steven_L_Intel1 · ‎01-17-2006

I am confused - what compiler are you using? You can't be using CVF if you have USE IFCORE in there. What Fortran compilation options are you using?

Message Edited by Steve_Lionel on 01-17-2006 09:23 AM

Steven_L_Intel1 · ‎01-17-2006

No, it is not finding the proper libraries.

Create a ZIP of your solution and send it to Intel Premier Support along with a description of the problem. We'll take a look.

Wesley_G_ · ‎01-17-2006

What all do you need?? Do you need the special library that I'm linking to??

Where do I send it??

Contact me directly please.....you have my e-mail, right??

W

Steven_L_Intel1 · ‎01-17-2006

Please see here for instructions as to how to register for and contact support. I don't think the special library is needed to investigate this, though it would help if the project was buildable. It would be best to have the entire "solution", including sources, project files, and build logs from a failed attempt.