Intel Software Network articles Feed

“Fatal error LNK1103: debugging information corrupt” when building Intel IPP 7.0 with Visual C++ 2005

Wed, 12 Jan 2011 05:00:00 -0800

When linking IPP 7.0 static libraries with Microsoft Visual C++ 2005*, the application may review the following link errors:

"Fatal error LNK1103: debugging information corrupt."

An example error message is as bellow:

ipps_l.lib(psbitrevw7as.obj) : fatal error LNK1103: debugging information corrupt; recompile module
ippcore_l.lib(pscpudefas.obj) : fatal error LNK1103: debugging information corrupt; recompile module

The problem happened because of the compatibility issue between different Microsoft Visual C++ versions:

To fix this problem, please check the following knowledge base article for Microsoft Visual C++* , and install the hot fix:
http://support.microsoft.com/kb/949009/en-us/

The DirectX* render in UMC sample failing at Windows* 7 or Windows Vista*

Thu, 03 Jun 2010 05:00:00 -0700

Problem :

When Windows Aero is turned on at Windows* 7 or Windows Vista*, the simpleplayer application in Unified Media Classes (UMC) sample does not render any video with the error message:

"Error in video render"

Root Cause :

The UMC DirectX* render sample uses old function interfaces and does not work with Windows* Aero. Users need to disable Windows Aero if they run the simpleplayer application.

When users add UMC DirectX render sample code (dx_drv.cpp) in the application, the DirectX render also does not work correctly at Windows* systems with Aero enabled.

Workaround :

The workaround for this problem is to disable Windows Aero to run the simpler player applications. When users add the DirectX render sample code (dx_drv.cpp) in the application, they can use the attached file is to temporally disable Aero.

The problem was fixed in Intel IPP 7.0 release.

Intel® IPP Library 6.1 Fixes List

Thu, 04 Feb 2010 08:00:00 -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 summarized 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.

Providing a complete description of each item in the list below is impractical. For that reason we ask that you post a message on the IPP user forum and reference this page and the "DPD" number of interest if you have further questions regarding the information in these tables. A DPD number with more information has a link.

These tables are updated regularly to correct errors and omissions.

NOTE: The bugs listed below are for both the IPP library and the IPP sample code. Always upgrade the IPP library and sample code at the same time.

IPP v6.1 update 6 (30 Jul 2010)

DPD200155165        UMC simple_player app does not work with Windows Aero interface.
DPD200154198        Data Compression error in ZLIB (deflate.c) when source buffer size >=48K.
DPD200154900        Data compression error with deflate() under certain variable block size conditions.
DPD200153276        Change alignment in H.264 UMC decoder to DECLALIGN macros insted of __ICL alignment.
DPD200087211        Documentation: Example 9-4 ippiFilterColumn() needs to include border information.
DPD200154874        Documentation: ippsFIR() descriptions are misleading or incorrect in description of "numIter" parameter.
DPD200186071        Documentation: Correct example 6-1 using ippiRGBToYUV() -- wrong ROI size: should be {3,3} not {9,3).

IPP v6.1 update 5 (9 Apr 2010)

DPD200150333        Output image has small corruption on top edge when applying WarpAffine with dst roi size (1920 x 240).
DPD200150883        Delphi sample code error on loading file name (sample has been updated).
DPD200089782        JPEG grayscale lossless compresion distortion.
DPD200150199        Error in DIB_PAD_BYTES in UIC picnic sample.
DPD200151794        Corrected results for the ippGetNumCoresOnDie() function on multi-core processors.
DPD200151952        IPP-zlib compress generates spurious compressed data that cannot be decompressed.
DPD200089070        UMC H264EncoderFrameList_InsertFrame() fails allocating 15MB frame buffer, returns null pointer.
DPD200092946        Picnic sample application produces invalid JPEG 2000 files when saving in lossless format.
DPD200187089        ippiRGBToGray_8u_AC4C1R and ippiRGBToGray_8u_C3C1R translate RGB(255,255,255) to 254.

IPP v6.1 update 4 (10 Feb 2010)

DPD200149498        Memory leak in H.264 UMC sample code with resolution change on same instance of decoder.
DPD200150122        IPP_BZIP2 data corruption -- data sensitive and isolated to a 3mb fragment of a specific binary file.
DPD200149570        IPP samples redistribution file and EULA updated for clarification.
DPD200087613        ippsFilterNoiseDetect* "ascending noise detection" problem fixed. PESQ was increased by ~0.01.
DPD200148808        Cryptography function ippsECCPComparePoint* contains a misprint: "equial" should be "equal."

