Intel Software Network articles feed

dyld:Library not loaded:libiomp5.dylib

Mon, 16 Nov 2009 01:02:02 -0800

Problem :

Build a mkl program on Mac OS with Intel fortran compiler,

For example, m_cprof_p_11.1.076,
MKLPATH=/opt/intel/Compiler/11.1/076/Frameworks/mkl/lib/em64t
MKLINCLUDE=opt/intel/Compiler/11.1/076/Frameworks/mkl/include
> ifort main. f -o main -L$(MKLPATH) -I$(MKLINCLUDE) -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -lpthread

get compiler warning:
ld64 warning: indirect library libiomp5.dylib could not be loaded: file not found: libiomp5.dylib

Or runtime error:
dyld: Library not loaded: libiomp5.dylib
Referenced from: /opt/intel/Compiler/11.1/076/Frameworks/mkl/lib/em64t/libmkl_intel_thread.dylib
Reason: image not found
Trace/BPT trap

Root Cause :
Since MKL 10.0, MKL libraries for Mac OS* was integrated to Intel® C++/Fortran Compiler Professional Edition. The default path of MKL libraries were changed from
"/Library/Frameworks/Intel_MKL.framework/Versions/10.0.x.xxx/"
to "/opt/intel/Compiler/11.x/0xx/Frameworks/mkl/"

At the same time, the default OpenMP library (libiomp5.dylib, libiomp5.a) used by MKL are not in /lib directory as previous versions. They are under Intel compiler lib directory now.
for example, in /opt/intel/Compiler/11.0/0xx/lib

(IPP is same, please see the article XCode link error: "file not found: libiomp5.dylib" )

Resolution :
For compiler warning,
Please refer to the MKL link line advisor
the command line could be
>ifort main. f -o main -L$(MKLPATH) -I$(MKLINCLUDE) -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -openmp -lpthread

or
ifort main. f -o main -L$(MKLPATH) -I$(MKLINCLUDE) -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core
-L opt/intel/Compiler/11.1/076/lib -liomp5 -lpthread

For run-time error
Please add the path of libiomp5.dylib in system environment before run binary.
>export DYLD_LIBRARY_PATH="opt/intel/Compiler/11.1/076/lib:$DYLD_LIBRARY_PATH"

Intel® IPP Library 6.1 Fixes List

Mon, 02 Nov 2009 08:56:32 -0800

The tables below summarize specific customer issues or feature requests that have been addressed by the indicated product releases. Some items span multiple architectures and/or operating systems and some relate only to a single architecture or operating system.

NOTE: The issues, defects, bug reports, and feature requests described below represent specific issues with specific test cases. An item listed here does not imply that it necessarily applies to your application(s). If your situation does not match the specific test case you may not have experienced the error or problem associated with that update. It is not possible to describe the details of every issue and its specific test case in these tables.

Please post a message on the IPP user forum, http://software.intel.com/en-us/forums/intel-integrated-performance-primitives/, and reference this page and the "DPD" number associated with the item of interest, if you have questions regarding the information in these tables.

IPP v6.1 update 2 (18 Oct 2009)


