#880 Support applications using full statically linkage
Metadata
| Property | Value |
|---|---|
| Reported by | Markus Blatt (markus@dr-blatt.de) |
| Reported at | Feb 17, 2011 14:40 |
| Type | Feature Request |
| Version | 2.0 |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | May 2, 2011 17:46 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | May 2, 2011 17:46 |
| Closed in version | Unknown |
| Resolution | Implemented |
| Comment | in r6383 |
Description
Hey,
the past few days I tried to persuade DUNE to build my binaries using only static linkage (for both system and 3rd-party libraries.) The main reason for this is that loading dynamically linked binaries takes more than half an hour on the full Blue Gene in Jülich.
It is possible, but needs some patch and some care:
- "libtool --tag=CXX --mode=link $CXX" --> "libtool --tag=CXX --mode=link $CXX -all-static" for both the module search test and all linking. (see attached diff that uses a LIBTOOL_LINK_FLAGS configure variable)
- Put "-static -static-libgcc" into LDFLAGS (in the opts file).
I was wondering whether a dunecontrol option for rquesting static-only linkage would make sense.