Warning message: Cannot open message catalog”1037libiomp5ui.dll”

Product Index
Search

Intel® Software Network

Language:
- English

	January 21, 2010 8:00 PM PST

Problem:

While running the application linked with IPP a command window is popped-up with the following text:
OMP: Warning #2: Cannot open message catalog "1037\libiomp5ui.dll":
OMP: System error #126: The specified module could not be found.
OMP: Info #3: Default messages will be used.

Root Case:

Currently IPP supports English and Japanese messages only and so locale catalogs for them.
There is no support for other languages.

Solution:

There are several workarounds for this issue:

1. set the environment variable, to suppress the run-time warnings
set KMP_WARNINGS=0
2. at the beginning of the code call routine kmp_set_defaults( “KMP_WARNINGS=0” ) (the Intel extension routine for OpenMP)
3. manually copy libomp5ui.dll (English version or Japanese one ) into 1037\libiomp5ui.d under corresponding binary catalog for Intel Compiler
e.g. <compiler_install_dir>\bin\ia32\1037\libiomp5ui.dll

Resolution:

we are going to fix the problem at the next release.

Do you need more help?

Search knowledge base
Visit user forums
Find additional support

This article applies to: Intel® Integrated Performance Primitives Knowledge Base

For more complete information about compiler optimizations, see our Optimization Notice.

Comments (6)

March 13, 2010 12:43 PM PST

heinz

Total Points:
3,577

Brown Belt

Hi Gennady,
this is not fixed in update5 of "Intel Compiler Suite Pro" and "Parallel Studio" Composer update5.
I was waiting for it.

heinz

March 13, 2010 12:57 PM PST

heinz

Total Points:
3,577

Brown Belt

Hi Gennady

small typo fix: in point 3. --> a i is missing in the name libomp5ui.dll

3. manually copy libiomp5UI.dll (English version or Japanese one ) into 1037libiomp5UI.dll under corresponding binary catalog for Intel Compiler

hint: libiomp5UI.dll is to find still in 1041 (Japanese) not in 1033 (English)

March 18, 2010 10:39 AM PDT

Albert

Did anybody try the workaround (2) with ICC Pro 11.1 update 5? Does it work?

I tried kmp_set_warnings_off(); but it does not work.
(3) works, but it is not feasible for deployment. Our customers has many different languages and we have to create many folders such as "1031", "1044" ....
I think (1) also does not work.

April 4, 2010 3:05 PM PDT

Albert

Any follow up on this bug? I have tried both work around (1) and (2) on ICC PRO 11.1 update 5. They do NOT work at all. (2) works but not feasible when we have to deal with many possible languages.

This problem has be in the last couple of releases and was repeatedly reported. I am wondering what type of QA system you guys are using. BTW, I having been an extensive ICC/IPP/MKL user for the last 5 years and this type of problems came up all the time. For example, even in your current release, the vml is not working on your 64-bit core 2 processors (sub try vdSub or vdAdd on a 64-bit compile on core 2 dual system).

I like the functionality and the performance gain ICC/IPP/MKL are providing. However, each new release you guys will fix a few problems but also introduce new bugs. I think the quality is much more important than introducing new functionality.

April 22, 2010 5:16 AM PDT

Victor Pasko (Intel)

Total Points:
5,606

Brown Belt

Correction for Solution: 1. set the environment variable, to suppress the run-time warnings

On Linux with bash:

export KMP_AFFINITY=nowarnings
or if you had affinity settings
export KMP_AFFINITY=nowarnings,$KMP_AFFINITY

On Windows:

set KMP_AFFINITY=nowarnings
or if you had affinity settings
set KMP_AFFINITY=nowarnings,%KMP_AFFINITY%

April 23, 2010 8:41 PM PDT

Gennady Fedorov (Intel)

Total Points:
45,230

Black Belt

Hello everybody,
the fix of the problem available in the version of IPP bundled with in the latest Intel(R) Compiler Professional version 11.1 Update 6.
and with the standalone version of IPP v.6.1 Update5