DPD200084538	UIC sample picnic.exe (64 bits) cannot be started
DPD200085298	Linking problem on 64-bit Mac OS X with IPP fuctions
DPD200084177	Image artifacts in jpeg2000 image
DPD200140266	DMIP crashes when reusing graphs
DPD200140194	BWT error
DPD200082866	Artifacts when usinng ippiResizeSqrtPixel_16_C1R with IPPI_INNTER_LINEAR for interpolation
DPD200138989	Running application in debug causes heap corruption at the end of functions that use UIC classes
DPD200138897	Remove path to .pdb files that reference \\svsfiler02 in release version of Intel IPP libraries
DPD200134422	UG lists wrong threading lib for dynamic and static linking
DPD200133386	mp3 encoder produces fuzzy results with 8k sampleing rate PCM
DPD200136808	IPP C# wrapper bugs
DPD200134685	ippiAbs_32f_AC4IR failed with 300x300
DPD200134689	C++ sample ippi.hpp missing ippiCopy_16u_C1R
DPD200134691	Remove description of ippiGrayDilateBorder/ippiGrayErodeBorder
DPD200132032	ROI is reversed in ippiResizeSqrPixel_x_P
DPD200132259	Place jpeg en/decoder classes in a namespace
DPD200132261	Fix the jpegview makefile for OpenMP from MS VC.NET 2005
DPD200128941	Small destination block size optimization
DPD200132721	Crypto sample error: add -lguide -lpthread in build_ssl_ipp.sh
DPD200131858	Problems with data compression
DPD200131911	Typo error in umc_media_data.h
DPD200133648	ippiSwapChannels_8u_C41R crashes with small image width
DPD200133653	OverFlow in 10-bit DCT ippiDCT8x8Inv_16s_C11()
DPD200133657	Request UMC Deinterlacing Method
DPD200130286	Request convert rgb565 to YUV420 or YUV422
DPD200129614	Add notes about ippiCrossCorrFull_Norm to manual
DPD200132928	Add notes under function ippiCrossCorrx_x
DPD200134288	Bug in WarpBilinearBack function with NN interpolation
DPD200134697	Problem with ippiFilterGaussBorder_32f_C1R
DPD200133374	Correction to custom DLL section of the User Guide
DPD200133848	env\ippenv files do not set threading library locations
DPD200133665	Output for example 12-27 in ippsman.pdf is incorrect
DPD200130099	Unclear document for two H.264 functions
DPD200129120	Feature request for other interpolation method for UndistortRadial
DPD200133872	Feature request for adding documents on utility classes in UMC sample
DPD200134755	Incorrect decoding for IPP MJPEG sample in UMC
DPD200134769	C++ application example includes invalid character
DPD200128945	Other borders in universal pyramid functions
DPD200130212	Add const specifier in DataWriter::PutData() method
DPD200130124	JPEG color conversion functions
DPD200129616	H.264 support for non-IDR frames video
DPD200133693	Line 741 of umc_frame_constuctor.cpp
DPD200134726	ippiMirror returns ippStsSizeErr
DPD200134712	Distored JPEG output
DPD200134959	Unexpected result with ippiColorToGray with integer inputs
DPD200134967	UMC::ColorSparceConversion YUY2->YV12 error

IPP v6.1 update 1 (02 Jul 2009)


DPD200133747	ippiForegroundGaussian does not produce expected results
DPD200134979	ResizeSqrPixel function crash when size<=6
DPD200133708	ippiResizeSqrPixel_8u_C1R performance issue
DPD200132114	ippiQualityIndex_16u32f_C3R() error
DPD200131846	Inconsistent use of const specifier for some IPP functions
DPD200133631	Improve scripts to display clear error message
DPD200131102	No explanation of nonpic libs (linux) in documentation
DPD200134358	NHM function optimization
DPD200133920	ippsFIRSparse is slower than using SSE compiler intrinsics
DPD200134752	Incorrect conversion of RGB to Gray
DPD200134693	redist.txt missing ipp*merged_t.lib
DPD200134748	Redistribute and document libmmds.lib
DPD200134969	Gather interface for accumlulating AAD for AES-GCM
DPD200134763	Interface for accumulating AAD (additional authenticated data)
DPD200136077	Sample build problem: file not found: libiomp5.dylib
DPD200082620	G711 bug in PLC
DPD200134973	UMC::ColorSpaceConversion YUY2 -> YV12 error
DPD200134862	Bug in umc_video_processing.cpp
DPD200134779	ippsCIS_32fc_All does not work
DPD200134356	IPP ZLIB fails to compress image after gzrewind
DPD200134270	ippiNormDiff_L1_8u_C1R error
DPD200133638	ippsNorm_L1_16s32f bug
DPD200132645	MPEG4 decoding problem
DPD200132341	Makefile error for UMC
DPD200131704	Resize function error
DPD200131142	ippiUndistortRadial function gives wrong results
DPD200130292	Performance issue for ippsAccCovarianceMatrix_32f64f_D2
DPD200130035	Add notes for ippiDCTQuantInv8x8LS_JPEG_16s16u functions
DPD200133943	Improve MPEG2Mux
DPD200133939	IppiCrossCorrValid_NormLevel_8u32f
DPD200130294	Performance issue for IPP String processing function on EM64T systems
DPD200134815	ippsResamplePolyphase_32f performance issue
DPD200134750	Internal function cpMul_BNU_FullSize does not obey the IPF software conventions
DPD200134716	ippiCrossCorrFull_NormLevel gives unexpected results
DPD200134707	Crash inside ippiInterpolateAverage16x16_8u_C1IR
DPD200133569	Intermediate computational errors
DPD200129130	Wiener filter MaskSize error
DPD200129122	2D media filter performance
DPD200134399	Incorrect Redist.txt file
DPD200134254	Modify IPP ZLIB sample to get better performance
DPD200128923	Watershed segmentation for 32 bit float images added
DPD200134378	Crypto sample does not work with latest OpenSSL package
DPD200127691	perfsys documentation of -FL
DPD200133670	Problems encoding 16u_C1 jpeg2000
DPD200130345	Add destructive versions of ippsNthMaxElement_32f_I

