topic Re: error: mkl.h: No such file or directory in Intel® oneAPI Math Kernel Library

error: mkl.h: No such file or directory

zx123 — Wed, 23 Dec 2009 01:34:22 GMT

Hi

I can't fix error in my makefile:

CPP=/opt/intel/Compiler/11.1/059/bin/ia32/icpc
INC=/opt/intel/Compiler/11.1/059/mkl/include/
LIB=/opt/intel/Compiler/11.1/059/mkl/lib/32/
main: main.cpp
$(CPP) -Wall -I$(INC) -c main.cpp
main: main.o
$(CPP) main.o -L$(LIB) -lmkl_intel -lmkl_core -lmkl_intel_thread -liomp5 -lpthread -lm -o main

Then I try to compile I always get error: mkl.h: No such file or directory. What is wrong?

The following script compiles correctly
#! /bin/bash
PATH_LIB="/opt/intel/Compiler/11.1/059/mkl/lib/32"
PATH_MKL="/opt/intel/Compiler/11.1/059/mkl/include/"
PATH_CPP="/opt/intel/Compiler/11.1/059/bin/ia32/"
LANG=C ${PATH_CPP}icpc main.cpp -I${PATH_MKL} -L${PATH_LIB} -static -lmkl_intel -lmkl_core -lmkl_intel_thread -liomp5 -lpthread -lm -o main

Re: error: mkl.h: No such file or directory

Evgueni_P_Intel — Wed, 23 Dec 2009 02:50:31 GMT

Quoting - zx123

Hi zx123!
I think that the target of the 1st rule should be main.o.
-Evgueni.

Re: error: mkl.h: No such file or directory

Evgueni_P_Intel — Wed, 23 Dec 2009 06:16:39 GMT

...that is, the make file should look as follows:
main.o: main.cpp
$(CPP) -Wall -I$(INC) -c main.cpp
main: main.o
$(CPP) main.o -L$(LIB) -lmkl_intel -lmkl_core -lmkl_intel_thread -liomp5 -lpthread -lm -o main

Re: error: mkl.h: No such file or directory

zx123 — Wed, 23 Dec 2009 08:42:47 GMT

Yes, it works!!!

Thank you, Evgueni

Re: error: mkl.h: No such file or directory

zx123 — Wed, 23 Dec 2009 09:38:21 GMT

Sorry...Sure I'm not programmer...

I replaced main: main.cpp -> main.o: main.cpp
but now makefile creates main.o but I still have not an executable. My makefile does not produce executable file. What is wrong now?

Re: error: mkl.h: No such file or directory

Evgueni_P_Intel — Wed, 23 Dec 2009 09:45:09 GMT

Quoting - zx123

Your make file produces an executable called main -- this name is given after the -o switch at the end of the second rule.
Though this namedoesn'tendwith .exe, you can run the file.
-Evgueni.

Re: error: mkl.h: No such file or directory

zx123 — Wed, 23 Dec 2009 21:05:48 GMT

Quoting - Evgueni Petrov aka espetrov (Intel)

Your make file produces an executable called main -- this name is given after the -o switch at the end of the second rule.
Though this namedoesn'tendwith .exe, you can run the file.
-Evgueni.

Unfortunately, an executable (indeed called main) is produced only if I use main: main.cpp instead of main.o: main.cpp and only if I exclude #include ''mkl.h'' from my code. If I unclude both main.o: main.cpp and #include ''mkl.h'' no any executables are produced - only main.o That is very strange...

Is it possible to compile code with mkl library using only one rule as in my script that I listed in my first post?

Re: error: mkl.h: No such file or directory

Evgueni_P_Intel — Thu, 24 Dec 2009 03:53:22 GMT

zx123,
Remember that by default make makes the target of the first rule (the tokens before the semicolon.)
Do make main instead of make or put the rule for main in front of the rule for main.o.
Good luck!

But... you may find running your application also tricky!
Your make file links your application to your dynamic MKL libraries.
For this reason, your application contains only references to the needed MKL libraries, functions, andvaribales.
These references are resolved only when you run your application.
At that moment, the linker needs to know the path to the MKL libraries because by default this path isn't hard-coded in your application.
The standard solution is to add the path to the MKL libraries to environment variable LD_LIBRARY_PATH as follows:
export LD_LIBRARY_PATH=/opt/intel/Compiler/11.1/059/mkl/lib/32/:${LD_LIBRARY_PATH}
Of course, this needs be done before you run the application.
Good luck once again!

-Evgueni.

Re: error: mkl.h: No such file or directory

zx123 — Thu, 24 Dec 2009 10:12:42 GMT

yes, I understood

Thank you!

This error tends to happen if

Subodh_P_ — Tue, 19 Jan 2016 11:39:40 GMT

This error tends to happen if the paths for include headers and bindings are not set correctly. Intel has made this process very straightforward now. Just set the environment using following command for say intel64 architecture located at /opt/intel/bin.

source ./compilervars.sh intel64

This will set all the appropriate locations for MKL/TBB/etc headers. If you intent to set only the MKL paths then refer to bash script located at /opt/intel/mkl/bin named as "mklvars.sh"

Thanks,

Subodh Pachghare