fatal error LNK1104: cannot open file 'ifconsol.lib

[Julie_D_1]

Hello:

I have installed the 30-day trial Intel Parallel Studio XE Composer.  I also installed Microsoft Visual 12. I am new to using a compiler.  I am new at troubleshooting issues concerning computers.  I am a new beginner at using Visual C++ or fortran.  I have read other forum entries to learn about similar situations.   I have had IT support for these types of projects at school or work.  Expect, I am trying to install on my home computer with the hopes of using a compiler.  I am trying to compile a ANSYS fortran user subroutine using these products.  I keep getting the following error: LINK: fatal error LNK1104: cannot open file 'ifconsol.lib'.  I have located the file at this location: C:\\Program Files (x86)\Intel\Composer XE 2015\ compile\lib\intel64

I would like to have some success with this product.  But, so far the trial product is very hard to get configured for use.

Can someone help me with this error.

Regards,

Julie D

[mecej4]

Someone new to Intel Fortran and running compiler toolsets from the command line may find it difficult to troubleshoot integration with a package such as Ansys. Consider taking your home PC to your place of work and getting the help of your IT people.

Is your version of Ansys 32 bit or 64 bit? Which version of IFort does the Ansys documentation declare as compatible?

[Steven_L_Intel1]

I suggest starting ANSYS from the Fortran build environment command prompt. Otherwise it may not see where to find the Fortran libraries.

[mecej4]

Julie D. wrote:
ANSYS 15 requires Visual Studio 2010 SP1 (including the MS C++ compiler) and Intel Fortran 12.1 compilers.  I am not sure what version of compiler I have gotten in the 30-day trial version.

The current trial download contains Intel Fortran 15.0.2. As far as compatibility is concerned it may be more important to ensure that the "bitness" is correct -- for example, if Ansys 15 requires the 32-bit compiler, you should use that version. You cannot use the 64 bit compiler with Ansys if the latter needs the 32-bit compiler, and vice versa. That is why I asked you to state the "bitness" of your installation of Ansys.

[Julie_D_1]

hello:

I have a 64 bit computer.  I am using  ANSYS Rev 15.  According to the documentation, it requires Visual Studio 2010 SP1 (including the MS C++ compiler) and Intel FORTRAN 12.1 compilers.  I am not sure what version of fortran compiler is included in the trial version.  

The procedure is to dynamically link files or to create a stand alone executable.  The Intel 64 command prompt is used to accomplish this task.  In the file folder where the custom link files reside, I execute the the anscust.bat or ansusershared.bat.  It prompts me to answer one question before it starts the link process.  The custom fortran file is in the file folder.  When it is creating the specific object file for the fortran file, I get this error:

fatal error LNK1120: 5 unresolved externals.

I am not sure about the next steps.   But, I wonder if the visual studio is set up correctly.

Regards,

Julie D.

[mecej4]

Few of us here are Ansys users. Therefore, we have to rely on you to supply details regarding Ansys. Specifically, and this is important, is your Ansys 32-bit or 64-bit?

Secondly, we need to know the error messages that you see reported in full. In particular, what were the names of the "unresolved externals" -- all five of them?

When it is creating the specific object file for the fortran file, I get this error:...

Just for your clarification: the compiler creates object files without regard to externals. The unresolved externals messages are from the linker, not the compiler.

[Julie_D_1]

MeceJ4:

I have been following explicit instructions provided by ANSYS provide in a separate training presentation.  It does not mention anything about "bitness".  When installing ANSYS, I choose the appropriate version of the software, 64 bit because I have a 64 bit computer.  

See attached snap shot of the command prompt.  This picture of the command prompt does not show all the details to discern what the 5 external errors are. How can I see specifically what are the 5 exact external errors?  Can you give me some instructions?

 Thanks about the clarification concerning the unresolved externals messages created by the linker, not the compiler.

Regard,

Julie D.

[mecej4]

On a 64-bit computer, you can run Windows 32-bit or Windows 64-bit. On the former, you can only run 32-bit programs. On the latter, you can run both 32-bit and 64-bit programs. Thus, on your Windows-X64, you may have the 32-bit version of Ansys or you may have the 64-bit version, and you need to know which one it is.

The missing external names are clearly listed in the screenshot, enclosed between double quote marks. They are the names of routines from the C++ ostream family. These names are defined in the libcpmxx.lib and msvcpxx.lib libraries that come with Visual C++ ("xx" can be "mt", "rt", etc., depending on which specific library is to be used). The Ansys script that issued the link command should have caused one of these libraries to be searched during the link step. Beyond that, I cannot tell you what to fix since that has to be done on the Ansys side (I don't use Ansys). You can ask for help regarding this on an Ansys forum or support page.

When you report error messages, it is better to copy and paste the text from the command window than to attach an image (such as *.PNG).

[Julie_D_1]

mecej4:

I understand the importance of determining whether I installed a 32-bit version or 64- bit version of ANSYS.  I built my computer...I know I have a 64-bit computer.  I installed a 64-bit version of Windows and ANSYS.  

Any explanation or insightful comments about the error message is helpful.  The comment about the Visual C++ files...I did not know what these file were or where they came from...I will investigate further.

Thank you for all of your tips and explanations.  Every little bit helps.    

Regards,

Julie D 

[mecej4]

There is something that you can try to troubleshoot. It will not take much time, so it is not a big problem even if it fails.

Obtain the example code at http://www.math.hkbu.edu.hk/parallel/pgi/doc/pgC++_lib/stdlibcr/bas_8583.htm#Examples . Note that there are two examples in the code block. Split the code into, say, ostream1.cpp and ostream2.cpp. 

Open an Intel Fortran 64-bit command window as Steve Lionel suggested in #3. Move to the directory where you saved the two files named in the previous paragraph, and compile them with the Intel or Microsoft C++ compilers. If the compilation goes through, that is a strong indication that the problem lies in the Ansys scripts. If not, there is something amiss in your C/C++ installation and that needs to be fixed. Note that the suggested tests do not involve using Ansys at all, so it does not matter if, in the Intel Fortran 64-bit command window, the environment to run Ansys is not established. 

[Julie_D_1]

Mecej4:

Great idea!  I will do it and let you know what my findings are once complete.  Many thanks to you.

Regards,

Julie D.

[Julie_D_1]

Mecej4:

So I created the two files and compiled using the Intel 64-bit command prompt.  Both successfully compiled. So the problem lies with ANSYS.  I will investigate further with ANSYS.  Many thanks for the ideas, thoughts and any consideration on my behalf.

Julie D.

Output from command prompt:

ostream2.cpp

You are using an Intel supplied intrinsic header file with a third-party compiler.
Microsoft (R) Incremental Linker Version 11.00.60610.1
Copyright (C) Microsoft Corporation.  All rights reserved.

/out:ostream2.exe 
ostream2.obj 

ostream1.cpp
You are using an Intel supplied intrinsic header file with a third-party compiler.
Microsoft (R) Incremental Linker Version 11.00.60610.1
Copyright (C) Microsoft Corporation.  All rights reserved.

/out:ostream1.exe 
ostream1.obj