Skip to content

Commit 16d8dbb

Browse files
committed
Merge pull request #7 from anhzhang/master
Added an new item how to link intel statically
2 parents cc89762 + 0a1f14f commit 16d8dbb

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

faq/building.inc

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1744,3 +1744,26 @@ href=\"$topdir/community/help/\">Getting Help</a> page -- it details
17441744
how to send a request to the Open MPI mailing lists.";
17451745

17461746
/////////////////////////////////////////////////////////////////////////
1747+
1748+
$q[] = "How do I statically link to the libraries of Intel compiler suite?";
1749+
1750+
$anchor[] = "statically-link-with-intel-libraries";
1751+
1752+
$a[] = "The Intel compiler suite, by default, dynamically links its runtime libraries
1753+
against the Open MPI binaries and libraries. This can cause problems if the Intel
1754+
compiler libraries are installed in non-standard locations. For example, you might
1755+
get errors like:
1756+
1757+
<blockquote>
1758+
error while loading shared libraries: libimf.so: cannot open shared object file:
1759+
No such file or directory
1760+
</blockquote>
1761+
1762+
To avoid such problems, you can pass flags to Open MPI's configure script that instruct
1763+
the Intel compiler suite to statically link its runtime libraries with Open MPI:
1764+
1765+
<geshi bash>
1766+
shell$ ./configure CC=icc CXX=icpc FC=ifort LDFLAGS=-Wc,-static-intel ...
1767+
</geshi>";
1768+
1769+
/////////////////////////////////////////////////////////////////////////

0 commit comments

Comments
 (0)