IPP v6.1 (25 Apr 2009)


DPD200134199	Improve the UMC sample code buiding script
DPD200134679	V-plane Corrupted when input 640x480 YUV422 into encoder
DPD200134370	Bug in 'ippiRGBToYCbCr_8u_C3R'
DPD200134362	ippiTrueDistanceTransform_8u32f_C1R caps the maximum distance value at 1000.0
DPD200134360	ippiDecodeHuffman8x8_Direct_JPEG_1u163_C1 reads beyond input data
DPD200134387	Cannot use libipp_z.a and libipp_bzip2.a at the same time
DPD200134597	Error in color conversion function 'ippiRGBToYCbCr420_8u_C3P3R' for 'u8' variant
DPD200134372	Read error in 'ippiDCTQuantInv8x8To2x2LS_JPEG_16s8u_C1R' for JPEG decoding
DPD200134341	'ippiCompColorKey_8u_C4R' does not work correctly for some ROI widths
DPD200134447	Remove ippStaticInitBest() from Getting_started.htm
DPD200134092	IPP-Crypto- support to RSA_SSA1.5 nor RSA_PKCSv1.5
DPD200133906	ippiCrossCorrValid_NormLevel_32f_C1R on EM64T system
DPD200134376	Bug in colors for planar destinations at lower resolution option in 'JPEGView'
DPD200134386	Issue with ippiTrueDistanceTransform_8u32f_C1R function
DPD200133691	A number of UMC MPEG-4 decoder issues (IPP v. 5.2)
DPD200134366	Missing build64.sh file from data compression sample
DPD200133646	ippsRandomRunform_8u does not produce the upper border value
DPD200134018	Incorrect environment paths set during installation
DPD200133926	Add "Library Dependencies by Domain" table to User's Guide
DPD200133366	Resolution not saved in jpeg
DPD200134179	ippGetStatusString crash in C# sample code
DPD200133821	USC_EC delay issues
DPD200134087	Some missprints in ippi.h
DPD200134368	Bug in the state of CABAC in that mode
DPD200133819	Add pixel aspect ratio as a configuration parameter
DPD200134284	Add info about RTI removal to the release notes
DPD200133922	Add description about libiomp5mt.lib
DPD200133689	A number of issues for the H.264 UMC decoder
DPD200134397	H264 encoder problem after running many hours
DPD200134487	UMC H264 parser memory leak

Avoiding libstdc++ library dependency when using ipp_zlib samples

Tue, 20 Oct 2009 04:30:41 -0700

When C applications are developed based on ipp_zlib samples, it requires the use of libstdc++ libraries to the link line.
Otherewise, while linking you may get __gxx_personality_v0 unresolved external error in ipp_static.o.

This is because the call to ippStaticInit() is done from a struct in ipp_static.cpp file as below.

struct IPP_ZLIB_STATIC_INIT {
int tmp;
IPP_ZLIB_STATIC_INIT(int tmp_init){this->tmp = tmp_init; ippStaticInit();}
};

The above error can be avoided by calling ippStaticInit() from your code directly and excluding ipp_static.cpp from your application project. This will also remove the linking dependency of libstdc++ library in the build.

Simplified Link Instructions for the IPP Library

