- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I want to run a program created with IVF and /Qopenmp on my laptop. When I try to execute it (using one thread) I get the message: This application has failed to start because libiomp5md.dll was not found.
Do I need to install some libraries somewhere and set an environment variable? Or perhaps to run on a single-CPU machine the program needs to be built without OMP?
Do I need to install some libraries somewhere and set an environment variable? Or perhaps to run on a single-CPU machine the program needs to be built without OMP?
Link Copied
6 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There's no point in building with /Qopenmp if you intend to run just one thread, but you ought to be able to do it. If running from the command prompt, the PATH as it is set up in the ifort command prompt window would find the shared libraries. The paths are set by the ifortvars.bat which is included in the Start menu shortcut for ifort command prompt.
If running the default dynamic linked build on a machine where ifort isn't installed, you would have to copy over the shared libraries used by your .exe. When you don't set any environment variables, the standard Windows rules govern where the libraries would be found (same folder as the .exe, standard shared library directories, ...) In current ifort, choice of static or dynamic OpenMP library linking is a separate switch from the choice for the other libraries.
If running the default dynamic linked build on a machine where ifort isn't installed, you would have to copy over the shared libraries used by your .exe. When you don't set any environment variables, the standard Windows rules govern where the libraries would be found (same folder as the .exe, standard shared library directories, ...) In current ifort, choice of static or dynamic OpenMP library linking is a separate switch from the choice for the other libraries.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - tim18
There's no point in building with /Qopenmp if you intend to run just one thread, but you ought to be able to do it. If running from the command prompt, the PATH as it is set up in the ifort command prompt window would find the shared libraries. The paths are set by the ifortvars.bat which is included in the Start menu shortcut for ifort command prompt.
If running the default dynamic linked build on a machine where ifort isn't installed, you would have to copy over the shared libraries used by your .exe. When you don't set any environment variables, the standard Windows rules govern where the libraries would be found (same folder as the .exe, standard shared library directories, ...) In current ifort, choice of static or dynamic OpenMP library linking is a separate switch from the choice for the other libraries.
If running the default dynamic linked build on a machine where ifort isn't installed, you would have to copy over the shared libraries used by your .exe. When you don't set any environment variables, the standard Windows rules govern where the libraries would be found (same folder as the .exe, standard shared library directories, ...) In current ifort, choice of static or dynamic OpenMP library linking is a separate switch from the choice for the other libraries.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When the compiler installed, by default it adds to PATH the path containing the compiler's LIB folder. It sounds as if that didn't happen for you. Depending on how you installed, you may have been asked if this was ok and said no.
Add to PATH the following:
%IFORT_COMPILER11%libia32
Add to PATH the following:
%IFORT_COMPILER11%libia32
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
When the compiler installed, by default it adds to PATH the path containing the compiler's LIB folder. It sounds as if that didn't happen for you. Depending on how you installed, you may have been asked if this was ok and said no.
Add to PATH the following:
%IFORT_COMPILER11%libia32
Add to PATH the following:
%IFORT_COMPILER11%libia32
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. You have to copy the dependent DLLs to the target system. For the Intel DLLs, you can put them in the same folder as the executable or in a folder on PATH. libiomp5md.dll may be the only one you need if you did not ask to link against DLL libraries (you get that one as a DLL by default anyway.) You can find the Intel DLLs in the LIB folder.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
Yes. You have to copy the dependent DLLs to the target system. For the Intel DLLs, you can put them in the same folder as the executable or in a folder on PATH. libiomp5md.dll may be the only one you need if you did not ask to link against DLL libraries (you get that one as a DLL by default anyway.) You can find the Intel DLLs in the LIB folder.
Gib
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