Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Error in opening the Library module file

kirschpe
Beginner
‎09-26-2003 03:17 PM
452 Views
In compiling my code with a "use kernel32" statement I get ...

Error: Error in opening the Library module file. [KERNEL32]
use kernel32
------------^

I'm using Compaq fortran 6.6b on on Intel machine.

This used to compile.

thanks...
What happened and how do I fix it.
0 Kudos

Link Copied

2 Replies
Steven_L_Intel1
Employee
‎09-26-2003 04:09 PM
452 Views
Are you using the command line or the IDE? Have you also installed Intel Fortran 7.x?

If you're using the IDE, the compiler looks in the list of folders under Tools..Options..Directories..Include Files. If the command line, the INCLUDE environment variable. The folder ending in DF98INCLUDE should be in these. If Intel Fortran 7.x folders are in the list, remove them.

Steve
0 Kudos
Copy link
kirschpe
Beginner
‎10-01-2003 02:44 PM
452 Views
I solved my own problem.

Somehow the fortran includes files directory, C:PROGRAM FILESMICROSOFT VISUAL STUDIODF98INCLUDE, was missing.

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.