Thu, 17 Sep 2009 17:26:56 -0700

IPP Link Problem:
Link errors, like the dreaded unresolved external symbol error, keep cropping up and you cannot figure out which IPP lib files should be part of your link list when building your IPP application.

Solution:
By default, the linker only includes, or extracts, those functions, or library members, that your application requests. In this case, it is perfectly acceptable to list ALL the IPP lib files in your link list. Using this approach can significantly simplify your build process bookkeeping. (Caution, a few rules do still apply.)

The IPP lib file link lists shown below should work for building your IPP application. This KB article is based on the v6.1.1 IPP library distribution, version 6.1 update 1 (v6.1.1.xxx).

The link lists below assume a Windows Visual Studio build environment. The basic idea also applies to Windows and Linux makefiles or scripted build environments. For the Linux OS and other operating system build environments you will need to change the extension of your lib filenames to match those for your environment.

- Static Link (thread-safe model):

ippacemerged.lib ippccemerged.lib ippchemerged.lib ippcvemerged.lib ippdcemerged.lib ippdiemerged.lib ippgenemerged.lib ippiemerged.lib ippjemerged.lib ippmemerged.lib ippremerged.lib ippscemerged.lib ippsemerged.lib ippsremerged.lib ippvcemerged.lib ippvmemerged.lib ippacmerged.lib ippccmerged.lib ippchmerged.lib ippcvmerged.lib ippdcmerged.lib ippdimerged.lib ippgenmerged.lib ippimerged.lib ippjmerged.lib ipprmerged.lib ippmmerged.lib ippscmerged.lib ippsmerged.lib ippsrmerged.lib ippvcmerged.lib ippvmmerged.lib ippcore.lib

Note: These library files are located in the lib subdirectory in your IPP install directory. The “thread-safe” model means these libraries are safe to use within a multi-threaded application, even though this version of the library is not multi-threaded.

- Static Link (multi-threaded model):

ippacemerged.lib ippccemerged.lib ippchemerged.lib ippcvemerged.lib ippdcemerged.lib ippdiemerged.lib ippgenemerged.lib ippiemerged.lib ippjemerged.lib ippmemerged.lib ippremerged.lib ippscemerged.lib ippsemerged.lib ippsremerged.lib ippvcemerged.lib ippvmemerged.lib ippacmerged_t.lib ippccmerged.lib ippchmerged_t.lib ippcvmerged_t.lib ippdcmerged_t.lib ippdimerged_t.lib ippgenmerged_t.lib ippimerged_t.lib ippjmerged_t.lib ippmmerged_t.lib ipprmerged_t.lib ippscmerged_t.lib ippsmerged_t.lib ippsrmerged_t.lib ippvcmerged_t.lib ippvmmerged_t.lib ippcore_t.lib libircmt.lib svml_dispmt.lib libmmt.lib libiomp5mt.lib

Note: library files in red are Intel Compiler support files and are needed if you are NOT using the Intel compiler to compile and link your application. The equivalent files on a Linux system are named libirc, libsvml, libimf, and libiomp5. these libraries are required to satisfy Intel compiler optimizations and OpenMP calls used by the IPP library, because the IPP libraries are created using the Intel compiler.

- Dynamic Link:

ippac.lib ippcc.lib ippch.lib ippcv.lib ippdc.lib ippdi.lib ippgen.lib ippi.lib ippj.lib ippm.lib ippr.lib ipps.lib ippsc.lib ippsr.lib ippvc.lib ippvm.lib ippcore.lib libiomp5md.lib

Note: libiomp5md.lib is the Intel OpenMP library file and is used by the IPP libraries to implement multi-threading. The equivalent file is named libiomp5 on a Linux system. These files are located in the stublib directory on a Windows system and in the sharedlib directory on a Linux system. You are not required to use OpenMP in your application when you include this library file, but it is required by some IPP library functions when mult-threading is enabled (the default case). To disable OpenMP threading, within the dynamic libraries, see the ippSetNumThread() function.

IPP Cryptography Library
The IPP cryptography library files are not included in the above lists, since they are not part of the standard product. If you are using the IPP cryptography library you will need to add those library files to your link list. The crypto files are named ippcp*.