IPP v6.1 update 3 (26 Nov 2009)

DPD200140668        ippiResizeSqrPixel_8u_C1R has differing results depending on CPU (rounding error problem)
DPD200134986        DFT performance optimization for lengths 8*n, 16*n, 13*n, p*n (p>50)
DPD200084751        Correct ippiColorToGray_8u_C3C1R rounding errors
DPD200086319        ippiSegmentWatershed_8u16u should use the value IPP_MAX_16U for border pixels but uses 8u instead
DPD200084408        Problem with IPP linking in kernel mode for Intel64 (em64t red zone in ring0 and interrupts)
DPD200087170        ippiCopy_8u_C1R performance on v8 architecture (v8 code slower in Core 2 Duo than t7 and w7)
DPD200141560        Feature request: BZIP2 with ipp_ prefixes

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
DPD200138989        Running application in debug causes heap corruption at the end of functions that use UIC classes
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
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
DPD200133648        ippiSwapChannels_8u_C41R crashes with small image width
DPD200133653        OverFlow in 10-bit DCT ippiDCT8x8Inv_16s_C11()
DPD200134288        Bug in WarpBilinearBack function with NN interpolation
DPD200134697        Problem with ippiFilterGaussBorder_32f_C1R
DPD200133374        Correction to custom DLL section of the User Guide
DPD200133665        Document: Output for example 12-27 in ippsman.pdf is incorrect
DPD200134755        Incorrect decoding for IPP MJPEG sample in UMC
DPD200130124        JPEG color conversion functions
DPD200133693        Line 741 of umc_frame_constuctor.cpp
DPD200134726        Document error: 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 (Intel Nehalem microarchitecture) function optimizations
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
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
DPD200133670        Problems encoding 16u_C1 jpeg2000
DPD200130345        Add destructive versions of ippsNthMaxElement_32f_I

IPP v6.1 (25 Apr 2009)

DPD200134199        Feature request: 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
DPD200133366        Resolution not saved in jpeg
DPD200134179        ippGetStatusString crash in C# sample code
DPD200133821        USC_EC delay issues
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
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

dyld:Library not loaded:libiomp5.dylib

Sat, 23 Jan 2010 06:00:00 -0800

Problem :

Build an Intel® 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, the MKL libraries for Mac OS* have been integrated into Intel® C++/Fortran Compiler Professional Edition or Intel® C++/Fortran Composer XE for Mac OS* X. 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 libraries (libiomp5.dylib, libiomp5.a) used by MKL are not in /lib directory as in previous versions. They are under the Intel compiler lib directory now.
for example, in /opt/intel/Compiler/11.0/0xx/lib

