Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29427 Discussions

Fortran Error Message - Ordinal Not Found

dsmanoli
Beginner
‎03-22-2009 10:51 AM
1,001 Views
Hi,

I recently upgraded to IVF 11.0 with the IMSL library and I'm using Microsoft Visual Studio 2005.

I am trying to run a fortran program, and I am getting the following error message in a pop-up window (the window has the title "my_program.exe - Ordinal Not Found"):


The ordinal 1857 could not be located in the dynamic link library libguide40.dll.

The program compiles without any errors, so I am not sure what to do. Please let me know if you have any advice. Thanks!
0 Kudos

Link Copied

2 Replies
TimP
Honored Contributor III
‎03-22-2009 11:50 AM
1,002 Views
Unless you specify the legacy OpenMP library at link time, it would require the libiomp5 (default for 11.0 OpenMP) instead of libguide.
0 Kudos
Copy link
dsmanoli
Beginner
‎03-22-2009 11:57 AM
1,002 Views
Quoting - tim18
Unless you specify the legacy OpenMP library at link time, it would require the libiomp5 (default for 11.0 OpenMP) instead of libguide.

Hi,

Thanks for your response. Could you tell me how I should specify the legacy OpenMP library at link time? I had changed the properties in Microsoft Visual Studio to generate the parallelized code and process OpenMP directives, but is there something elseI should do?
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.