About Link List Order
Thank you to my colleague Chao Yu who pointed out that the order of the link list is important for static libraries in a Linux environment, since many of the linkers used in this environment default to operating in a single-pass mode. In this case it is best to order the library files according to the following rule: *emerged.a first, followed by *merged.a and ending with ippcore.a. The lists above have been ordered to reflect that rule.

If you have problems with interdependencies between libraries causing link errors on a Linux system you may need to use the -( and -) options (or equivalent --start-group and --end-group options) with your Linux linker to force multi-pass behavior, at the expense of reduced linker performance.

Additionally, you can repeat the name of a library on the link list to resolve circular dependencies, without resorting to the -( and -) options; by listing a library file a second time after the archive that depends on that key library. The nm command can be used to list the object file names within a specific library archive so you can identify which library is needed to satisfy a missing dependency problem.

Additional Info
Obviously, you must also set your makefile or environment variables to point to the appropriate install directories. See the env and tools subdirectories for your IPP installation for more information or review the articles linked below.

Using Intel® IPP Threaded Static Libraries
Building a Windows* Application Using Intel® IPP
Compiling and Linking with Microsoft* Visual C++* and Intel® C++ Compiler
Error LNK2001: Unresolved External Symbol _ipp*
How to Build an Intel IPP Application
Intel® IPP - Intel® IPP Linkage Models - Quick Reference Guide
Intel® IPP- Library Dependencies by Domain
Intel® IPP - Threading / OpenMP* FAQ

unresolved external symbol __intel_fast_memcpy

Mon, 24 Aug 2009 19:42:53 -0700

Problem :
When link ipp static library, get the link error
ippsmerged_t.lib(pscopyca_split_px_ownsCopy_8u.obj) : error LNK2019: unresolved external symbol __intel_fast_memcpy referenced in function

for example, build the below C code in Microsoft* Visual Studio IDE

#pragma comment(lib, "ippsemerged.lib")
#pragma comment(lib, "ippsmerged_t.lib")
#pragma comment(lib, "libiomp5mt.lib")
#pragma comment(lib, "ippcore_t.lib")

#include

int main()
{
ippsCopy_32f(0,0,0);
return 0;
}

Root Cause :

The symbol intel_fast_memcpy is defined in Intel support library : libirc.lib and libircmt.lib. It optimizes memory copy function memcpy() for specific CPU types by the use of SSE vector instructions where appropriate.

The libraries are from Intel Compiler and also be included in IPP library.

libirc.lib
Intel support library for CPU dispatch, intel_fast_ memory, and traceback support routines

libircmt.lib
Same as libirc.lib, but with thread-safe support. This library is shipped for legacy purposes, as libirc.lib now contains thread-safe support.

See more in Intel Compiler on-line manual :
http://software.intel.com/sites/products/documentation/hpc/compilerpro/en-us/cpp/win/compiler_c/bldaps_cls/cppug_ccw/bldaps_libs_tools_cw.htm

Resolution :
Please link libirc.lib or libircmt.lib into your project

#pragma comment(lib, "ippsemerged.lib")
#pragma comment(lib, "ippsmerged_t.lib")
#pragma comment(lib, "libiomp5mt.lib")
#pragma comment(lib, "ippcore_t.lib")
#pragma comment(lib, "libirc.lib")

or in project propery page =>Configuration Properies =>Linker =>Input=>Additinal Dependency
add ippsemerged.lib ippsmerged_t.lib ippcore_t.lib ippiomp5mt.lib libirc.lib

Add IPP library path, e.g. C:\Program Files\Intel\IPP\6.1.1.035\ia32\lib
in Configuration Properies =>Linker =>General =>Additional Library Directories at the same time if need.

OMP abort: Initializing libguide.lib, but found libguide40.lib already

Tue, 07 Jul 2009 22:20:25 -0700

Symptom(s):
OMP abort: Initializing libguide.lib, but found libguide40.lib already initialized.

This can cause performance degradation.

Set environment variable KMP_DUPLICATE_LIB_OK=TRUE if you want your program to continue in this case.

Cause:

