Frequently Answered Questions on IML

Table of Contents

1. IML compatibility issues
   1. Is IML compatible with my processor?
   2. Is IML compatible with my operating system?
   3. Is IML compatible with my compiler?
2. Executing your application which uses IML
   1. My IML application gives SEGV at program termination.
   2. My IML application seems to get stuck in an infinite loop inside IML.
3. Linking IML to your application
   1. Linker gives an error "libm.lib not found" but my application doesn't use math functions.
   2. Linker gives an error "symbols already defined in libc.lib.
4. Misc

Questions and Answers

Is IML compatible with my processor?

Currently, IML supports the following processors. IML should work with processors compatible with them.

• PentiumPro
• Pentium2

If you are a Pentium user wishing to use IML, please write to us. If there's sufficient demand, we'll provide it.

Is IML compatible with my operating system?

Currently, IML supports the following operating systems.

• Windows NT 4.0 on Intel 32bit Architecture
• Windows 95

Is IML compatible with my compiler?

IML is known to be compatible with the following compilers.

• Microsoft Visual C++ version 4.0 or later
• Microsoft FORTRAN PowerStation version 4.0 or later
• Intel C Compiler version 2.3 or later
• Intel FORTRAN Compiler version 2.3 or later

My IML application gives SEGV at program termination.

Your standard library should deallocate resources in an appropriate order but it does not. Try calling iml_Terminate() explicitly.

My IML application seems to get stuck in an infinite loop inside IML.

A pre-release version of IML 1.2 beta had this problem. We believe we have fixed this problem. However, we'd like to know if this problem happens again.

Linker gives an error "libm.lib not found" but my application doesn't use math functions.

IML does not use any functions defined in libm.lib. The linker is somehow confused and tries to link libm.lib. Try linking the application with the /NODEFAULTLIB option (in the case of MS Visual C++ link.exe). You probably have to explicitly specify which library files to link.

Linker gives an error "symbols already defined in libc.lib".

Your linker is probably linking libcd.lib (debug version of libc.lib) after libc.lib is linked. For better debugging, you should link libcd.lib before libc.lib for obvious reasons. Try linking the application with the /FORCE option (in the case of MS Visual C++ link.exe) if the problem persists.