|
Please note the following with respect to this particular release of Intel® Threading Building Blocks.
Library issues
The cache_aligned_allocator template is incompatible with the Microsoft* deque and list containers.
The atomic<long long> and atomic<unsigned long long> templates are not supported when using the Microsoft* Visual C++* 7.1 (Microsoft* Visual Studio* .NET 2003) compiler.
To allow more accurate results to be obtained with Intel® Thread Checker or Intel® Thread Profiler, download the latest update releases of these products before using them with Intel Threading Building Blocks.
If you are using Intel Threading Building Blocks and OpenMP* constructs mixed together in rapid succession in the same program, and you are using Intel® compilers for your OpenMP code, set KMP_BLOCKTIME to a small value (e.g., 20 milliseconds) to improve performance. This setting can also be made within your OpenMP* code via the kmp_set_blocktime() library call. See the Intel compiler OpenMP documentation for more details on KMP_BLOCKTIME and kmp_set_blocktime().
In general, non-debug ("release") builds of applications or examples should link against the non-debug versions of the Intel Threading Building Blocks libraries, and debug builds should link against the debug versions of these libraries. On Windows* systems, compile with /MD and use Intel Threading Building Blocks release libraries, or compile with /MDd and use debug libraries; not doing so may cause run-time failures. See the Tutorial in the product "doc" sub-directory for more details on debug vs. release libraries.
When using Ubuntu* 7.04 in 64-bit mode, compilations can fail with error messages saying that "`::system' has not been declared". These failures can be worked around by removing libpthread-dev from the system. See the following link for more details:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/77559
Library example issues
When building an example on Windows* systems, either via a Makefile or via a Microsoft Visual Studio project, a spurious warning may be encountered of the form:
cl : Command line warning D4002 : ignoring unknown option '/G-'
This warning can be ignored; the compilation should complete and the compiled example should execute correctly.
The Xcode* IDE projects for the examples, on Mac OS* systems, currently only support Xcode tool suite 2.4 or higher. Use 'make' commands, as described in each example's index.html page, to build and run the examples on Mac OS systems when using Xcode* tool suite versions prior to 2.4.
Windows* installation issues
If the version of Windows* Installer on your system is older than version 2.0, the installer will automatically upgrade it and you will need to reboot the computer after the installation is complete.
Scripts are used in the normal install process and may trip false positives in certain anti virus software. You may need to disable script blocking or you may be able to temporarily allow scripts for the installation process.
Linux* installation issues
Some versions of RPM do not allow installation to a non-default installation directory, including RPM 4.0.2 (resolved in RPM 4.0.3) and RPM 4.1 (resolved in RPM 4.11 to 4.2).
When installing on Linux*, there is a known issue where the registration step at the end of the installation program may freeze after your email address is entered. If this occurs, you may interrupt the installation program (e.g., via pressing <ctrl-C>); the installation should already have completed.
In this case, you may register via the Intel® Software Development Products Registration Center by visiting:
https://registrationcenter.intel.com/
When installing on Mandriva/Mandrake* Linux* 10.1.06, there is a known issue where the installation program may freeze after printing "installing RPM package...". If this occurs, try re-installing and choose to install without using RPM.
Mac OS* installation issues
Xcode* tool suite 2.2.1 or higher must be installed prior to installing Intel Threading Building Blocks on Mac OS systems.
This applies to:
| 