mkl_c.lib is one of mkl static library interface. It defines libguide.lib as a default library for resolution of threading library calls. But other Intel® software such as Intel® IPP, Intel® C++ Compiler and Intel® OpenCV defined libguid40.lib as default. So the error arises because of the duplicate initialization of libguide.lib when using static MKL library and other Intel software at the same time.

Solution:

You could use linker switch /nodefaultlib:libguide.lib and link with libguide40.lib by adding the option to the link line or in project option.

For example, link users.obj mkl_c.lib /nodefaultlib:libguide.lib libguide40.lib. This will stop mkl_c.lib from defining libguide.lib as a default library for resolution of threading library calls.

Operating System:

Windows* XP Professional, Windows* XP Home Edition, Windows* XP Tablet PC Edition, Windows* XP Media Center Edition

XCode link error: "file not found: libiomp5.dylib"

Tue, 26 May 2009 00:55:13 -0700

Environment :

Mac OS* X 10.5.x, Xcode 3.x.x. Intel® C++ Compiler Professional Edition for Mac OS* X, version 11.x.xxx, Installed compiler with default options.

Problem:

Build any application linking with dynamic IPP library, get build error: file not found:libiomp5.dylib

For example, download the IPP sample m_ipp-samples_p_6.0.0.109 from http://software.intel.com/en-us/articles/intel-integrated-performance-primitives-code-samples/

Open the /image-processing/image-processing-functions/ippiDemo.xcodeproj in Xcode IDE.

Build the ippiDemo.xcodeproj project, it will fail with error message: file not found:libiomp5.dylib

Build failed(1 error)

Resolution :
As a workaround, please try

1) # cd /Library/Frameworks/Intel_IPP.framework

2) # ./Versions/Current/tools/env/ippunbind.sh

3) # cp /opt/intel/Compiler/11.0/0xx/lib/libiomp5.dylib ./Libraries

4) # ./Versions/Current/tools/env/ippbind.sh

Please note: since 6.0, IPP libraries for Mac OS* was integrated to Intel® C++ Compiler Professional Edition. As the default OpenMP library (libiomp5.dylib, libiomp5.a) used by IPP are not in IPP Libraries/lib directory as previous versions. They are actually under Intel compiler lib directory /opt/intel/Compiler/11.0/0xx/lib now.

Other related error: "Library not loaded: libiomp5.dylib"

If add -liomp5 to the "Other Linker Flags" and added "/opt/intel/Compiler/11.0/0xx/lib/" to the "Library Search Paths" in the ippiDemo project.
Or
try IPP static link: add –lippsemerged –lippsmerged /opt/intel/Compiler/11.0/056/Frameworks/ipp/lib/libippcore.a

The project compiled, but at run time, it failed with error:
Library not loaded: libiomp5.dylib
Referenced from: /opt/intel/Compiler/11.0/056/Frameworks/ipp/Libraries/libippac-6.0.dylib
Reason: image not found

Workaround:

If dynamic link IPP library, please try the resolution as above.

If static link IPP library, please delete the explicit link files in the project :ippiDemo.xcodeproj. libippi.dylib libipps.dylib libippcore.dylib and Intel_IPP.Frameworks and rebuild.

unresolved external symbol __libm_sse2 and _iob

Mon, 23 Mar 2009 20:37:34 -0700

Symptom(s):

When link with the static threaded version of IPP libraries, e.g ippiemergedem64t.lib ippimergedem64_t.lib.
receive the following error

ippimergedem64t_t.lib(piwarp_split_mx_ippiGetRotateShift.obj) : error LNK2019: unresolved external symbol __libm_sse2_sincos referenced in function mx_ippixxx

Cause:

The symbol is defined in Intel Math library libm*.lib provided by Intel® C++ Compiler. The Math library contains highly optimized mathematical functions, such as sin(), cos(). Some IPP functions depends on them.

Library Option Description
libm.lib Default static math library.
libmmt.lib /MT Multi-threaded static math library.
libmmd.lib /MD Dynamically linked math library.
libmmdd.lib /MDd Dynamically linked debug math library.
libmmds.lib Static version compiled with /MD option.

Solution:

Link the libmmt.lib in your application.

IPP bundle the library libmmt.lib/libm.lib in directory lib, by default they are in C:\Program Files\Intel\IPP\6.0.0.xx\[em64t|ia32]\lib.