(IPP is the 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 runtime error: like dyld: Library not loaded: lib[mkl|ipp]_x.dylib

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

In Xcode 2.3 development environment,
Under Executables, Double click active Executable, click "Arguments" Tab, under Variables to be set in the environment, Add DYLD_LIBRARY_PATH , set value, for example,
/opt/intel/Compiler/11.1/076/lib:/opt/intel/Compiler/11.1/080/Frameworks/mkl/lib/em64t

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

Thu, 21 Jan 2010 21:00:00 -0800

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. \bin\ia32\1037\libiomp5ui.dll

Resolution:

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

JPEG Bug Fix Details

Fri, 08 Jan 2010 00:00:00 -0800

In reply to this forum thread http://software.intel.com/en-us/forums/intel-integrated-performance-primitives/topic/69755/

DPD200130124 - JPEG color conversion function request
Added support for RGBA as an input format for the IPP JPEG encoder and RGBA/BGRA as an output format for the IPP JPEG decoder. This functionality is also available in the UIC JPEG codec. This function helps avoid a memory copy from RGBA to RGB format.

DPD200134755 - incorrect decoding for IPP MJPEG sample in UMC
Fixed an issue where the last (bottom right) 8x8 fragment of an image might be incorrectly decoded and instead there is a solid gray 8x8 area.

DPD200134712 - distored JPEG output

Opening a BMP file and saving as JPEG using the settings: Bas, 444, Huffman, RGB, quality=75 results in a grayscale and distorted JPEG file.

DPD200134360 - ippiDecodeHuffman8x8_Direct_JPEG_1u163_C1 read beyong input data
An issue with the above function when decoding a JPEG file under certain conditions; the function reads beyond the input data. This is reported by Valgrind or when using the Electric Fence tool. This has been tested on Linux both 32-bit and 64-bit. The "unoptimized" variants (i.e. 'px' and 'mx') do not exhibit this problem. Although not tested, the problem may also occur on Windows.

DPD200134372 - read error in 'ippiDCTQuantInv8x8To2x2LS_JPEG_16s8u_C1R' for JPEG decoding
A problem in the above function exists when reducing JPEG images to a lower resolution. The problem occurs when 'ippiDCTQuantInv8x8To2x2LS_JPEG_16s8u_C1R' and an inverse DCT, inverse quantization and level-shifting is focused on the upper-left 2x2 part of an 8x8 block. The function reads "too far" in the *destination* buffer. This can cause a read access violation. Observed on *both* Linux and Windows and both 32-bit and 64-bit optimizations. The "unoptimized" 'px' (32-bit) and 'mx' (64-bit) variants do not exhibit the problem.

DPD200134376 - bug in colors for planar destinations at lower resolution option in 'JPEGView'
Not a bug but a request for a new mode: decoding of reduced resolution for planar output image format. When choosing to decode to smaller resolutions and extract native data in planar YCbCr format, the color planes seem to be wrongly handled as the resulting image shows color errors. Only the left half of image contains color, that is incorrect.

DPD200133366 - resolution not saved in JPEG
The sample code encoder/decoder does not pass Image Resolution (DPI) for JPEG.

unresolved external symbol __libm_sse2 and _iob

Wed, 06 Jan 2010 00:00:00 -0800

Symptom(s):

When linking with the static threaded version of IPP libraries, e.g ippiemergedem64t.lib ippimergedem64_t.lib, you may 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 the 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 depend 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 bundles 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 built 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 linking 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 the MSVC static C run-time library libcmt.lib. When using IPP static threaded library in MSVC, we assume that the application is built with the /MT option, thus link libcmt.lib automatically.

But one application or its parts may have been built with the /MD option, which will link MSVC dynamic C run-time library MSVCRT*.dll,which does not have 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.

How to build IPP application in Linux environment

Tue, 15 Dec 2009 08:00:00 -0800

Introduction

Below we will give an example on how to build an IPP project in Linux within two steps.

Prerequisite: $source /em64t/tools/env/ippvarsem64t.sh

Required Software installed: Intel® IPP library install package: l_ipp_p_x_x.x.xxx.tgz
Supported Compiler: gcc, g++ and related tools or Intel® C++ Compiler version for Linux* OS for IA-32 processors and Intel 64 processors (optional).

Please note that the latest IPP version(IPP 7.0 Update 2)changed the library name and library directories: New Directory Structure and Library Naming Scheme for Intel® IPP 7.0 Library
You may change the library name and path correspondingly.

The library is available as a stand-alone product or as a component in Intel® Parallel Studio 2011, Intel® Parallel Studio XE 2011, Intel® C++ Studio XE 2011, Intel® Composer XE 2011, and Intel® C++ Composer XE 2011. Please visit the Intel® Software Evaluation Center to download evaluation versions of these and other Intel software products.

Step 1 – Call Intel® IPP Functions

Calling Intel IPP functions is as simple as calling any other C functions. Include the relevant header file (ex. ipp.h) and then call the function with correct parameters.

The example code is as follows:

#include “ipp.h”
void main()
{
IppiSize roi = {5,4};
Ipp8u x[8*4] = {0};
ippiSet_8u_C1R(1, x,8, roi); //call ippiSet_8u_C1R() function in ipp.h
}

Save this file as main.c.

Step 2 – Build Intel® IPP Projects

Build using gcc in command line. We will take Intel IPP 64bit as an example:

Set environment: export ipp_install_path="/opt/intel/ipp/6.1.x"
For dynamic link, the command is: $gcc -o main main.c -I /em64t/include -L /em64t/sharedlib -lippiem64t -lippsem64t -lippcoreem64t -liomp5 -lpthread -lm
For static link, the command is: $gcc -o main main.c -I /em64t/include -L /em64t/lib -lippiemergedem64t -lippimergedem64t -lippsemergedem64t -lippsmergedem64t -lippcoreem64t -lpthread
For threaded static link, the command is $gcc -o main main.c -I /em64t/include -L /em64t/lib -lippimergedem64t -lippimergedem64t_t -lippsmergedem64t -lippsmergedem64t_t -lippcoreem64t_t.a -liomp5 -lpthread

To see why we link these libraries in the command and to clarify the problem which libraries should be linked for my own project, you can refer to Library dependencies by domain.

If you build successfully, you can get the executable file: main.

*Note 1: is the path where your IPP is installed, e.g. /opt/intel/ipp/6.x/, /opt/intel/Compiler/11.x/0xx/ipp/.

*Note 2: The article command sample is for Intel 64 application. For IA32 application, the command is same:
-I /ia32/include -L /ia32/sharedlib -lippi -lipps -lippcore -liomp5 -lpthread -lm

*Note 3: As Which version of Intel IPP, Intel MKL and Intel TBB is installed by the Intel® Compiler Professional Edition? mentions, Intel Compiler Professional Edition have IPP as a component . At the same time, Intel Compiler provide a compile option -ipp instead linking ipp manually, thus if using Intel Compiler Professional Edition, the build command become simple:
$icc *.c -ipp

Step 3 - Run Intel® IPP Binary

If using the Intel® IPP shared libraries, you need to add the path to the libraries to the system variable LD_LIBRARY_PATH by either using the shell script or manually setting the environment.

Use the Intel IPP shell script to set the required environment variables for shared library dispatching and building code samples:
- Open a Terminal.
- Navigate to the Intel IPP directory /tools/env.
- Type source ippvars32.sh ( or ippvarsem64t.sh for Intel(R) 64 processors)

Manually set the environment variable:

- Open a Terminal.
- If the libraries are in the /opt/intel/ipp/X.X/ia32/sharedlib folder, and then type export LD_LIBRARY_PATH=/opt/intel/ipp/X.X/ia32/sharedlib:$LD_LIBRARY_PATH

Common error messages

Error message: main.c:(.text+0x49): undefined reference to `ippiSet_8u_C1R'
1. Make sure to link all dependent libraries. To solve the problem above, you should check your build command to see if it contains the library, "-lippiem64t".
2. Make sure to link the libraries in appropriate order. For example, if your command contains both "-lippiemergedem64t" and "-lippimergedem64t". Make sure to put "-lippiemergedem64t" before "-lippimergedem64t" in command, otherwise you will get this "undefined reference" either.
Error message: /opt/intel/ipp/6.0.0.045/em64t/sharedlib/libiomp5.so: undefined reference to `pthread_atfork'
- Please make sure to link "-lpthread" library in your command line.Error message: /opt/intel/ipp/6.0.0.045/em64t/lib/libippiemergedem64t.a(ippi02496as.o): In function `ippiSet_8u_C1R': (.text+0x3): undefined reference to `ippJumpIndexForMergedLibs'
  If your command line links libraries from /em64t/lib, please make sure to contain "-lippcoreem64t" library.
Other libiomp5 error: OpenMP run time library like libiomp5.so is provided by Intel(r) Compiler. It may locate in Compiler directory: OpenMP Run-time Libraries Changed since Intel IPP 6.0 and Intel MKL 10.1
http://software.intel.com/en-us/articles/xcode-link-error-file-not-found-libiomp5dylib/

Simplified Link Instructions for the IPP Library

Wed, 21 Oct 2009 21:00:00 -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 ippcorel.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 libiomp5md.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.

Note: libiomp5mt.lib and libiomp5md.lib are two different versions of the same Intel OpenMP library. The "t" version is a static link library and the "d" version is a dynamic link library. Both OpenMP libraries provide the same functionality. You are strongly encouraged to link against the dynamic version of the OpenMP library, regardless of how you link against the IPP library, in order to avoid conflicts associated with having multiple copies of the OpenMP library running on your system at the same time. One caveat is that linking against the "d" version of the OpenMP library will require that you redistribute the shared OpenMP library file (e.g., libiomp5md.dll) with your application, even if you have statically linked with the IPP library.

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

Avoiding libstdc++ library dependency when using ipp_zlib samples

Wed, 21 Oct 2009 06:00:00 -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.