[Dune] [#880] Support applications using full statically linkage

Dune flyspray at dune-project.org
Fri Feb 18 15:40:30 CET 2011


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#880 - Support applications using full statically linkage
User who did this - Olaf Ippisch (ippisch)

----------
@Christian: I tested your approach on jugene and it does not work. The compiler command in the libtool call is not postfixed with -all-static. This leads to libtool still selecting the dynamic libraries and the compilation failing with
/bgsys/drivers/V1R4M2_200_2010-100508P/ppc/gnu-linux/lib/gcc/powerpc-bgp-linux/4.1.2/../../../../powerpc-bgp-linux/bin/ld: attempted static link of dynamic object `/bgsys/drivers/V1R4M2_200_2010-100508P/ppc/gnu-linux/powerpc-bgp-linux/lib/libstdc++.so'

@Robert: The time lag created by dynamic linking scales with the size of the problem. With 32000 Processors the time lag is 'only' 5 minutes, so you probably did not notice it.
However on 290000 processors the time lag is 40 minutes which is not acceptable. Markus made a test with a statically linked executable and there was no time lag at all. So dynamic linking is definitely the problem. The problem is that the nodes of jugene do not have any local drives and therefore 2900000 nodes simultaneously try to read the dynamic libraries
which leads to a load of mutually blocking.
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=880#comment2423

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.




More information about the Dune mailing list