Please note, we assume that the applicatoin is build with /MT option here. The Intel math library linked to an application depends on the compilation or linkage options specified. Refer to the above table.

Troubleshooting
After link libmmt.lib, a sequential error may appear:

libmmt.lib(libm_error.obj) : error LNK2019: unresolved external symbol _iob referenced in function write_message

The symbol _iob is defined in MSVC static C run-time library libcmt.lib. When using IPP static threaded library in MSVC, we assume that the application is build with /MT option, thus link libcmt.lib automatically.

But one application or it's parts may build with /MD option, which will link MSVC dynamic C run-time library MSVCRT*.dll,which haven't the symbol defined. In this case, please link libmmds.lib instead.

libmmds.lib - Static math library version compiled with /MD option, which is provided by Intel Compiler.

Notes:
Both Intel Profession Compiler and Intel Parallel Composer include IPP library and the Intel Math Libraries. You may find them in their install directory.

Intel® Integrated Performance Primitives (Intel® IPP) - Error: "No DLL was found."

Fri, 19 Sep 2008 00:00:00 -0700

Symptom(s):

I ran an Intel® IPP application and obtained one of the error messages below:

"No DLL was found in the Waterfall procedure."

"This application has failed to start because ippxx-x.x.dll was not found."

Cause:

Windows* is unable to determine the location of the Intel IPP dynamic libraries.

Solution:

Four solutions to this problem are listed below:

Before using the Intel IPP dynamic libraries, add the location of the DLLs to the PATH environment variable. The instructions below are for a Windows* XP system. Please refer to your operating system help file for more information on how to set environment variables.
1. Open Control Panel and select System.
2. Click Advanced.
3. Click Environment Variables.
4. Double-click the variable PATH in User Variables.
5. Add the path to the Intel IPP dynamic libraries to variable value.
  For example, if you installed the Intel IPP to the default location and are running a 32-bit application then add C:Program FilesIntelIPPx.xia32 to the PATH.
6. Close all Control Panel windows.
7. Close Microsoft Visual C++*.
Note: Make sure to close Microsoft Visual C++ and restart to have the PATH variable take effect. Then rerun the application.
Use the Intel IPP Runtime Installer (RTI), located in IPPx.xia32 ools untime, to automatically install the dynamic libraries to the system32 directory.
Manually copy the contents of IPPx.xia32

Intel® Integrated Performance Primitives (Intel® IPP) for Linux* (IA) - Error: "No shared library was in the waterfall procedure"

Fri, 19 Sep 2008 00:00:00 -0700

I compiled and ran a C program with Intel® IPP and and obtained error message:

"No shared library was in the Waterfall procedure"

How can I fix this?
This problem happens because the application can not the find the correct processor-specific libraries. These processor-specific libraries are named *px*.so, *a6*.so, *t7*.so, *w7*.so, *v8*.so and *p8*. At run time, Intel IPP "dispatcher" libraries (named ipp*.so) will detect the processor and load the correct processor-specific libraries.

In order to fix this problem, the path to Intel IPP "dispatcher" libraries and CPU specific libraries must be added to the system variable LD_LIBRARY_PATH. For example, if IPP "dispatcher"libraries and CPU specific libraries are included in the folder /opt/intel/ipp/X.X/ia32/sharedlib, the following command line should be entered to set the variable in the bash shell:

export LD_LIBRARY_PATH=/opt/intel/ipp/X.X/ia32/sharedlib:$LD_LIBRARY_PATH

When you redistribute Intel IPP dynamic libraries with your application, you need to redistribute both "dispatcher" libraries and processor-specific libraries.
For more information, please read the document Deploying applications with Intel® IPP DLLs.

Operating System:

Mac OS*, Red Hat* Enterprise Linux 2.1, SUSE* Linux 9.1, SUSE* Linux Enterprise Server 8.0, SUSE* Linux Enterprise Server 9.0, Red Hat* Enterprise Linux 4.0, Red Hat* Linux 7.3, Red Hat* Linux 8.0, Red Hat* Linux 9.0, Red Hat* Enterprise Linux 3.0, SUSE* Linux* 8.2