Enable completely static build

[kilian]

The libtool mechanism allows for building both dynamically and statically linked versions of the executable. The statically linked version is not necessarily complete, i.e., ALL external libraries should be linked statically, including the Fortran runtime. Check this and enable it where necessary.

A fully static build is also necessary for reliable profiling.

[Juergen Reuter]

What is the connection of this w.r.t. to the --enable-fc-static flag introduced in r2995?

[kilian]

Thanks Juergen, I didn't remember that there is this ticket.

The option --enable-fc-static (together with an executable generated in the Sindarin file:

compile as "..."

now generates a static build. It is not COMPLETELY static, since it doesn't include static Fortran and C libraries. I'll check, leaving the ticket open for now.

[Juergen Reuter]

After discussion with Wolfgang moving back to 2.0.5.

[kilian]

Changes in r3076:

• Removed option --enable-fc-static, it didn't make much sense.
• Enabled the test 'static.run', was missing due to a typo
• The executable created by 'compile as ...' now generates an executable that contains all libtool libraries statically, including HepMC and LHAPDF (if enabled)
• It does not include the Fortran and C++ runtime libraries, these have to be installed on the target system.

Unless a build which includes the Fortran and C++ runtimes is really needed, the issue is settled. Closing the ticket.