- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi:
I recently re-installed Intel Fortran Compiler (Integration for Microsoft Visual Studio 2005, 10.1.4159) in my laptop after a Windows Vista meltdown.
My old installation run smoothly. In the new installation, I can compile and run a simple "hello world" program.
However, when I call the IMSL library, I can compile but, at running time, I get the message
application failed initialize properly (0xc0000142)
I saw in the forum an old thread discussing this issue, but the conversation ended without a final resolution.
My options>fortran>executables reads (after the other lines):
C:Program FilesIntelCompilerFortran10.1.024IA32Lib
C:Program FilesIntelCompilerFortran10.1.024IA32Include
C:Program FilesVNIimslfnl600IA32Lib
C:Program FilesVNIimslfnl600IA32includeDLL
C:Program FilesVNIimslfnl600IA32includeSTATIC
Any help will be most useful. I have been struggling with this problem for two days
J
I recently re-installed Intel Fortran Compiler (Integration for Microsoft Visual Studio 2005, 10.1.4159) in my laptop after a Windows Vista meltdown.
My old installation run smoothly. In the new installation, I can compile and run a simple "hello world" program.
However, when I call the IMSL library, I can compile but, at running time, I get the message
application failed initialize properly (0xc0000142)
I saw in the forum an old thread discussing this issue, but the conversation ended without a final resolution.
My options>fortran>executables reads (after the other lines):
C:Program FilesIntelCompilerFortran10.1.024IA32Lib
C:Program FilesIntelCompilerFortran10.1.024IA32Include
C:Program FilesVNIimslfnl600IA32Lib
C:Program FilesVNIimslfnl600IA32includeDLL
C:Program FilesVNIimslfnl600IA32includeSTATIC
Any help will be most useful. I have been struggling with this problem for two days
J
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The list you show above is not used when applications are run - that's just for building. The key is what is the value of the PATH environment variable.
Does it work if you link to the static (not DLL) IMSL libraries?
Does it work if you link to the static (not DLL) IMSL libraries?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi:
I copied the information relating the executables because I read in the help section "Specifying Path, Library, and Include Directories":
I copied the information relating the executables because I read in the help section "Specifying Path, Library, and Include Directories":
"Executables: the directories to be searched for executable files. (Works like the PATH environment variable.)" and in the old thread there was a discussion about PATH.
With the static call:
include 'link_fnl_static.h'
I cannot compile. It was next on my list of problems, but less important because I prefer the dll. Can these two problems be related?
Thanks
J
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What problem do you get when you use link_fnl_static.h? If it is a series of undefined references from the linker, add this line:
!DEC$ OBJCOMMENT LIB:'libguide.lib'
!DEC$ OBJCOMMENT LIB:'libguide.lib'

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page