- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
The installed MKL8's lib folder contains 32/ , 64/ and em64t/.
While insatlling AMBER8 it took MKL lib from 32/ dir on AMD64 Dual core. dual CPU opteron. Installed successfully.
When I execute, its giving following error:
$ $AMBERHOME/exe/sander: symbol lookup error: /home/sangamesh/AMBER-Intel/amber8/exe/sander: undefined symbol: __intel_cpu_indicator
When used AMBER9 it took MKL lib from em64t/. And it failed to build the executable with the following error:
ld: skipping incompatible /opt/BLAS_LIBS/MKL8/lib/em64t/libvml.so when searching for -lvml
ld: cannot find -lvml
Can any one tell how to resolve this problem?
Regards,
Sangamesh
The installed MKL8's lib folder contains 32/ , 64/ and em64t/.
While insatlling AMBER8 it took MKL lib from 32/ dir on AMD64 Dual core. dual CPU opteron. Installed successfully.
When I execute, its giving following error:
$ $AMBERHOME/exe/sander: symbol lookup error: /home/sangamesh/AMBER-Intel/amber8/exe/sander: undefined symbol: __intel_cpu_indicator
When used AMBER9 it took MKL lib from em64t/. And it failed to build the executable with the following error:
ld: skipping incompatible /opt/BLAS_LIBS/MKL8/lib/em64t/libvml.so when searching for -lvml
ld: cannot find -lvml
Can any one tell how to resolve this problem?
Regards,
Sangamesh
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you are trying to run a 32-bit build which uses dynamic libraries, you must take care to put the necessary 32-bit libraries in LD_LIBRARY_PATH. Perhaps you need /opt/BLAS_LIBS/MKL8/lib/ in LD_LIBRARY_PATH.
In my experience, this cpu_indicator error could be caused by confusion between an out of date libguide provided with MKL, and a more up to date libguide used by the openmp option of an Intel compiler. In that case, you would want the 32-bit compiler library to show in LD_LIBRARY_PATH, rather than the MKL, or you might do better with a more up to date MKL.
In my experience, this cpu_indicator error could be caused by confusion between an out of date libguide provided with MKL, and a more up to date libguide used by the openmp option of an Intel compiler. In that case, you would want the 32-bit compiler library to show in LD_LIBRARY_PATH, rather than the MKL, or you might do better with a more up to date MKL.
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